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

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

I'm a bit confused here.  I checked out the html5 project from central and the pom.xml has the following:

{code}
    <maven.compiler.target>1.6</maven.compiler.target>
    <version.jboss.maven.plugin>7.4.Final</version.jboss.maven.plugin>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <version.surefire.plugin>2.10</version.surefire.plugin>
    <version.org.eclipse.m2e>1.0.0</version.org.eclipse.m2e>
    <maven.compiler.source>1.6</maven.compiler.source>
{code}

So it seems it should be compiling with a class version of "50", which should be deployable on an eap using java6. 

[~mmalina] Can you help track down why it's behaving this way for you? 

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