[ https://issues.jboss.org/browse/JBIDE-18700?page=com.atlassian.jira.plugi... ] 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. -- This message was sent by Atlassian JIRA (v6.3.8#6338)