[jbosstools-issues] [JBoss JIRA] (JBDS-3689) ask user for JDK location when old location is gone

Len DiMaggio (JIRA) issues at jboss.org
Mon Mar 21 10:41:00 EDT 2016


    [ https://issues.jboss.org/browse/JBDS-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179919#comment-13179919 ] 

Len DiMaggio commented on JBDS-3689:
------------------------------------

FYI - A user can easily get into this situation by simply updating their JDK (yum update, etc.) - if the path changes to reflect the updated version number.

> 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: installer, upstream
>    Affects Versions: 9.1.0.Beta2
>         Environment: Fedora 23
>            Reporter: Aleksandar Kostadinov
>            Assignee: Denis Golovin
>             Fix For: 10.0.0.Alpha1
>
>
> 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