November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22878?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22878: --------------------------------------- [~rob.stryker], sorry for the delay. Yes, let's go through this together. Is tomorrow good? > EAR deployed from DevStudio to EAP contains errorneously named ejbs > ------------------------------------------------------------------- > > Key: JBIDE-22878 > URL: https://issues.jboss.org/browse/JBIDE-22878 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final, 4.4.0.Final > Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. > Reporter: Mikhail Kalkov > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: JBIDE-22878-deployment-assembly.png, screendump.png, test-ear.ear, test-projects.zip > > > I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar. > When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot. > This problem makes it extremely difficult to debug issues that arise only with zipped ear deployments. The only workaround is to comment out bundleFileName lines in test-ear pom.xml as well as possibly fix filenames in persistence.xml, and remember to revert these changes before committing! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23213?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23213: --------------------------------------- It seems that the conclusion is to put off adding Fedora until next release, if this is fixed by then. >From HipChat: Todd: {quote} I've been having issues with F25 for other stuff, so I think the call is to drop F25 as a supported platform for Banksia. If we can find workarounds and documenting them, let's do so (and that can be done post-release, too.) {quote} Len: {quote} +1 (To Todd) {quote} > Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23213 > URL: https://issues.jboss.org/browse/JBIDE-23213 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Martin Malina > Labels: releasework > Fix For: 4.4.2.Final > > > It's time to review the available platforms on which we test devstudio / jbt. > Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016. > [0] https://wiki.ubuntu.com/Releases > * Should we move to 16.04.1 LTS and 16.10? > * Should we move to 14.04.5 LTS and 16.04.1 LTS ? > * Should we move to 14.04.5 LTS and 16.10? > Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1]. > [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... > But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right? > [2] https://fedoraproject.org/wiki/Releases/25/Schedule > * Should we move to F24 and F25? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4203) For JBDS 10.2.0.GA: Prepare for 4.4.2.Final / 10.2.0.GA [installer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4203?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4203. ---------------------------- Resolution: Done > For JBDS 10.2.0.GA: Prepare for 4.4.2.Final / 10.2.0.GA [installer] > ------------------------------------------------------------------- > > Key: JBDS-4203 > URL: https://issues.jboss.org/browse/JBDS-4203 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 10.2.0.GA > > > For JBDS 10.2.0.GA [installer]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: features installer LICENSE.txt p2-director plugins pom.xml pom.xml.orig README.adoc results rpm site *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: features installer LICENSE.txt p2-director plugins pom.xml pom.xml.orig README.adoc results rpm site *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4203) For JBDS 10.2.0.GA: Prepare for 4.4.2.Final / 10.2.0.GA [installer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4203?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4203: -------------------------------- Assignee: Nick Boldt (was: Denis Golovin) > For JBDS 10.2.0.GA: Prepare for 4.4.2.Final / 10.2.0.GA [installer] > ------------------------------------------------------------------- > > Key: JBDS-4203 > URL: https://issues.jboss.org/browse/JBDS-4203 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 10.2.0.GA > > > For JBDS 10.2.0.GA [installer]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: features installer LICENSE.txt p2-director plugins pom.xml pom.xml.orig README.adoc results rpm site *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: features installer LICENSE.txt p2-director plugins pom.xml pom.xml.orig README.adoc results rpm site *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23213?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23213: ------------------------------------ Re: F25 w/ Wayland... see JBDS-4204 > Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23213 > URL: https://issues.jboss.org/browse/JBIDE-23213 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Martin Malina > Labels: releasework > Fix For: 4.4.2.Final > > > It's time to review the available platforms on which we test devstudio / jbt. > Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016. > [0] https://wiki.ubuntu.com/Releases > * Should we move to 16.04.1 LTS and 16.10? > * Should we move to 14.04.5 LTS and 16.04.1 LTS ? > * Should we move to 14.04.5 LTS and 16.10? > Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1]. > [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... > But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right? > [2] https://fedoraproject.org/wiki/Releases/25/Schedule > * Should we move to F24 and F25? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) JBoss IDE and dialogs not sizing correctly under Fedora 25

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4204: ----------------------------- Release Notes Docs Status: Not Yet Documented This should be documented as a known issue w/ workaround. cc: [~supriya.bharadwaj] > JBoss IDE and dialogs not sizing correctly under Fedora 25 > ---------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Snjezana Peco > Labels: upstream > Fix For: 10.x > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) JBoss IDE and dialogs not sizing correctly under Fedora 25

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Snjezana Peco reassigned JBDS-4204: ----------------------------------- Assignee: Snjezana Peco > JBoss IDE and dialogs not sizing correctly under Fedora 25 > ---------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Snjezana Peco > Labels: upstream > Fix For: 10.x > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23514) Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23514: ------------------------------------------ [~rob.stryker] I agree. We already do such (far from perfect) guessing for local code when deploying docker images, trying to mirror what the cmd-line does in "oc new-project". Debug ports are present in docker metadata. See https://issues.jboss.org/browse/CLOUD-243?focusedCommentId=13136473&page=... [~jcantrill] do you know if there is anything that could help us identifying if the app in OpenShift supports JMX? > Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error) > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23514 > URL: https://issues.jboss.org/browse/JBIDE-23514 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: jmx, openshift_v3, server_adapter > Fix For: 4.4.3.AM1 > > Attachments: jmx-error-nodejs.png > > > Most likely server adapters for non-java based apps should not have a jmx node. > Steps to reproduce: > # ASSERT: make sure that you have a nodejs app (with a service) running in OpenShift (ex. created via nodejs-example template) > # ASSERT: make sure the build is finished, the pod is running. > # ASSERT: make sure that you have a server adapter for your service > # ASSERT: make sure that it is in "[Started, Synchronized]" state) > # EXEC: unfold the server adapter and double click on the JMX child > Result: > An error shows up > !jmx-error-nodejs.png! > {code} > java.io.IOException: org.jolokia.client.exception.J4pRemoteException: Service Unavailable > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:328) > at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:83) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.jolokia.client.exception.J4pRemoteException: Service Unavailable at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:278) > at org.jolokia.client.J4pClient.execute(J4pClient.java:191) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4205) Devsuite Installer for Mac OSX is not labeled Alpha

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBDS-4205?page=com.atlassian.jira.plugin.... ] Catherine Robson commented on JBDS-4205: ---------------------------------------- [~dgolovin] Correct, we've never put version numbers or Alpha/Beta/GA information on the product logos. > Devsuite Installer for Mac OSX is not labeled Alpha > --------------------------------------------------- > > Key: JBDS-4205 > URL: https://issues.jboss.org/browse/JBDS-4205 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.GA > Reporter: Pavol Srna > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.2.0.GA > > Attachments: label-alpha.png > > > Devsuite Installer for mac osx is according to the Banksia global goals alpha quality. > The installer should say so in all labels. > !label-alpha.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4098) Support OpenShift 3.3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-4098?page=com.atlassian.jira.plugin.... ] Marián Labuda closed JBDS-4098. ------------------------------- Verified. DevStudio 10.2.0.GA has been tested with OSE 3.3.x. > Support OpenShift 3.3 > --------------------- > > Key: JBDS-4098 > URL: https://issues.jboss.org/browse/JBDS-4098 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: openshift > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Fix For: 10.2.0.GA > > > iPaas Fuse is using Openshift 3.3 > In order to improve Eclipse Fuse Tooling to work with iPaas Fuse, JBDS need to support OpenShift 3.3 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 November 2016