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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Assignee: Brian E Fox
• Reporter: Matt Brozowski
• Created: 02/Aug/06 15:00
• Updated: 10/Mar/16 13:51
• Resolved: 27/Oct/06 07:19

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-44 unpacking/copying of attached artifacts from reactor projects doesn't work