August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4495) Missing CDI features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4495?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4495: ---------------------------------- Final clarification points * we also want these three features (and their associated test features) to no longer be labelled "deprecated" - partial revert of https://github.com/jbosstools/jbosstools-javaee/commit/34ce9dc1a8f8207f04... * we want to keep the deprecated Central connectors for Seam 3, but remove the CDI stuff from inside them? https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... > Missing CDI features > -------------------- > > Key: JBDS-4495 > URL: https://issues.jboss.org/browse/JBDS-4495 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, cdi > Affects Versions: 11.0.0.GA > Reporter: Lukáš Valach > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 11.0.0.GA > > Attachments: No_CDI_Plugins.png > > > I have installed devstudio-11.0.0.GA-v20170801-0412-B670-installer-standalone.jar and I don't see any CDI functionality. It seems that CDI related plugins wasn't installed. > Help->About->Installation Detains->Plugins, Search for "CDI", there is nothing. > !No_CDI_Plugins.png|thumbnail! > JBoss Tools seems to be ok. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24024) Server adapter editor, wizard: better tell me what the settings are for

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24024?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24024: ------------------------------------------ [~rhopp] good catch! changing the fix-version > Server adapter editor, wizard: better tell me what the settings are for > ----------------------------------------------------------------------- > > Key: JBIDE-24024 > URL: https://issues.jboss.org/browse/JBIDE-24024 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_editor, server_adapter_wizard > Fix For: 4.5.1.AM1 > > Attachments: image-2017-03-03-11-43-41-941.png, image-2017-03-03-11-44-46-410.png, server-adapter-editor.png, server-adapter-wizard.png > > > A server adapter will publish local files to a pod in OpenShift (via rsync). Our wizard and server adapter editors allows to set the adapter to fullfill this task. The wizard and the editor do a poor job explaining the purpose of those settings though: > The wizard generically states that it does "file synchronization" but fails to tell "from" where to "where" > !image-2017-03-03-11-43-41-941.png! > The editor is even poorer in usability. It wont say anything about file synchronization and even mixes settings for the source and destination: > !image-2017-03-03-11-44-46-410.png! > "Source Path" should be right below the "Eclipse Project" since it's providing further details for it. "Pod Deployment Path" should be right below "Resource" (år "Service" in older verisions of this editor" since it provides the path on pods that are identified by "Resource". > Ideally we'd also add labels "From" and "To" (or similar means to better identify the settings) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24024) Server adapter editor, wizard: better tell me what the settings are for

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24024?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24024: ------------------------------------- Fix Version/s: 4.5.1.AM1 (was: 4.5.0.Final) > Server adapter editor, wizard: better tell me what the settings are for > ----------------------------------------------------------------------- > > Key: JBIDE-24024 > URL: https://issues.jboss.org/browse/JBIDE-24024 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_editor, server_adapter_wizard > Fix For: 4.5.1.AM1 > > Attachments: image-2017-03-03-11-43-41-941.png, image-2017-03-03-11-44-46-410.png, server-adapter-editor.png, server-adapter-wizard.png > > > A server adapter will publish local files to a pod in OpenShift (via rsync). Our wizard and server adapter editors allows to set the adapter to fullfill this task. The wizard and the editor do a poor job explaining the purpose of those settings though: > The wizard generically states that it does "file synchronization" but fails to tell "from" where to "where" > !image-2017-03-03-11-43-41-941.png! > The editor is even poorer in usability. It wont say anything about file synchronization and even mixes settings for the source and destination: > !image-2017-03-03-11-44-46-410.png! > "Source Path" should be right below the "Eclipse Project" since it's providing further details for it. "Pod Deployment Path" should be right below "Resource" (år "Service" in older verisions of this editor" since it provides the path on pods that are identified by "Resource". > Ideally we'd also add labels "From" and "To" (or similar means to better identify the settings) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24501) Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24501?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24501: ------------------------------------------ [~rhopp] thanks for testing this carefully! The main aim for this jira is to get rid of the NPE, which you seem to confirm. I also noticed the image disappearing. I am not fully sure how this is expected. If it's not, we should file another jira. [~jeffmaury] do you know why the image disappears? > Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24501 > URL: https://issues.jboss.org/browse/JBIDE-24501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: image-2017-05-23-12-00-51-733.png, image-2017-05-23-12-07-14-028.png, image-2017-05-23-12-10-06-694.png, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4495) Missing CDI features

by Bob Davis (JIRA)

