[
https://issues.jboss.org/browse/JBDS-3689?page=com.atlassian.jira.plugin....
]
Alexey Kazakov commented on JBDS-3689:
--------------------------------------
First at all this is not purely JBDS specific. This is a documented Eclipse feature we use
in JBDS. Despite the way we go in JBDS, Eclipse could behave better and at least give more
details to the user how the problem with missing JVM can be fixed.
And we can't just get rid of -vm for JBDS completely because the default JVM can be
incompatible with JBDS. But what we can/should do is to not set -vm if users chose the
default JVM during the installation.
So I see here two issues:
#1 Upstream one. Eclipse doesn't suggest to change -vm in the *.ini file to fix the
problem. [~mickael_istria] can you report it to Eclipse?
#2 JBDS installer should not set -vm if the default JVM is used. Assigning this to
[~dgolovin].
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)