Community
Participate
Working Groups
We need to remove the partial Java EE 8 support from the JavaEEProjectUtilities.getLatestVersion() function, as this has caused a serious regression in components that access it. This is due to incomplete Java EE 8 support throughout the rest of WTP Java EE Tools, which has not yet been committed (See Bug 518383).
New Gerrit change created: https://git.eclipse.org/r/105645
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. Adopters are running into NPEs and other exceptions due to issues exposed by partial Java EE 8 functionality. Is there a work-around? If so, why do you believe the work-around is insufficient? There is no work-around. How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? The fix has been tested in the adopter code and fixes the issue. Give a brief technical overview. Who has reviewed this fix? As part of the partial Java EE 8 update, the default Java EE version for undefined instances was raised to Java EE 8. We are reverting the default Java EE version back to Java EE 7. Carl Anderson, Chuck Bridgham, and Elson Yuen have reviewed this fix. What is the risk associated with this fix? Extremely low risk- we are reverting back to well-tested functionality from Oxygen
Note that both WTP PMC and Eclipse PMC approval will be needed to get this change into WTP 3.9.1a
Gerrit change https://git.eclipse.org/r/105645 was merged to [master]. Commit: http://git.eclipse.org/c/jeetools/webtools.javaee.git/commit/?id=a105b38d37fcff16dcb04d46285a55f61a2cb4bf
Committed to master for WTP 3.9.1a and WTP 3.10.0 M3