[ http://jira.codehaus.org/browse/MASSEMBLY-14?page=all ] Kenney Westerhof reopened MASSEMBLY-14: ---------------------------------------
There are some major issues with this commit (revision 327855). The only way to run the assembly plugin in a reactor is to bind it to the lifecycle of some pom. If you're not interested in ALL modules and ALL dependencies, but for instance, you use the assembly plugin to create an artifact in a submodule somewhere, all modules and all dependencies of them end up in that assembly. Example: root/pom.xml, define moda and modb moda/pom.xml, depend on X modb/pom.xml, depend on Y, declare assembly then root/modb/target/... contains moda.jar, modb.jar, X.jar and Y.jar. I'm sure that that's not what's intended. I think this can be easily resolved by only considering child modules of the current pom. I find it strange that this wasn't tested in a reactor environment, since that's the only way to test this patch. > assembly plugin does not include dependencies for all artifacts in reactor. > --------------------------------------------------------------------------- > > Key: MASSEMBLY-14 > URL: http://jira.codehaus.org/browse/MASSEMBLY-14 > Project: Maven 2.x Assembly Plugin > Type: Bug > Reporter: Erick Dovale > Assignee: Edwin Punzalan > Attachments: MNG-1206-maven-assembly-plugin.patch, test-assembly-m2.zip > > > When trying to create an archive using maven-assembly-plugin the dependencies > for the artifacts in the reactor are not added to the archive. > attached is a whole project structure that can be used to reproduce this > issue. -- 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
