[
http://jira.codehaus.org/browse/MWAR-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100366
]
Jason Melnick edited comment on MWAR-9 at 6/25/07 8:30 AM:
-----------------------------------------------------------
The all-or-nothing approach to WAR/EAR packaging isn't sufficient. Some jars
will need to be packaged in the war (like struts, for example) while others
(almost eveyrhting else) needs to be packaged in the EAR. The WAR's directions
(speficying deps as optional) will work with a patch.
I have a fix for this and will supply a patch ASAP.
See http://jira.codehaus.org/browse/MWAR-21 and
http://jira.codehaus.org/browse/MNG-3067
was:
I have a fix for this and will supply a patch ASAP.
See http://jira.codehaus.org/browse/MWAR-21 and
http://jira.codehaus.org/browse/MNG-3067
> WAR plugin should support minimal WARs for inclusion within an EAR
> ------------------------------------------------------------------
>
> Key: MWAR-9
> URL: http://jira.codehaus.org/browse/MWAR-9
> Project: Maven 2.x War Plugin
> Issue Type: Improvement
> Reporter: Mike Perham
> Assignee: Stephane Nicoll
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
