[MASSEMBLY-395] Module dependencies not included

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2-beta-3
• Fix Version/s: 2.5.1
• Component/s: moduleSet
• Environment: Maven version: 2.0.9; Java version: 1.5.0_09; OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
• Assignee: Kristian Rosenvold
• Reporter: Jaan Vajakas
• Created: 26/Feb/09 07:33
• Updated: 25/Nov/14 11:45
• Resolved: 04/Nov/14 00:20

Description

Maven assebly plugin 2.2-beta-3 does not include module dependencies, even when the explicit <includeDependencies>true</includeDependencies> is used in assembly descriptor. Maven assebly plugin 2.2-beta-2 did not have this issue.

See the attached project: running mvn package for the parent project my-app creates a ZIP that contains only my-app-module1-1.0-SNAPSHOT.jar. If assembly plugin 2.2-beta-2 is used (i.e. if one replaces 2.2-beta-3 with 2.2-beta-2 in pom.xml of my-app) then the ZIP also contains my-app-module2-1.0-SNAPSHOT.jar and junit-3.8.1.jar.

Issue Links

• is duplicated by: MASSEMBLY-582 Plugin omits transitive runtime dependencies where artifact is present with test-scope in current project
• is related to: MASSEMBLY-727 Implied dependencysets have incorrect outputfilemapping
• relates to: MASSEMBLY-558 Assembly does not include runtime-dependency if test-dependency with shorter path exists