You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Tran (JIRA)" <ji...@codehaus.org> on 2006/05/11 18:58:41 UTC
[jira] Commented: (MDEP-2) Sibling Dependency Not Included in
copy-dependencies output during multi-project build
[ http://jira.codehaus.org/browse/MDEP-2?page=comments#action_65204 ]
Dan Tran commented on MDEP-2:
-----------------------------
Kenney, i think you patch it to the wrong place. the plugin has been moved to maven-dependency-plugin at Apache
> Sibling Dependency Not Included in copy-dependencies output during multi-project build
> --------------------------------------------------------------------------------------
>
> Key: MDEP-2
> URL: http://jira.codehaus.org/browse/MDEP-2
> Project: Maven 2.x Dependency Plugin
> Type: Bug
> Reporter: Stephen Duncan Jr
> Assignee: Kenney Westerhof
> Fix For: 1.1
> Attachments: dependency-test.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