[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4410) Modifying JDK version from "Open Launch Configuration" is misleading

[Max Rydahl Andersen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBIDE-4410:
---------------------------------------

    Fix Version/s: 3.1.0.M3
         Assignee: Rob Stryker


Rob - was thinking about this issue the other day. Couldn't this be "fixed" by adding validation in the configuration tabs we use and simply check if the user changed something that we know will be changed/wrong/fixed/overwritten based on runtime ?

> Modifying JDK version from "Open Launch Configuration" is misleading
> --------------------------------------------------------------------
>
>                 Key: JBIDE-4410
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4410
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS
>    Affects Versions: 3.0.0.GA
>            Reporter: Stelios Koussouris
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 3.1.0.M3
>
>
> From the IDE in the Open Launch Configuration you are be able to modify details related to the JDK but not the JDK itself. This is in order for the launch configurations not to go out of sync (ie. you are allowed to add, not modify things you already setup). The fact that when closing the "Open Launch Configuration" the changes of JDK is maintained (ie. showing different from the one in the "Runtime Environment") can be misleading since the server will start with the JDK set in "Runtime Environment". 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira