[
http://jira.codehaus.org/browse/MDEP-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107881
]
Brian Fox commented on MDEP-114:
--------------------------------
I don't see any possible why that running from the parent would include _more_
dependencies than in a module. The only way this is happening is if maven is
recursing and you are copying to an absolute path thus the effect is each
module copies its own dependencies to the same place.
You can use the dependency:copy and list only the modules you want and there
are excludes/includes options to help filter the copy-dependencies (including
transitivity)
> 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
