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

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-21606:
-------------------------------------

I must be using an early build of eap 6.4.   From a mailing list thread:

Per the EAP supported configurations page [1],  the user can only use EAP 6.3.2 and below if they are using Oracle or IBM Java 1.7.  If they are using OpenJDK Java 1.7, then they can run up to EAP 6.4.

[1] https://access.redhat.com/articles/111663

So at the very least, eap 6.4 requires Java7. 

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