[ http://jira.codehaus.org/browse/MDEP-32?page=comments#action_71422 ] Matt Brozowski commented on MDEP-32: ------------------------------------
I have reopened this because it doesn't appear to be fixed in maven-dependency-plugin. I have revised the original test to use the maven-dependency-plugin and am attaching it. Matt Brozowski > -Sibling Dependency Not Included in copy-dependencies output during > multi-project build > --------------------------------------------------------------------------------------- > > Key: MDEP-32 > URL: http://jira.codehaus.org/browse/MDEP-32 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Reporter: Matt Brozowski > Assigned To: Kenney Westerhof > Fix For: 1.1 > > Attachments: dependency-revised.zip > > > Using the following structure > dependency-test > - module1 > - module2 > I have the dependency-maven-plugin:copy-dependencies goal attached > the package phase of the module2 module. > "module2" has a dependency on "module1". When I run "mvn package" from the > "module2" folder, it correctly includes the "module1" jar in the > target/dependency folder. > When I run "mvn package" from the "dependency-test" folder, the "module1" jar > is > not included in the impl/target/dependency folder. > A simple example of the problem is attached. -- 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
