jira-importer opened a new issue, #170:
URL: https://github.com/apache/maven-war-plugin/issues/170

   **[Mike 
Perham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mperham)** 
opened 
**[MWAR-9](https://issues.apache.org/jira/browse/MWAR-9?redirect=false)** and 
commented
   
   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
   
   
   ---
   
   **Attachments:**
   - 
[AbstractWarMojo.patch](https://issues.apache.org/jira/secure/attachment/12720627/AbstractWarMojo.patch)
 (_10.77 kB_)
   
   **Issue Links:**
   - [MWAR-21](https://issues.apache.org/jira/browse/MWAR-21) Need a way to 
include limited set of webapp's dependencies
   
   - [MECLIPSE-167](https://issues.apache.org/jira/browse/MECLIPSE-167) 
.component assumes all dependencies should be packaged in WAR
   
   - [MEAR-60](https://issues.apache.org/jira/browse/MEAR-60) Improve support 
for skinny war files
   
   - [MEAR-17](https://issues.apache.org/jira/browse/MEAR-17) Jar files packed 
in the EAR file should also be added to application.xml or manifest.mf
   
   
   59 votes, 37 watchers
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to