[
https://issues.jboss.org/browse/JBIDE-17829?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-17829:
-------------------------------------
I re-read your jira, and you say it's starting with java6. I'm not able to
replicate this in any way. I'm not able to mark a java6 jre as a default vm install
for a java7 or java8 execution environment. I've tried setting the java6 as the
workspace default, but, it still doesn't change the classpath in the launch
configuration. I'll keep working on this.
[~mmalina] are you able to replicate this in any way at all? Try to get a wildfly to start
with a java6. I'm unable to replicate, despite trying everything I can think of to
force it to have the wrong jre.
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
Affects Versions: 4.2.0.Beta3
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)