[MWAR-9] WAR plugin should support minimal WARs for inclusion within an EAR

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Assignee: Unassigned
• Reporter: Mike Perham
• Created: 27/Sep/05 10:02
• Updated: 18/Nov/11 07:24
• Resolved: 18/Nov/11 07:24

Description

I noticed that when I build a WAR, I get a gigantic WEB-INF/lib with all my deps. This is fine for a default but maven should also support "skeleton" WARs which will be packaged within an EAR. We have EARs which package 3-4 WARs each and to have the deps duplicated within each WAR means we cannot have shared data (since the classes are loaded within each WAR's classloader, rather than by the parent EAR's classloader). It also means 80MB EARs!

It seems like two things need to happen:

1) Add a "skeleton" flag which prevents copying any dependencies to WEB-INF/lib.
2) Instead generate a META-INF/MANIFEST.MF which has a Class-Path entry which lists the relative locations of the dependencies within the parent EAR.

Fabrice has basically the same idea written down here. Starting with "- for a War..." : http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112737860024530&w=2

Issue Links

• is related to: MECLIPSE-167 .component assumes all dependencies should be packaged in WAR
• is related to: MEAR-60 Improve support for skinny war files
• is related to: MEAR-17 Jar files packed in the EAR file should also be added to application.xml or manifest.mf
• relates to: MWAR-21 Need a way to include limited set of webapp's dependencies