[
https://jira.codehaus.org/browse/MEAR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285334#comment-285334
]
Andreas Thaler commented on MEAR-60:
------------------------------------
Hi Dennis,
I would prefer to see the problem solved rather than documented as the
workaround involves custom code. Without the workaround the skinnyWar issue is
not solved from my perspective..
However here my solution with which it is working fine for me:
I created a jar containing a single java file implementing the FileNameMapping
interface. The implementation uses Artifact.getVersion() instead of
Artifact.getBaseVersion() used in AbstractFileNameMapping. So the libs placed
to the ear will have the same file name as in the war and duplicates will be
detected. I attached the jar to this issue.
At the plugin configuration the fileNameMapping property must be configured to
the custom file in the new jar. Furthermore the dependency to the jar must be
configured at the plugin.
{code}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<version>2.7-SNAPSHOT</version>
<configuration>
<!-- Custom FileNameMapping provided in additional jar to use
unique
timestamp version for jars, otherwise duplicated jars
will not be recognized -->
<fileNameMapping>de.hybris.maven.VersionFileNameMapping</fileNameMapping>
<skinnyWars>true</skinnyWars>
<defaultLibBundleDir>lib</defaultLibBundleDir>
</configuration>
<dependencies>
<dependency>
<groupId>de.hybris.maven</groupId>
<artifactId>maven-ear-plugin-addon</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
</dependencies>
</plugin>
{code}
Thanks for bringing this whole story to an end,
Andreas
> 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
> Assignee: Dennis Lundberg
> Priority: Critical
> Fix For: 2.7
>
> 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