[
https://issues.jboss.org/browse/JBIDE-19576?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-19576.
---------------------------------
I checked this and it works ok. For instance when you remove all 1.8 jdks, you can no
longer select the java-se-1.8 exec environment. But I wondered what would happen if I set
the runtime up with 1.8 and remove the installed VMs after. The server will actually start
with java 1.7 - I expected some error - and then when I add a 1.8 java back in it will
start with java 1.8. I'm not sure how this works, but it works :)
Verified in JBoss Tools 4.3.0.Alpha2
Execution environments with no matching JREs should not show up in
runtime wizard
---------------------------------------------------------------------------------
Key: JBIDE-19576
URL:
https://issues.jboss.org/browse/JBIDE-19576
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.0.Alpha2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.3.0.Alpha2
In a new server / runtime wizard, execution environments such as java8 may show up in the
list despite hte workspace having no java8 or higher JREs available. When the user selects
the Java8 exec-env, an error is shown and the user cannot continue.
This execution environment should not appear in the list unless the user has a compatible
JRE in the workspace.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)