Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.2
-
Fix Version/s: 2.2.1
-
Component/s: None
-
Labels:None
-
Patch Submitted:Yes
-
Number of attachments :
Description
The actual behaviour of the ejb mojo is that if excluding something from the ejb (server side), ejb-jar.xml is not excluded anymore. As it's not excluded anymore, it appears twice in the archive (once because added as the deployment descriptor file, and twice because is present in the output dir).
Please note that the actual version of test org.apache.maven.plugin.ejb.EjbMojoTest.testMainJarExclusions() should not pass because of the problem reported.
I suggest changing the behaviour of the exclusion mecanism so that ejb-jar.xml is always "excluded" so that it only appears once in the jar (see provided patch).
Fixed in r924415. Thanks for the patch but I opted to only exclude the ejb-jar.xml automatically rather than all the default excludes. Otherwise, users won't be able to override the defaults.