[
https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-21606:
-------------------------------------
As was mentioned on the call:
1) Choosing the highest allowed exec-env is not a good idea. Java9 will probably break
this.
2) The lower-bound exec-env is set by runtime-type. Since eap6.4 shares a runtime type
with eap 6.1, we can't simply raise it.
3) It'd be best if we could set the default execution environment based on details of
the server home (ie introspect the runtime to see what actual version is there)... so
I'll see if I can fix it along this path.
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.Alpha3
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)