[MEAR-153] Skinny Modules -- not just WARs

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7
• Fix Version/s: 3.2.0
• Labels: contributers-welcome
• Flags: Patch
• Assignee: Unassigned
• Reporter: Roland Asmann
• Created: 06/Jul/12 06:43
• Updated: 20/Dec/20 09:41
• Resolved: 06/Dec/20 18:08

Description

Currently it is only possible to have the plugin filter WARs to make them 'skinny', however this could be very useful for other modules as well!

In my project I have both a WAR and a SAR that should share several libraries. As standalone artifacts, they should both package it themselves, but in the deployed EAR I get classloading-errors when they don't have the libs shared in the EAR.

I traced a solution to the method 'EarModule.getLibDir()', which is only implemented with a value in the 'WebModule'-subclass.
Since I am not familiar with all the module-types, I attached a solution that ONLY handles the SarModule, but this can probably used in all other Modules that contain libs as well.

Issue Links

• fixes: MEAR-267 assembly.xml contains incorrect references to modules
• is related to: MRAR-9 Avoid to bundle rar dependencies (w/o scope=provided) inside the rar archive
• links to: "Maven EAR Plugin 3.2.0 with skinnyModules option" topic in the [e-mail] mailing list
• links to: GitHub Pull Request #24