[
https://jira.codehaus.org/browse/MWAR-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358084#comment-358084
]
Michael Osipov commented on MWAR-220:
-------------------------------------
Note: I had this issue years ago too. The problem is that entire WAR file is
taken as artifact. Packed atifacts are mere files. The depenency resolutoin
happens here. What you can do is to exclude the conflicting dependencies. This
is what I did as a workaround.
> dependencyManagement && overlay + transitive dependency = multiple versions
> of same dependency in WEB-INF/lib
> -------------------------------------------------------------------------------------------------------------
>
> Key: MWAR-220
> URL: https://jira.codehaus.org/browse/MWAR-220
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: overlay
> Environment: Reproduced this on: 2.0.11, 2.1.0, 2.2.1, 3.0-alpha-7
> Reporter: jieryn
> Attachments: pom.xml
>
>
> With dependencyManagement section defined I get multiple versions of spring
> libraries in target/cas-*/WEB-INF/lib after mvn package. If I remove the
> dependencyManagement section then only one version of the spring libraries
> are found.
> There seems to be a problem with m-war-p and overlays and
> dependencyManagement not using the maven GAV resolver in a proper way.. I
> attached a simple pom which exhibits the problem, just run mvn package to
> verify.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