[ https://issues.jboss.org/browse/JBDS-4495?page=com.atlassian.jira.plugin.... ] Bob Davis commented on JBDS-4495: --------------------------------- I agree with [~mmalina] - thank you. > Missing CDI features > -------------------- > > Key: JBDS-4495 > URL: https://issues.jboss.org/browse/JBDS-4495 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, cdi > Affects Versions: 11.0.0.GA > Reporter: Lukáš Valach > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 11.0.0.GA > > Attachments: No_CDI_Plugins.png > > > I have installed devstudio-11.0.0.GA-v20170801-0412-B670-installer-standalone.jar and I don't see any CDI functionality. It seems that CDI related plugins wasn't installed. > Help->About->Installation Detains->Plugins, Search for "CDI", there is nothing. > !No_CDI_Plugins.png|thumbnail! > JBoss Tools seems to be ok. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4495) Missing CDI features

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4495?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-4495: ------------------------------------- As agreed right now on the retrospective call (Nick, Bob, Jeff and others), we will put back these: org.jboss.tools.cdi.feature org.jboss.tools.maven.cdi.feature org.jboss.tools.cdi.deltaspike.feature > Missing CDI features > -------------------- > > Key: JBDS-4495 > URL: https://issues.jboss.org/browse/JBDS-4495 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, cdi > Affects Versions: 11.0.0.GA > Reporter: Lukáš Valach > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 11.0.0.GA > > Attachments: No_CDI_Plugins.png > > > I have installed devstudio-11.0.0.GA-v20170801-0412-B670-installer-standalone.jar and I don't see any CDI functionality. It seems that CDI related plugins wasn't installed. > Help->About->Installation Detains->Plugins, Search for "CDI", there is nothing. > !No_CDI_Plugins.png|thumbnail! > JBoss Tools seems to be ok. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24501) Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24501?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-24501: ------------------------------------ Hi [~adietish], I tried to verify this one, but unfortunately I was not able to. I've built the hola docker image on docker daemon from CDK 3.1. Then I deployed it to openshift (CDK) project "test" successfully and the image gets pushed into docker registry as "172.30.1.1:5000/test/hola". Then I tried to deploy that image to the second project "test1", but I failed (as seen on screencast: https://youtu.be/JolnbsW1lTw). Could you please check if I did something wrong, or whether I encountered a bug? Notice, that after I tried to deploy the 172.30.1.1:5000/test/hola image (and failed), the image somehow disappears, which seems pretty weird to me. > Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24501 > URL: https://issues.jboss.org/browse/JBIDE-24501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: image-2017-05-23-12-00-51-733.png, image-2017-05-23-12-07-14-028.png, image-2017-05-23-12-10-06-694.png, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24646) Import wizard: doesnt check if local branch match

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24646?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24646: ------------------------------------- Summary: Import wizard: doesnt check if local branch match (was: Import App from openshift doesnt check branch match) > Import wizard: doesnt check if local branch match > ------------------------------------------------- > > Key: JBIDE-24646 > URL: https://issues.jboss.org/browse/JBIDE-24646 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Jan Novak > Labels: import_app, openshift_v3 > Fix For: 4.5.x > > > Importing project from Openshift > * use existing repo > * local repo uses different branch than Openshift > * remote branch isnt locally fetched > * import finishes succesfully > * in local repo is *stil checkouted wrong branch*, without any warnings -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24646) Import wizard: doesnt check if local branch match

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24646?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24646: ------------------------------------- Labels: import_app openshift_v3 (was: ) > Import wizard: doesnt check if local branch match > ------------------------------------------------- > > Key: JBIDE-24646 > URL: https://issues.jboss.org/browse/JBIDE-24646 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Jan Novak > Labels: import_app, openshift_v3 > Fix For: 4.5.x > > > Importing project from Openshift > * use existing repo > * local repo uses different branch than Openshift > * remote branch isnt locally fetched > * import finishes succesfully > * in local repo is *stil checkouted wrong branch*, without any warnings -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24646) Import application: doesnt check if local branch match

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24646?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24646: ------------------------------------- Summary: Import application: doesnt check if local branch match (was: Import wizard: doesnt check if local branch match) > Import application: doesnt check if local branch match > ------------------------------------------------------ > > Key: JBIDE-24646 > URL: https://issues.jboss.org/browse/JBIDE-24646 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Jan Novak > Labels: import_app, openshift_v3 > Fix For: 4.5.x > > > Importing project from Openshift > * use existing repo > * local repo uses different branch than Openshift > * remote branch isnt locally fetched > * import finishes succesfully > * in local repo is *stil checkouted wrong branch*, without any warnings -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2017