[jbosstools-issues] [JBoss JIRA] (JBIDE-18700) EAP 6.x Configuration doesn't select Java 7 by default

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-18700:
-------------------------------------

So... it seems I could change the default facet for eap6.1+ to java 1.7, BUT,  since the user could technically be launching with java-6, this would confuse a bunch of users.... if they were able to make their web project with java 7 but not launch it with their pre-defined java-6 eap6.x

I'm not entirely sure this is the best choice... and so far I haven't found a  way to make sure the new dynamic web project wizard can default to web 3.0 and java 1.6  to remove the error. I honestly don't think it's possible without also removing support for web 3.1.  It seems they take the highest possible supported version of a given facet for a runtime type...  except where the default is different. 

> EAP 6.x Configuration doesn't select Java 7 by default
> ------------------------------------------------------
>
>                 Key: JBIDE-18700
>                 URL: https://issues.jboss.org/browse/JBIDE-18700
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Final
>            Reporter: Fred Bricon
>            Assignee: Rob Stryker
>             Fix For: 4.3.0.Alpha1
>
>
> - Create a new EAP 6.3 server
> - Create a new Dynamic Web Project
> - Select the EAP runtime
> => An error is shown : "Dynamic Web Module 3.1 requires Java 1.7 or newer."
> !http://content.screencast.com/users/fbricon/folders/Jing/media/ee20c272-5761-40ab-8fe8-1004533501c7/00000025.png!
> The EAP 6 Default Configuration should have the Java 1.7 Facet set by default.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)