[MASSEMBLY-97] multiproject with assembly fails in mysterious ways

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Won't Fix
• Affects Version/s: 2.1
• Assignee: John Dennis Casey
• Reporter: nigel magnay
• Created: 10/May/06 05:16
• Updated: 31/Jan/15 13:41
• Resolved: 27/Oct/06 00:34

Description

The attached project has a (very simple) multiproject build.

If you edit the root pom.xml and comment out project2, then "mvn install" will execute correctly and build and assemble the jar files, and deploy them to the local repo.

If you have both project1 and project2, then something odd happens - it fails building the package for item1, but the error report is that there is a missing dependency for item2's package - which it hasn't built yet.

This means that 'root level' builds for us can't be executed from a clean system as they always fall over.

Issue Links

• is duplicated by: MASSEMBLY-102 'attached' goal bound to 'package' phase not working in a multiproject environment when having dependency between its modules