[
https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-21606:
-------------------------------------
I tested this in an environment that has j8, j7, and j6 installed.
When I use runtime detection, the server that gets created has an execution environment of
j6. When I launch the server, it is launched in via the java6 jre as well, so I know
there's no error there.
When I import the html5 project it has the java6 attached to it with the java6 compiler
settings. So... it seems both are taking the minimum allowed runtime environment. So if
your workspace has one of each, it seems impossible to get into a situation where the
project is compiled with j7 and the runtime targeting j6.... unless you add the j6
jre/jdk sometime after you import the html5 project?
Can anyone else confirm what i'm seeing?
Consider using java 8 for EAP 6.4 by default
--------------------------------------------
Key: JBIDE-21606
URL:
https://issues.jboss.org/browse/JBIDE-21606
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.1.Beta2
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.4.0.Alpha1
Here's the problem that I just hit:
I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project
from JBoss Central using the EAP 6.4 server as target runtime.
Then on the project, I just Run -> Run on Server.
The server started, but deployment failed on Unsupported version: 51.0
Which is a bit strange, because the server was running with java 6. But anyhow. It seems
the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6.
So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in
the past and there didn't seem to be any way to make something like this happen. But I
just wanted to present this use case and perhaps there is some possibility?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)