[
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=352346#comment-352346
]
Lenny Primak commented on MDEP-451:
-----------------------------------
This is not accurate. I am pinning the plugin versions in my POM files,
While your argument may be correct that it may be interpreted that it works as
designed, I don't see anything in the plugin documentation suggesting so.
For my project, it is a regression, because all I did is update maven with
correctly designed Pom files. This bug makes dependency:copy completely
useless to me.
This may not be an unusual case anyway because if you want to gather all the
dependencies in a multi-module project this is the only way I can see how to do
it.
Nevertheless I will open a new issue as you suggested.
> Regression: mvn dependency:copy doesn't run under maven 3.x multi-module
> project
> --------------------------------------------------------------------------------
>
> Key: MDEP-451
> URL: https://jira.codehaus.org/browse/MDEP-451
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: copy
> Affects Versions: 2.8
> Environment: All
> Reporter: Lenny Primak
> Assignee: Karl-Heinz Marbaise
> Priority: Critical
> Attachments: deptest.tar
>
>
> I have a muldi-module project,
> running mvn dependency:copy on root project just runs
> on root project without recursing into the modules.
> This works under maven 3.0.3 but doesn't run at all in the
> current 3.2.2 version of maven
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
