[MDEP-44] unpacking/copying of attached artifacts from reactor projects doesn't work

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-alpha-1
• Fix Version/s: 2.0-alpha-3
• Assignee: Unassigned
• Reporter: Richard van der Hoff
• Created: 16/Oct/06 14:07
• Updated: 29/Aug/07 23:20
• Resolved: 20/Mar/07 22:31

Description

I have a parent project, which has two modules - "one" and "two".

"one" uses assembly:single to attach an assembly to its build.
"two" depends upon that assembly, and uses "dependency:unpack-dependencies" to unpack it.

This works fine if the projects are built separately - and the assembly is installed in the local repository. However, when using the reactor to build both projects at once, the dependency plugin still looks in the local repository for the assembly, rather than using the artifact which was just built. This either fails, or produces the wrong version of the assembly.

I suspect this may be a bug with the reactor mechanism - but I don't really understand how all that works...

The attachment demonstrates the problem.

Issue Links

• depends upon: MNG-2877 unable to resolve attached artifacts from reactor that are not in repo. (patch applied in svn and IT tests added)
• is duplicated by: MDEP-23 unpack-dependencies unpacks the wrong dependencies
• is duplicated by: MDEP-32 -Sibling Dependency Not Included in copy-dependencies output during multi-project build
• relates to: MDEP-64 Subprojects using m2 dependency plugin causes release:prepare to fail
• relates to: MDEP-106 Unpacking primary artifact from sibling module uses repository rather than reactor