The project facets for e.g. an EJB or a utility project offer the selection of the Java version. However, only 1.6 and 1.5 is available when using Eclipse 3.7.1, WTP 3.3.1, and JBossTools 3.3.0.M3.
Since Eclipse 3.7.1 supports Java 1.7, I'm wondering whether the limitation is caused by WTP or by JBossTools. Using the try/catch enhancements or the diamond operator for collections or ... would make a developer's life a little bit easier ;-)
I haven't tried the Java 7 support yet but WTP is the one providing the Java Facets thus my first guess is Web Tools limitation (which i'm surprised they put in/didn't fix if true ;(
You can check if its Web tools or jboss tools by creating a utility jar project without any jboss tools facets/features.
In any case share the link here if you get around to it - in any case i'll raise it on the WTP call this week to hear what the status is (assuming its webtools
I created an issue in our JIRA and we'll try to solve that issue:
If you have anything to add in sake of issue documentation, please feel free to do so
Max Rydahl Andersen wrote:
Just to let everyone know in case they see this thread - yes, we had listed jst.java facet requirements from 1.3-1.6 which caused this problem.
Its now fixed and M4 will have this fix in.
I'm running Eclipse 3.7.2 and JBoss Tools Beta 1, but it seems to have disappeared again.
It's not in the drop-down and if I manually change it in /.settings/org.eclipse.wst.common.project.facet.core.xml I get a problem in my markers view saying:
Project facet Java 1.7 is not supported by target runtime JBoss 6.x Runtime.
It would be nice if the fix that went into M4 can somehow be re-applied again in case it has disappeared. Otherwise, is there something special we need to do?
That seems to have been a complete fluke. Here's the patch that was added in m4: https://source.jboss.org/changelog/JBossTools?cs=35266
If you look at the patch (you don't have to), you can see every server except AS6 had the proper facet added....... oops? Seems I just skipped over as6 by accident. I'll make a jira and fix this.