[jira] [Commented] (MWAR-220) dependencyManagement && overlay + transitive dependency = multiple versions of same dependency in WEB-INF/lib
[ https://issues.apache.org/jira/browse/MWAR-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16999108#comment-16999108 ] Elliotte Rusty Harold commented on MWAR-220: probably still an issue > dependencyManagement && overlay + transitive dependency = multiple versions > of same dependency in WEB-INF/lib > - > > Key: MWAR-220 > URL: https://issues.apache.org/jira/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 >Priority: Major > 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 (v8.3.4#803005)
[jira] [Commented] (MWAR-220) dependencyManagement && overlay + transitive dependency = multiple versions of same dependency in WEB-INF/lib
[
https://issues.apache.org/jira/browse/MWAR-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15684836#comment-15684836
]
Michael Osipov commented on MWAR-220:
-
This can't and won't work if you take a look how overlays are
[implemented|https://github.com/apache/maven-plugins/blob/trunk/maven-war-plugin/src/main/java/org/apache/maven/plugins/war/packaging/OverlayPackagingTask.java].
WARs are opaque ZIPs files, all operations happen on a file basis and not on
artifacts and dependencies. At that point, dependency mediation is long over. A
probably good solution would read the POM from the WAR, build the dependency
tree, match against current project and produce a new {{WEB-INF/lib}} listing.
A busload of work. Working with file excludes is the only reasonable workaround
for now.
> dependencyManagement && overlay + transitive dependency = multiple versions
> of same dependency in WEB-INF/lib
> -
>
> Key: MWAR-220
> URL: https://issues.apache.org/jira/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.3.4#6332)
[jira] [Commented] (MWAR-220) dependencyManagement && overlay + transitive dependency = multiple versions of same dependency in WEB-INF/lib
[ https://issues.apache.org/jira/browse/MWAR-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15684491#comment-15684491 ] Sandra Parsick commented on MWAR-220: - Reproducable with Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) and Maven-War-Plugin version 3.0.0 > dependencyManagement && overlay + transitive dependency = multiple versions > of same dependency in WEB-INF/lib > - > > Key: MWAR-220 > URL: https://issues.apache.org/jira/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.3.4#6332)
