[jira] Commented: (MEAR-60) Improve support for skinny war files

["Dennis Lundberg (JIRA)" <ji...@codehaus.org>]

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

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

Here's a status report.

I've managed to extract a patch from Eric's Github repo. It's applied locally and I have modified it so that all the current integration tests pass. There were two cases where the current ITs failed. A new integration test for skinny wars have been added.

This is a change that will affect many projects, and I feel that we should have a parameter in the EarMojo to enable this new functionality. It should be disabled by default, to preserve the current behavior. I suggest a boolean parameter called "skinnyWars".

What do you think?

> 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