[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-3450.
------------------------------
Fix Version/s: 11.3.0.GA
Resolution: Done
Fixed in JBDS-4454 - Path to JDK needs to be updated after every update of JDK.
> installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3450
> URL: https://issues.jboss.org/browse/JBDS-3450
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 11.3.0.GA, 11.0.0.GA
>
> Attachments: jbds-installer_step4-jvm-selection.png
>
>
> {quote}
> (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min
> (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS.
> (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK)
> (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine
> (2015-06-02 16:39:02) joshuaw: was found after searching the following locations:
> (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java
> (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java?
> (2015-06-02 16:39:40) joshuaw: let me check
> 16:40
> (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it
> (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :(
> (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist?
> (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file
> (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update?
> (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist
> (2015-06-02 16:42:32) nickboldt: aha
> (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8*
> (2015-06-02 16:42:48) nickboldt: pwd
> (2015-06-02 16:42:52) nickboldt: put that in your ini file
> (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file
> (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk
> (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39
> (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39
> (2015-06-02 16:46:33) joshuaw: stupid minor minor version update
> (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ?
> (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file
> (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion
> (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini
> (2015-06-02 17:55:27) nickboldt: -vm
> (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> (2015-06-02 17:55:36) maxandersen: thats bad
> (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :(
> (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ?
> {quote}
> It's possible the installer is using the CURRENT value of alternatives path for JDK...
> {code}
> $➔ alternatives --display java
> java - status is manual.
> link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071
> {code}
> So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3450:
-----------------------------
Fix Version/s: 11.0.0.GA
> installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3450
> URL: https://issues.jboss.org/browse/JBDS-3450
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 11.0.0.GA
>
> Attachments: jbds-installer_step4-jvm-selection.png
>
>
> {quote}
> (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min
> (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS.
> (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK)
> (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine
> (2015-06-02 16:39:02) joshuaw: was found after searching the following locations:
> (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java
> (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java?
> (2015-06-02 16:39:40) joshuaw: let me check
> 16:40
> (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it
> (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :(
> (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist?
> (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file
> (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update?
> (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist
> (2015-06-02 16:42:32) nickboldt: aha
> (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8*
> (2015-06-02 16:42:48) nickboldt: pwd
> (2015-06-02 16:42:52) nickboldt: put that in your ini file
> (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file
> (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk
> (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39
> (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39
> (2015-06-02 16:46:33) joshuaw: stupid minor minor version update
> (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ?
> (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file
> (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion
> (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini
> (2015-06-02 17:55:27) nickboldt: -vm
> (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> (2015-06-02 17:55:36) maxandersen: thats bad
> (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :(
> (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ?
> {quote}
> It's possible the installer is using the CURRENT value of alternatives path for JDK...
> {code}
> $➔ alternatives --display java
> java - status is manual.
> link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071
> {code}
> So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3450:
-----------------------------
Fix Version/s: (was: 9.x)
> installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3450
> URL: https://issues.jboss.org/browse/JBDS-3450
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 11.0.0.GA
>
> Attachments: jbds-installer_step4-jvm-selection.png
>
>
> {quote}
> (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min
> (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS.
> (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK)
> (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine
> (2015-06-02 16:39:02) joshuaw: was found after searching the following locations:
> (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java
> (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java?
> (2015-06-02 16:39:40) joshuaw: let me check
> 16:40
> (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it
> (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :(
> (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist?
> (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file
> (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update?
> (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist
> (2015-06-02 16:42:32) nickboldt: aha
> (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8*
> (2015-06-02 16:42:48) nickboldt: pwd
> (2015-06-02 16:42:52) nickboldt: put that in your ini file
> (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file
> (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk
> (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39
> (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39
> (2015-06-02 16:46:33) joshuaw: stupid minor minor version update
> (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ?
> (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file
> (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion
> (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini
> (2015-06-02 17:55:27) nickboldt: -vm
> (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> (2015-06-02 17:55:36) maxandersen: thats bad
> (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :(
> (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ?
> {quote}
> It's possible the installer is using the CURRENT value of alternatives path for JDK...
> {code}
> $➔ alternatives --display java
> java - status is manual.
> link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071
> {code}
> So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBDS-4553) Get ready for Java 9
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4553?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4553 at 5/23/18 8:17 AM:
-----------------------------------------------------------
Note that there are various levels of "support" to be discussed here, including:
- ability to simply run the devstudio installer with JDK 9
- support devsuite installing JDK 9 on Windows/OSX
- support running Eclipse/devstudio with JDK 9 via installer / update site install
- support deploying projects to a JDK 9 runtime environment via Eclipse/devstudio
- support building projects w/ JDK 9 (which requires Maven 3.5.2 and potentially a new version of Tycho >= 1.1.0-SNAPSHOT)
(Edit: No new RPMs will be produced for 12.x, so we no longer have to support that install use case.)
was (Author: nickboldt):
Note that there are various levels of "support" to be discussed here, including:
- ability to simply run the devstudio installer with JDK 9
- support devsuite installing JDK 9 on Windows/OSX
- support running Eclipse/devstudio with JDK 9 via installer / update site install
- support running Eclipse/devstudio with JDK 9 via RPM install
- support deploying projects to a JDK 9 runtime environment via Eclipse/devstudio
- support building projects w/ JDK 9 (which requires Maven 3.5.2 and potentially a new version of Tycho >= 1.1.0-SNAPSHOT)
> Get ready for Java 9
> --------------------
>
> Key: JBDS-4553
> URL: https://issues.jboss.org/browse/JBDS-4553
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: installer, platform-installer
> Affects Versions: 11.1.0.AM2
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: installer, java9
> Fix For: 12.0.0.GA
>
>
> When 11.1 will be out, Java9 will also be out. The installer refuses to accept Java9 JVM when JBDS is installed. Shouldn't we accept them now ?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-23489) Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23489?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23489:
-------------------------------
Fix Version/s: 4.5.3.Final
(was: 4.6.x)
> Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23489
> URL: https://issues.jboss.org/browse/JBIDE-23489
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests, qa
> Affects Versions: 4.4.2.AM3
> Reporter: Pavol Srna
> Assignee: Vojtech Prusa
> Fix For: 4.5.3.Final
>
> Attachments: FreeMarket_rhscl_enabled.log, Freemarker_testRuntime_p2Installed.log
>
>
> We need to find a way how to run automated tests agains devstudio rpm.
> I've tried the following paths:
> 1) (as root) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/
> 2) (as hudson) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
> But none of the above works.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-23489) Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23489?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-23489.
------------------------------
Resolution: Won't Do
No new RPMs will be produced for 12.x, so I'm closing this.
> Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23489
> URL: https://issues.jboss.org/browse/JBIDE-23489
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests, qa
> Affects Versions: 4.4.2.AM3
> Reporter: Pavol Srna
> Assignee: Vojtech Prusa
> Fix For: 4.5.3.Final
>
> Attachments: FreeMarket_rhscl_enabled.log, Freemarker_testRuntime_p2Installed.log
>
>
> We need to find a way how to run automated tests agains devstudio rpm.
> I've tried the following paths:
> 1) (as root) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/
> 2) (as hudson) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
> But none of the above works.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months