[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=comments#action_67135 ]
David Boden commented on MASSEMBLY-97: -------------------------------------- The goals are fixed by *removing the @aggregator annotation* from the class documentation. For example, removing it from AssemblyMojo.java. The aggregator annotation implies that the plugin is only able to build the aggregator pom in a multi-project build. This is not the case. The assembly plugin can run on sub-projects. > multiproject with assembly fails in mysterious ways > --------------------------------------------------- > > Key: MASSEMBLY-97 > URL: http://jira.codehaus.org/browse/MASSEMBLY-97 > Project: Maven 2.x Assembly Plugin > Type: Bug > Versions: 2.1 > Reporter: Nigel Magnay > 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
