[
https://issues.jboss.org/browse/JBDS-3689?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-3689:
--------------------------------------
This is one risk when setting the -vm flag. Eclipse IDE itself (at least on Linux)
doesn't set this -vm flag and relies on the JAVA_HOME or PATH, which gets correctly
updated when Java is updated. A solution for JBDS would be to simply not set this flag and
rely on the default behaviour to find out the best JVM.
ask user for JDK location when old location is gone
---------------------------------------------------
Key: JBDS-3689
URL:
https://issues.jboss.org/browse/JBDS-3689
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Components: upstream
Affects Versions: 9.1.0.Beta2
Environment: Fedora 23
Reporter: Aleksandar Kostadinov
Assignee: Mickael Istria
Fix For: 4.4
Hello, installed 9.1.0.Beta2 and starting it after some fedora update, yielded an error
that JDK is not found. With no help how to fix.
Searching over the internet I found
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu...
But it makes much more sense to let the user select a different location. Or at least
point user at the ini file to be updated. Currently user is left wondering why JBDS fails
to start when system has a perfectly working JDK installed on standard location. My first
thought was that for some reason JBDS installation broke.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)