[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=13261630#comment-13261630 ] 

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

After reviewing the redhat access document, it's clear that creating a separate runtime type for eap6.4 is unfeasible. The common intended JRE for EAP 6.1+ is basically java7. All are guarenteed to work for java7, so I'll bump the default for all EAP 6.1+ to use java7 by default. 

But making java 8 the default for these types is simply not feasible because the default execution environment is set before the user gets a chance to set the runtime home directory. So we really have no ability to figure this out in advance. 

On the other hand, once the user types in a home directory, I think it'd be a bit jarring if we started changing the selected execution environment based on what was typed in the runtime home directory field. 

So...  I'm closing this as partially complete. It's not the best result but it's what we can do. 

> 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.1.AM2
>
>
> 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)