[ 
https://jira.codehaus.org/browse/MWAR-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282456#comment-282456
 ] 

Nicolas Marcotte commented on MWAR-9:
-------------------------------------

As a maven user and in house plugins developer I wholeheartedly agree. However 
i would still like to see my updated test and documentations for MWAR-81 
included as a stop gap measure. 

If my last patch to MWAR-81 is included I can document it on the cited wiki, 
tell the readers to subscribe to MEAR-60 and MEAR-87 for a correct solution  
while using MWAR-81 while we wait while proper patch is developed. 

However, I won't update the wiki if MWAR-81 is not included because if there 
are no test nor documentation on that functionality, it can disappear in any 
future release and it is a behaviour that would I dislike to see as a maven 
user and evangelist ^1^ !

# I may have drunk to much Koolaid but,hey!, your maven Koolaid taste so good.


> WAR plugin should support minimal WARs for inclusion within an EAR
> ------------------------------------------------------------------
>
>                 Key: MWAR-9
>                 URL: https://jira.codehaus.org/browse/MWAR-9
>             Project: Maven 2.x WAR Plugin
>          Issue Type: Improvement
>            Reporter: Mike Perham
>            Assignee: Stephane Nicoll
>             Fix For: 2.2
>
>         Attachments: AbstractWarMojo.patch
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to