[jira] Commented: (MASSEMBLY-97) multiproject with assembly fails in mysterious ways
[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=comments#action_78321 ] Bugittaa Pahasti commented on MASSEMBLY-97: --- There is no equivalent target for directory task. directory-inline is similar like attached, which means that to completely workaround this bug would require yet another task directory-single. 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 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
[jira] Commented: (MASSEMBLY-97) multiproject with assembly fails in mysterious ways
[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=comments#action_67154 ] David Boden commented on MASSEMBLY-97: -- I have worked around this by using single as the goal rather than assembly. The single goal has been added as a workaround for this issue until the maven core can provide better multi-project support. This works for me: plugin artifactIdmaven-assembly-plugin/artifactId executions execution phasepackage/phase goals goalsingle/goal /goals /execution /executions configuration archive manifestFileMETA-INF/MANIFEST.MF/manifestFile /archive descriptors descriptor../SSBuild/bundle-assembly.xml/descriptor /descriptors /configuration /plugin 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
[jira] Commented: (MASSEMBLY-97) multiproject with assembly fails in mysterious ways
[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=comments#action_65449 ] Bugittaa Pahasti commented on MASSEMBLY-97: --- Still occurs with assembly 2.1final. 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
[jira] Commented: (MASSEMBLY-97) multiproject with assembly fails in mysterious ways
[ 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
