Community
Participate
Working Groups
In bug 252613, we added in the various Java EE 6 facets. All of them currently have the following line in their Java EE 6 version definition: <requires facet="jst.java" version="[5.0"/> The Java EE version should match the Java version. (Java Enterprise Edition 6 is Java 6 Standard Edition plus Enterprise Edition support.)
Created attachment 168523 [details] patch Simple patch that does the changes suggested by Carl.
Chuck, please approve this simple fix for RC2.
approve
* Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. This is not a stop-ship defect, but users can easily end up with Java EE 6 projects created with Java 5 facets. Since Java EE 6 require Java 6 (because some of the Java EE libraries moved down to Java SE), then this can result in missing Java EE libraries in the project's classpath. * Is there a work-around? If so, why do you believe the work-around is insufficient? The workaround is that users change the Java facet version from 5 to 6 during the project creation. But this is not an obvious thing for the general user. * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Manually tested. The validation of the facet framework shows error if the constraint is not satisfied. * Give a brief technical overview. Who has reviewed this fix? Changed is the minimum required version of the jst.java facet from 5.0 to 6.0 for the Java EE 6 facets. This is a change done completely in the plugin.xml descriptors. * What is the risk associated with this fix? No risk.
Committed and released.
Closing