Community
Participate
Working Groups
Build Identifier: M-3.2.3-20101129083231 Some JUnits (the import operations for JEE 6 modules and JEE 5 modules without deployment descriptor) need Java SE 1.6 in order to run correctly. If they run with Java SE 1.5, they fail. The patch and zip file attached to this defect are for creating a new plugin with Java SE 1.6 as the required execution environment, and for moving the JUnits that require Java SE 1.6 to this new plugin. Reproducible: Always
Created attachment 184085 [details] New plugin with execution environment Java SE 1.6
Created attachment 184086 [details] Move tests to new plugin
Maybe this has already been discussed within your team, but I have to ask ... why move them? Why not move the whole test suite to require Java 6? We've been using Java 6 to run our JUnit tests for some time now ... 2 years? ... and moving forward, Java 6 will be more officially minimum runtime level.
My two cents - we should have three different plugins with three different required JREs - all of the J2SE-1.4 through J2SE-1.6 - for running each of the different types of tests. The J2SE level would match the Java EE level. However, I would also be fine with moving all of the tests up to require J2SE-1.6. The important part is that the Java EE 6 tests need J2SE-1.6
I vote for this plugin at this time. Our requirements dictate that we run in backlevel java for most of our tests because the majority of our customers run in older legacy servers with Java 5 etc.... For now - having a separate java 6 test plugin for newer tests/scenarios makes sense to run them emulating the customer environment.
Created attachment 184148 [details] Move tests to new plugin and add new plugin to wtp test feature New patch to include the new plugin into the WTP test feature
approve
Created attachment 184677 [details] The sourceediting feature change
Since the org.eclipse.jst.web_tests.feature is in sourceediting, we will need to involve the sourceediting team
The new plugin has been created and Roberto's initial patch is now committed/released to both R3_2_maintenance and HEAD for WTP 3.2.3 and WTP 3.3. The sourceediting feature change still needs to be committed/released, so I am transferring this bug to them.
Attachment 184677 [details] release released to 3.2.3.
And to 3.3.
As per Nitin's previous comments, the test feature patch was committed/released to both R3_2_maintenance and HEAD for WTP 3.2.3 and WTP 3.3.