[jbosstools-issues] [JBoss JIRA] (JBDS-3689) ask user for JDK location when old location is gone
Alexey Kazakov (JIRA)
issues at jboss.org
Sun Mar 20 12:26:00 EDT 2016
[ https://issues.jboss.org/browse/JBDS-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Kazakov reassigned JBDS-3689:
------------------------------------
Fix Version/s: 4.4
Assignee: Mickael Istria (was: Max Rydahl Andersen)
This functionality comes from Eclipse. Not JBDS. And I agree it would be more user-friendly to at least suggest to update the *.ini file to point it to some correct jvm location.
[~mickael_istria] can you take a look and at least report this issue to Eclipse? Thanks!
> 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_Studio/7.1/html/Migration_Guide/Change_the_Path_of_the_JVM.html
> 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)
More information about the jbosstools-issues
mailing list