[jira] Closed: (MASSEMBLY-97) multiproject with assembly fails in mysterious ways

["John Casey (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MASSEMBLY-97?page=all ]

John Casey closed MASSEMBLY-97.
-------------------------------

      Assignee: John Casey
    Resolution: Won't Fix

Use assembly:single or assembly:directory-single for this type of application. directory-single is added in 2.2-SNAPSHOT

> multiproject with assembly fails in mysterious ways
> ---------------------------------------------------
>
>                 Key: MASSEMBLY-97
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-97
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>            Reporter: Nigel Magnay
>         Assigned To: John Casey
>            Priority: Critical
>         Attachments: bug-assembly-2.0.1.zip, bug-assembly-2.1-SNAPSHOT.zip, bug.zip
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira