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

Dennis Lundberg commented on MEAR-60:
-------------------------------------

The patch from Jeroen and Eric was applied with modifications and the addition 
of an IT in 
[r1210910|http://svn.apache.org/viewvc?view=revision&revision=1210910].

In [r1210930|http://svn.apache.org/viewvc?view=revision&revision=1210930] I 
added the paramter to enable skinnyWars together with another IT.

I'll also add some examples in the documentation showing how it is used and 
what it does in more detail. 

A new 2.7-SNAPSHOT has been deployed. It would be great if we could get some 
reports on how this works for everyone who has voted on this issue.

> Improve support for skinny war files
> ------------------------------------
>
>                 Key: MEAR-60
>                 URL: https://jira.codehaus.org/browse/MEAR-60
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.3
>         Environment: mvn 2.0.5
>            Reporter: Marcel Schutte
>            Priority: Critical
>         Attachments: maven-ear-plugin-MEAR-60.patch
>
>
> Provide a boolean configuration option for webModules to include the war's 
> transitive dependencies.
> As described on 
> http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html it 
> is very common in a J2EE environment to use so called skinny wars. Here the 
> war's WEB-INF/lib will not contain the dependent jars, but instead they are 
> packaged inside the EAR. The war references them through its 
> META-INF/MANIFEST.MF
> This option could be used to avoid the 'painful part' mentioned in the above 
> web page. The war's dependencies wouldn't have to be duplicated alongside the 
> ear's.
> I also found an old issue (MEAR-14) which has asked for the current default 
> behavior of not including the transitive dependencies. It suggests a property 
> to include specific dependencies of the war. As far as I can tell this has 
> never been implemented and this is also not what I am asking for. My proposal 
> is an all of nothing kind of option for each war module in the ear.
> On a side note, for me this is the part where removal of the old maven 1 
> style properties per dependency is missed the most. With them it was possible 
> to decide for each single dependency whether to put it in WEB-INF/lib or 
> reference it through the manifest classpath. But of course, then we didn't 
> have the transitive dependencies

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to