Community
Participate
Working Groups
Steps to reproduce: use glassfish or jboss server. 1. create ejb project 1.4 or 3.0 2. create a session bean 3. add ejb project to ear (note that export jar works ok) 4. try to deploy the enterprise application. 5. go and check the jar in eclipse temp folder or on server deploy server. inside the archive are only java files no class files.
build M-3.0.1-20080808153942
the problem seems to be in wst.server plugins... I will keep investigating.
found the problem it was caused by the fix of bug 237141
Created attachment 109936 [details] proposed patch This passed our adopter tests, but exposed a problem in WTP only. We are adding a junit to cover this. The problem was that the contents of the source folder rather than the output folder were copied to the server.
* 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. It breaks deployment to servers. Note, SAP marked this as blocker. * Is there a work-around? If so, why do you believe the work-around is insufficient? No workaround available * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? This has been tested in the adopter product. We are also adding a wtp junit test. * Give a brief technical overview. Who has reviewed this fix? The problem was that the contents of the source folder rather than the output folder were copied to the server. * What is the risk associated with this fix? Low
Created attachment 109945 [details] new junit This test will catch this failing issue
approve - tested with new junit
Thanks for the JUnit and fix. It does seem relatively safe and is a true blocker, so we do need to fix.
just tested the patch works great.
Committed to R3_0_maintenance for 3.0.1
tested with M-3.0.1-20080815211125