February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23925) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23925?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23925. ------------------------------ Resolution: Done > For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid] > ------------------------------------------------------------------------- > > Key: JBIDE-23925 > URL: https://issues.jboss.org/browse/JBIDE-23925 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid > Reporter: Jeff MAURY > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.4.4.AM1 > > > For JBIDE 4.4.4.AM1 [aerogear-hybrid]: Please perform the following tasks: > > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1 > > [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...] > > 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.4.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.4.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch: > > {code} > git checkout master; > git pull origin master; > git checkout -b jbosstools-4.4.x; > git push origin jbosstools-4.4.x > {code} > > Now, your root pom will use parent pom version: > > * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.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 aerogear-hybrid 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23907) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23907?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23907. ------------------------------ Resolution: Done > For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid] > ------------------------------------------------------------------------- > > Key: JBIDE-23907 > URL: https://issues.jboss.org/browse/JBIDE-23907 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid > Reporter: Jeff MAURY > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.4.4.AM1 > > > For JBIDE 4.4.4.AM1 [aerogear-hybrid]: Please perform the following tasks: > > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1 > > [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...] > > 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.4.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.4.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch: > > {code} > git checkout master; > git pull origin master; > git checkout -b jbosstools-4.4.x; > git push origin jbosstools-4.4.x > {code} > > Now, your root pom will use parent pom version: > > * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.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 aerogear-hybrid 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23926) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [arquillian]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23926?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23926. ------------------------------ Resolution: Done > For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [arquillian] > -------------------------------------------------------------------- > > Key: JBIDE-23926 > URL: https://issues.jboss.org/browse/JBIDE-23926 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: arquillian > Reporter: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.4.AM1 > > > For JBIDE 4.4.4.AM1 [arquillian]: Please perform the following tasks: > > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1 > > [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...] > > 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.4.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.4.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch: > > {code} > git checkout master; > git pull origin master; > git checkout -b jbosstools-4.4.x; > git push origin jbosstools-4.4.x > {code} > > Now, your root pom will use parent pom version: > > * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.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 arquillian 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23908) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [arquillian]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23908?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23908. ------------------------------ Resolution: Done > For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [arquillian] > -------------------------------------------------------------------- > > Key: JBIDE-23908 > URL: https://issues.jboss.org/browse/JBIDE-23908 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: arquillian > Reporter: Jeff MAURY > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.4.4.AM1 > > > For JBIDE 4.4.4.AM1 [arquillian]: Please perform the following tasks: > > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1 > > [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...] > > 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.4.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.4.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch: > > {code} > git checkout master; > git pull origin master; > git checkout -b jbosstools-4.4.x; > git push origin jbosstools-4.4.x > {code} > > Now, your root pom will use parent pom version: > > * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.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 arquillian 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ] Jan Richter commented on JBIDE-22075: ------------------------------------- Yup, that's the one. > Confusing error message when trying to attach remote debugger to OS app run in debug mode > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22075 > URL: https://issues.jboss.org/browse/JBIDE-22075 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: debugging, openshift_v3 > Fix For: 4.4.3.Final > > Attachments: debug-button-toolbar.png, error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, launch-debug-no-error.mov, remote-debugger-already-launched.png > > > If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically. > If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message > When I am trying to run remote debugging of an application on OpenShift I get following error > !!error-in-launching-remote-debugger.png! ! > {code} > Failed to connect to remote VM > com.sun.jdi.connect.spi.ClosedConnectionException > at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222) > at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214) > at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185) > at java.lang.Thread.run(Thread.java:745) > {code} > *Steps to reproduce:* > ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace. > EXEC: Select "Restart in Debug" in context menu of server adapter. > ASSERT: Server adapter is in state debugging ("[Debugging, Started]"). > EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging. > RESULT: Error is shown. > EXPECTED RESULT: The error message should tell you that there already is an instance running. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23895) JBoss Tools Central install job (smoke test) failing due to UI blocker

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23895?page=com.atlassian.jira.plugi... ] Lukáš Valach commented on JBIDE-23895: -------------------------------------- I am sorry for this misunderstanding. I only created PR. We have to wait until somebody megre this PR https://github.com/jbdevstudio/jbdevstudio-qa/pull/123 Or you can start job with these parameters: TESTS_FORK=luvalach TEST_BRANCH=JBIDE-23895_Update_JBT_from_online_site_fix_20170216 Or simply rebuild [build #31.|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_installer_tests/job/Devstudio_Installation/job/BYOE_Installation/job/Install_JBoss_Tools_online_update_site/31/rebuild/parameterized] > JBoss Tools Central install job (smoke test) failing due to UI blocker > ---------------------------------------------------------------------- > > Key: JBIDE-23895 > URL: https://issues.jboss.org/browse/JBIDE-23895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: install-tests > Affects Versions: 4.4.3.Final > Reporter: Nick Boldt > Assignee: Lukáš Valach > > This job is failing: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code} > 08:40:05.807 DEBUG [main][ScreenshotCapturer] Capturing Screenshot: ./target/screenshots/default/com.jboss.jbds.byoe.test.UpdateSiteTest.testInstallFromUpdateSite.png > java.lang.AssertionError: Licence is accepted by default{code} > -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Devstudi... > I'd like to use it to help verify that staged bits for QE are correctly populated, but I can't if the test won't run. :( > Can it be fixed to bypass the UI blockage? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4272) Check user permission before creating symlinks in /usr/local/bin on mac OS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4272?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4272: ----------------------------------- Assignee: Denis Golovin > Check user permission before creating symlinks in /usr/local/bin on mac OS > -------------------------------------------------------------------------- > > Key: JBDS-4272 > URL: https://issues.jboss.org/browse/JBDS-4272 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Story > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.4.0.AM1 > > Attachments: install.log > > > Installer fails if current user has no access to /usr/local/bin on mac OS -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3973) DevSuite Installer for MAC OS X

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3973?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3973: -------------------------------- Fix Version/s: 10.3.0.GA (was: 10.4.0.AM1) > DevSuite Installer for MAC OS X > ------------------------------- > > Key: JBDS-3973 > URL: https://issues.jboss.org/browse/JBDS-3973 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Affects Versions: 10.x > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.3.0.GA > > > DevSuite should provide installer for Mac OS X and match features available under Windows: > 1. Online and bundle installer distributions; > 2. Detection of installed software; > 3. Optional installation for any component from software stack; > 4. Installation for vagrant and virtualbox from apple disk image (.dmg files); > 5. Starting DevStudio from installer's last page; > 6. Adding installed components to PATH. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3973) DevSuite Installer for MAC OS X

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3973?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-3973. ------------------------------- Resolution: Done > DevSuite Installer for MAC OS X > ------------------------------- > > Key: JBDS-3973 > URL: https://issues.jboss.org/browse/JBDS-3973 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Affects Versions: 10.x > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.3.0.GA > > > DevSuite should provide installer for Mac OS X and match features available under Windows: > 1. Online and bundle installer distributions; > 2. Detection of installed software; > 3. Optional installation for any component from software stack; > 4. Installation for vagrant and virtualbox from apple disk image (.dmg files); > 5. Starting DevStudio from installer's last page; > 6. Adding installed components to PATH. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4032) [cdk installer] weird errors during startup

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4032?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-4032. ------------------------------- Resolution: Out of Date Vagrant is not used in CDK 3 > [cdk installer] weird errors during startup > ------------------------------------------- > > Key: JBDS-4032 > URL: https://issues.jboss.org/browse/JBDS-4032 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Rob Stryker > Assignee: Denis Golovin > Fix For: 10.4.0.AM1 > > > After a previously-working environment, I installed build http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/2016-08-24_0... > Once I did that, I get teh following environment: > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant -v > Vagrant 1.8.1 > Administrator@LBDZ-20120704HU MINGW64 /c/DevelopmentSuite4/cdk/components/rhel/rhel-ose > $ vagrant plugin list > landrush (1.1.2) > vagrant-registration (1.2.2) > - Version Constraint: 1.2.2 > vagrant-service-manager (1.1.0) > - Version Constraint: 1.1.0 > vagrant-share (1.1.5, system) > vagrant-sshfs (1.1.0) > - Version Constraint: 1.1.0 > Vagrant up had following log: https://paste.fedoraproject.org/418594/77989147/ > That log indicated I should read another log. The 2nd log is: https://paste.fedoraproject.org/418595/26780201/ > Removing the box and re-adding it did not seem to help. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017