[jbosstools-issues] [JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198102#comment-13198102 ] 

Fred Bricon edited comment on JBIDE-21606 at 4/27/16 6:46 PM:
--------------------------------------------------------------

What is actually needed here is a validation mechanism that detects the server module' compilation level matches the Server's actual JDK, regardless of the minimum Facet supported by said server.
eg:
- module compiled with Java 7, EAP 6.x running with Java 6 : Error
- module compiled with Java 7, EAP 6.x running with Java 7+ : No problem

That really sounds like an upstream problem


was (Author: fbricon):
What is actually needed here is a validation mechanism that detects the server module' compilation level matches the Server's actual JDK, regardless of the minimum Facet supported by said server.
eg:
- module compiled with Java 7, EAP 6.x running with Java 6 : Error
- module compiled with Java 7, EAP 6.x running with Java 7+ : No problem

That really sound like an upstream problem

> 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)