Community
Participate
Working Groups
Build Identifier: WTP 3.2.1 Currently changes made to the 'Manifest Entries' table in the 'Manifest Entries' tab of the 'Deployment Assembly' properties page are being reverted on the first use of the 'Apply' button. Steps to reproduce: 1) Create an EAR 6 project with all default modules. 2) Go to the 'Manifest Entries' tab of the 'Deployment Assembly' properties page for the Web project. 3) Add a manifest entry to the EJB project and click 'Apply' (the changes are reverted; without closing the window, if you repeat the add and click 'Apply' the changes persist.) Reproducible: Always
Created attachment 173702 [details] Proposed Patch Patch fixes the issue by setting the previousManifest variable to the initial manifest file when the window is opened.
I approve - a simple, high quality fix for an ugly problem.
* 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. Currently changes made to the 'Manifest Entries' table in the 'Manifest Entries' tab of the 'Deployment Assembly' properties page are being reverted on the first use of the 'Apply' button when the window is opened. * Is there a work-around? If so, why do you believe the work-around is insufficient? No. * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Tested through UI. * Give a brief technical overview. Who has reviewed this fix? Patch fixes the issue by setting the previousManifest variable to the initial manifest file when the window is opened. Right now it thinks that there was no initial manifest file, so it clears the table to load the contents of the manifest file. Reviewed by Carl Anderson. * What is the risk associated with this fix? Low.
Committed to HEAD for WTP 3.2.1 and WTP 3.3