October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23402) Explorer: can "Deploy Latest" even if the build failed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23402: -------------------------------- Component/s: upstream > Explorer: can "Deploy Latest" even if the build failed > ------------------------------------------------------ > > Key: JBIDE-23402 > URL: https://issues.jboss.org/browse/JBIDE-23402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png > > > I can have a deploy pod is waiting for a build pod that already failed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23402) Explorer: can "Deploy Latest" even if the build failed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23402: -------------------------------- Attachment: JBIDE-23402-a.png JBIDE-23402-b.png Here we can see that the deploy pod is waiting on the build pod, even though the build pod has failed. The deploy pod should fail very quickly once the build pod it's waiting for has failed. > Explorer: can "Deploy Latest" even if the build failed > ------------------------------------------------------ > > Key: JBIDE-23402 > URL: https://issues.jboss.org/browse/JBIDE-23402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png > > > I can have a deploy pod is waiting for a build pod that already failed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23402) Explorer: can "Deploy Latest" even if the build failed

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23402: ---------------------------------------- Summary: Explorer: can "Deploy Latest" even if the build failed Key: JBIDE-23402 URL: https://issues.jboss.org/browse/JBIDE-23402 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.2.AM2 Reporter: Andre Dietisheim I can have a deploy pod is waiting for a build pod that already failed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3743) Cannot use JBDS 10.2 with jdk 9 EA build 140

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3743?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3743 at 10/21/16 2:26 PM: ------------------------------------------------------------ Reopened to fix JIRA title (this is re: devstudio 10, not 9). But wanted to also note some other gotchas with using devstudio 10.2.0.AM2 and jdk 9: a) installer won't run with jdk 9, as noted above b) installer DOES run with jdk 8, then by editing `jbdevstudio.ini` with these values you can START devstudio 10.2 using jdk 9 ea build 140: {code}-vm /opt/jdk-9-ea+140/bin/java ... -vmargs --add-modules=java.se.ee{code} !launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png|thumbnail! However... (and this is why I reopened this issue, really) On startup there's no JRE available: !launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png|thumbnail! I tried adding JDK 9 ea build 140, and Eclipse rejects the /opt/jdk-9-ea+140 folder with: {code} Target is not a JDK root. System library was not found. {code} So... I don't see any way to actually USE devstudio with JDK 9, other than simply launching it and then using JDK 8 for everything else. was (Author: nickboldt): Reopened to fix JIRA title (this is re: devstudio 10, not 9). But wanted to also note some other gotchas with using devstudio 10.2.0.AM2 and jdk 9: a) installer won't run with jdk 9, as noted above b) installer DOES run with jdk 8, then editing `jbdevstudio.ini` with these values does allow it to start using jdk 9 ea build 140: {code}-vm /opt/jdk-9-ea+140/bin/java ... -vmargs --add-modules=java.se.ee{code} !launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png|thumbnail! But then on startup there's no JRE available: !launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png|thumbnail! > Cannot use JBDS 10.2 with jdk 9 EA build 140 > -------------------------------------------- > > Key: JBDS-3743 > URL: https://issues.jboss.org/browse/JBDS-3743 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 10.0.0.Alpha1, 10.2.0.AM2 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 10.x > > Attachments: launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-found-cant-build.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3743) Cannot use JBDS 10.2 with jdk 9 EA build 140

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3743?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3743: ----------------------------- Fix Version/s: 10.x (was: 10.0.0.Alpha1) > Cannot use JBDS 10.2 with jdk 9 EA build 140 > -------------------------------------------- > > Key: JBDS-3743 > URL: https://issues.jboss.org/browse/JBDS-3743 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 10.0.0.Alpha1, 10.2.0.AM2 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 10.x > > Attachments: launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-found-cant-build.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3743) Cannot use JBDS 10.2 with jdk 9 EA build 140

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3743?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3743: ----------------------------- Affects Version/s: 10.2.0.AM2 10.0.0.Alpha1 (was: 9.1.0.Beta1) > Cannot use JBDS 10.2 with jdk 9 EA build 140 > -------------------------------------------- > > Key: JBDS-3743 > URL: https://issues.jboss.org/browse/JBDS-3743 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 10.0.0.Alpha1, 10.2.0.AM2 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 10.0.0.Alpha1 > > Attachments: launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-found-cant-build.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3743) Cannot start JBDS 10 with jdk 1.9 EA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3743?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3743 at 10/21/16 2:21 PM: ------------------------------------------------------------ Reopened to fix JIRA title (this is re: devstudio 10, not 9). But wanted to also note some other gotchas with using devstudio 10.2.0.AM2 and jdk 9: a) installer won't run with jdk 9, as noted above b) installer DOES run with jdk 8, then editing `jbdevstudio.ini` with these values does allow it to start using jdk 9 ea build 140: {code}-vm /opt/jdk-9-ea+140/bin/java ... -vmargs --add-modules=java.se.ee{code} !launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png|thumbnail! But then on startup there's no JRE available: !launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png|thumbnail! was (Author: nickboldt): Reopened to fix JIRA title (this is re: devstudio 10, not 9). But wanted to also note some other gotchas with using devstudio 10.2.0.AM2 and jdk 9: a) installer won't run with jdk 9, as noted above b) installer DOES run with jdk 8, then editing jbdevstudio.ini with these values does allow it to start using jdk 9 ea build 140: {code}-vm /opt/jdk-9-ea+140/bin/java ... -vmargs --add-modules=java.se.ee{code} See also !launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png|thumbnail! But then on startup there's no JRE available: !launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png|thumbnail! > Cannot start JBDS 10 with jdk 1.9 EA > ------------------------------------ > > Key: JBDS-3743 > URL: https://issues.jboss.org/browse/JBDS-3743 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 10.0.0.Alpha1 > > Attachments: launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-found-cant-build.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3743) Cannot use JBDS 10.2 with jdk 9 EA build 140

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3743?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3743: ----------------------------- Summary: Cannot use JBDS 10.2 with jdk 9 EA build 140 (was: Cannot start JBDS 10 with jdk 1.9 EA) > Cannot use JBDS 10.2 with jdk 9 EA build 140 > -------------------------------------------- > > Key: JBDS-3743 > URL: https://issues.jboss.org/browse/JBDS-3743 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 10.0.0.Alpha1 > > Attachments: launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-found-cant-build.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3743) Cannot start JBDS 10 with jdk 1.9 EA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3743?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3743: ----------------------------- Attachment: launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-found-cant-build.png Worse, most of the quickstarts don't work. Managed to get the AngularJS Forge one to install the project, but then this error occurred, related to the previous comment: !launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-found-cant-build.png|thumbnail! The other quickstarts I tried just failed to do anything ... HTML5, JavaEE Web, Hybrid Mobile, Maven. > Cannot start JBDS 10 with jdk 1.9 EA > ------------------------------------ > > Key: JBDS-3743 > URL: https://issues.jboss.org/browse/JBDS-3743 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 10.0.0.Alpha1 > > Attachments: launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-found-cant-build.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3743) Cannot start JBDS 10 with jdk 1.9 EA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3743?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3743 at 10/21/16 2:20 PM: ------------------------------------------------------------ Reopened to fix JIRA title (this is re: devstudio 10, not 9). But wanted to also note some other gotchas with using devstudio 10.2.0.AM2 and jdk 9: a) installer won't run with jdk 9, as noted above b) installer DOES run with jdk 8, then editing jbdevstudio.ini with these values does allow it to start using jdk 9 ea build 140: {code}-vm /opt/jdk-9-ea+140/bin/java ... -vmargs --add-modules=java.se.ee{code} See also !launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png|thumbnail! But then on startup there's no JRE available: !launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png|thumbnail! was (Author: nickboldt): Reopened to fix JIRA title (this is re: devstudio 10, not 9). But wanted to also note some other gotchas with using devstudio 10.2.0.AM2 and jdk 9: a) installer won't run with jdk 9, as noted above b) installer DOES run with jdk 8, then editing jbdevstudio.ini with these values does allow it to start using jdk 9 ea build 140: {code}-vm /opt/jdk-9-ea+140/bin/java ... -vmargs --add-modules=java.se.ee{code} See also [^launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png] But then on startup there's no JRE available: [^launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png] > Cannot start JBDS 10 with jdk 1.9 EA > ------------------------------------ > > Key: JBDS-3743 > URL: https://issues.jboss.org/browse/JBDS-3743 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 10.0.0.Alpha1 > > Attachments: launchdevstudio10.2.0.AM2-with-jdk9ea140-configuration-settings.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-found-cant-build.png, launchdevstudio10.2.0.AM2-with-jdk9ea140-jre-not-supported.png > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016