[
http://jira.codehaus.org/browse/MDEP-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107871
]
Brian Fox commented on MDEP-114:
--------------------------------
Not sure i follow. that mojo gets the dependency list from the maven
interpolated project. A parent should have less dependencies than the others
because it will not include the ones from the child modules. However, running
mvn from the parent will cause maven to naturally iterate through all children.
If you don't want that, then you need to use the -N flag.
> Copy Dependencies does not have project dependency isolation
> ------------------------------------------------------------
>
> Key: MDEP-114
> URL: http://jira.codehaus.org/browse/MDEP-114
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: copy-dependencies
> Affects Versions: 2.0-alpha-4
> Reporter: Cameron Jones
> Assignee: Brian Fox
>
> In a multi-module project the copy-dependencies goal gets the list of
> dependencies from the project and not the individual modules. This has the
> effect that if the task is run from a module it has only that module's
> dependencies copied, however if run from the parent the entire project's
> dependencies are copied.
--
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
