[
https://issues.jboss.org/browse/JBIDE-14565?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-14565.
---------------------------------
Assignee: Rob Stryker
I cannot reproduce this message and I never saw it in the past (but I was away during
Beta1 testing) so I assume it is fixed (hopefully).
Verified in JBDS 7.0.0.Beta2 B318
jdk warning for servers are a bit fuzzy
---------------------------------------
Key: JBIDE-14565
URL:
https://issues.jboss.org/browse/JBIDE-14565
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Labels: respin-a
Fix For: 4.1.0.Beta2
Using a default eclipse install, pointing to a default EAP 6.1 (and probably any other
server) it chooses:
"Default JRE for JavaSE-1.6" as its JRE.
Even though I have an Java SE installed as the default runtime for this JRE.
Then the wizard tells me:
"This runtime type requries a JDK for launching a server. We cannot guarantee the
default virtual machine for this execution environment is a JDK".
and its cut off in the middle of the last line.
A) why not choose the JDK execution environment when one is there ?
B) since the execution environment actually points to a JDK the warning is not correct
C) The text is hard to grok.
- the title says server but text says runtime
- the warning shows up for the default behavior
- use "a server" when it is a specific one
suggestion for simplification:
"The server runtime requires a JDK to launch. 'Default JRE for JavaSE-1.6'
does not look like a JDK"
...actually - this is just as horrible.
If we cannot detect the various execution environments are a JDK reliably we
shouldn't warn at this time. It is confusing.
How come Java 7 execution environment is detectable as a JDK but the Default JRE is not ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira