[MWAR-294] Unwanted transitive dependencies added to the WAR with dependency management and Maven 3.

• Type: Bug
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.1.1, 2.3
• Fix Version/s: more-investigation

Environment

Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: /opt/apache-maven-3.0.4
Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-43-generic", arch: "i386", family: "unix"

• Assignee: Unassigned
• Reporter: Marc Rohlfs
• Created: 02/Oct/12 05:51
• Updated: 11/Oct/18 08:59

Description

With Maven 3, unwanted libraries are added to the WEB-INF/lib folder of the packed web app in a multi-module build if:

• The WAR module has a JAR dependency with provided scope.
• The POM of the WAR module (or its parent POM) has a dependencyManagement section that defines the transitive dependencies of the JAR module.
• The dependencies in the dependencyManagement section are not defined as dependencies of the WAR module.
• The dependencies in the dependencyManagement section explicitly define compile or runtime scope.

This leads to unwanted dependencies in the packaged web app or even duplicate dependencies when using overlays.

When running the build with Maven 2.2.1, it works fine and doesn't add those unwanted dependencies to the web app.

Issue Links

• links to: MWAR-294 sample project on GitHub