[
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MDEP-451.
------------------------------------
Resolution: Not A Bug
Assignee: Karl-Heinz Marbaise
The reason for your breakage is the update of Maven without pinning the
versions of the plugins in your poms. You can solve that by defining the
appropriate steps in your pom which can be activated by a profile.
Apart from that changing the behaviour of an existing goal for an extremly
unusal use case is not a good idea. So could you create a separate JIRA with
this request with a link to this jira so i can close this issue cause it is not
a regression nor something is going wrong. It works as designed.
> 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)
