[
https://issues.jboss.org/browse/JBIDE-17829?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-17829:
-------------------------------------
So something is really wrong.
Max, your sense of melodrama is over-the-top. I think it's obvious that the validation
is occurring using the previously selected widget, rather than with the new selection. I
would not consider this a blocker at all, or be so super confused by it.
As for why the launch configuration is displaying java-6 libraries, you already indicated
your workspace has no java other than java6. This means, clearly, that the launch
configuration could only possibly have java6 as the java to use. This also is not
confusing in the least.
Can you explain the reason you're confused by this? Would you expect a nonexistant
java7 be on the classpath for your server, despite the fact that your workspace has no
java7 declared?
Aside from fixing the lagging validation, I really don't see any big problems here.
Server adapter chooses wrong runtime for launches and validation is
inconsistent
--------------------------------------------------------------------------------
Key: JBIDE-17829
URL:
https://issues.jboss.org/browse/JBIDE-17829
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Priority: Blocker
Labels: respin-a
Fix For: 4.2.0.Beta3
I have only Java 6 JDK in eclipse.
Create server
Wildfly 8 (download and install runtime now works sanely- yay!)
gets error saying "No valid JRE's found for execution environment
"JavaSE-1.8" even though I have "JavaSE-1.7" selected.
and when I change to 1.8 it says it can't find one for 1.7...something is weird.
Then I add Java 7, choose Java 7 and save.
When opening launch configuration it has Java SE 6 as the JRE system library for
bootstrap entries.
So something is *really* wrong.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)