[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=comments#action_65377 ]
Bugittaa Pahasti commented on MASSEMBLY-97: ------------------------------------------- I'm seeing this too. It applies also to maven 2.0.4 with assembly plugin 2.0.1. I have attached a simplified example project based on the one submitted by Nigel Magnay. It demonstrates the bug with 3 modules only. The bug occurs when there are three modules in a reactor build (the simplest case): - the 1st module has assembly attached to package phase (assembly or attach goal) - the second module has dependency to module 1 - the third module has dependency to module 2 In this case the build fails. If the dependency in module 3 is changed to module 1, everything works as expected. This might be caused by a bug in some other component (dependency management?) as it seems to affect also some other plugins. I would really appreciate if someone would have time to take a look at this. Additionally, it would be really nice to have a release of the assembly-plugin, as the attached goal is really useful and using snapshot plugins is bit risky in a production build environment. > 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.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
