[MDEP-2] Sibling Dependency Not Included in copy-dependencies output during multi-project build

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-alpha-1
• Assignee: kenneyw
• Reporter: Stephen Charles Duncan, Jr.
• Created: 07/Feb/06 18:35
• Updated: 11/May/06 12:25
• Resolved: 11/May/06 11:43

Description

Using the following structure

dependency-test

• module1
• module2

I have the dependency-maven-plugin:copy-dependencies goal attached
the package phase of the module2 module.

"module2" has a dependency on "module1". When I run "mvn package" from the
"module2" folder, it correctly includes the "module1" jar in the
target/dependency folder.

When I run "mvn package" from the "dependency-test" folder, the "module1" jar is
not included in the impl/target/dependency folder.

A simple example of the problem is attached.

Issue Links

• duplicates: MDEP-1 multi-module builds don't unpack-dependencies with dependency-maven-plugin:1.0