[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-06 Thread Lenny Primak (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352419#comment-352419
 ] 

Lenny Primak commented on MDEP-451:
---

The reason copy-dependencies doesn't work for me is that i have specified
additional dependencies in artifactItems section and copy-dependencies does 
not listen to that element.

 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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-06 Thread Karl-Heinz Marbaise (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352420#comment-352420
 ] 

Karl-Heinz Marbaise commented on MDEP-451:
--

Please use the mailing list for discussion about it not JIRA.

 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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-06 Thread Lenny Primak (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352423#comment-352423
 ] 

Lenny Primak commented on MDEP-451:
---

I see I am getting major pushback from you.  
This is your right, but I would prefer more of a welcoming attitude,
I am just trying to contribute to the plugin, and all I am getting from you is 
defensive posture.
Believe me, I have spent a lot of time on this, I'd appreciate something 
besides no and can't or won't
or don't' do this.  I know how to read the documentation, sort through source 
code and google stuff.

In any case, you patch from above comments works (thank you!)
You obviously know what to do to fix this bug. 
In the meanwhile I will use a clone of the project.

This is critical for me to be fixed.



 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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-06 Thread Lenny Primak (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352424#comment-352424
 ] 

Lenny Primak commented on MDEP-451:
---

Assembly plugin doesn't work for me for the same reason copy-dependencies doen't

 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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-06 Thread Karl-Heinz Marbaise (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352425#comment-352425
 ] 

Karl-Heinz Marbaise commented on MDEP-451:
--

The welcoming attitude was there but you simply ignored several suggestions to 
do the discussion on the mailing where it belongs. 
Apart from that you are not contributing to the plugin you just try to force a 
particular change which sounds to me as the wrong way...there are better 
solutions which i had suggested. But i can't give you a really accurate 
suggestions cause i don't know the complete use case which you didn't described 
in contradiction to what i requested from you.
Furthermore you never described your complete use case and what you like to 
achieve.
To give you a no, don't or whatever for such a thing i need the full 
description of the use case which you didn't gave...

I have described why it is not usefull to integrate the patch to change the 
behaviour into your direction, cause it would break many builds and usages of 
the plugin which can't be done.
But the only thing you say is: change it it's important for me, but you haven't 
thought about the consequences for others.
My assumption is that you are going the wrong way with your build but you are 
not willing to discuss that nor are you willing to think about it and may be 
admit that it might give better way to solve your problem, but unfortunately i 
don't know your problem.



 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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-06 Thread Karl-Heinz Marbaise (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352425#comment-352425
 ] 

Karl-Heinz Marbaise edited comment on MDEP-451 at 9/6/14 2:52 PM:
--

The welcoming attitude was there but you simply ignored several suggestions to 
do the discussion on the mailing where it belongs. 

Apart from that you are not contributing to the plugin you just try to force a 
particular change which sounds to me as the wrong way...there are better 
solutions which i had suggested. But i can't give you a really accurate 
suggestion cause i don't know the complete use case which you didn't described 
in contradiction to what i requested from you.
Furthermore you never described your complete use case and what you like to 
achieve.
To give you a no, don't or whatever for such a thing i need the full 
description of the use case which you didn't gave...

I have described why it is not usefull to integrate the patch to change the 
behaviour into your direction, cause it would break many builds and usages of 
the plugin which can't be done.
But the only thing you say is: change it it's important for me, but you haven't 
thought about the consequences for others.
My assumption is that you are going the wrong way with your build but you are 
not willing to discuss that nor are you willing to think about it and may be 
admit that it might give better way to solve your problem, but unfortunately i 
don't know your problem.

And furthermore you continue to describe the designed behaviour as a bug which 
is simply wrong. It is the designed behaviour.

An other thing is you simple say: Assembly plugi doesn't work for me but you 
didn't write why ? So the realy point is you didn't describe you really like to 
achieve.


was (Author: khmarbaise):
The welcoming attitude was there but you simply ignored several suggestions to 
do the discussion on the mailing where it belongs. 
Apart from that you are not contributing to the plugin you just try to force a 
particular change which sounds to me as the wrong way...there are better 
solutions which i had suggested. But i can't give you a really accurate 
suggestions cause i don't know the complete use case which you didn't described 
in contradiction to what i requested from you.
Furthermore you never described your complete use case and what you like to 
achieve.
To give you a no, don't or whatever for such a thing i need the full 
description of the use case which you didn't gave...

I have described why it is not usefull to integrate the patch to change the 
behaviour into your direction, cause it would break many builds and usages of 
the plugin which can't be done.
But the only thing you say is: change it it's important for me, but you haven't 
thought about the consequences for others.
My assumption is that you are going the wrong way with your build but you are 
not willing to discuss that nor are you willing to think about it and may be 
admit that it might give better way to solve your problem, but unfortunately i 
don't know your problem.



 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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-06 Thread Lenny Primak (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352426#comment-352426
 ] 

Lenny Primak commented on MDEP-451:
---

The complete use case is described pretty well here:

http://code.google.com/p/flowlogix/wiki/TapestryLibrary#pom.xml:_if_you_are_running_in_Jetty_or_Tomcat,_brings_in_Glassf

 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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-05 Thread Karl-Heinz Marbaise (JIRA)

 [ 
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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-05 Thread Lenny Primak (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-05 Thread Lenny Primak (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352347#comment-352347
 ] 

Lenny Primak edited comment on MDEP-451 at 9/5/14 3:18 PM:
---

Make a dependency:copy-proj goal that is equivalent to dependency:copy but that 
works in multi- module project. 

Related issue: https://jira.codehaus.org/browse/MDEP-456


was (Author: lprimak):
Make a dependency:copy-proj goal that is equivalent to dependency:copy but that 
works in multi- module project. 

Related issue: https://jira.codehaus.org/browse/MDEP-451

 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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-05 Thread Karl-Heinz Marbaise (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352361#comment-352361
 ] 

Karl-Heinz Marbaise commented on MDEP-451:
--

If you like to gather all dependencies of your project dependency:copy is not 
intended for that. Than you should use dependency:copy-dependencies. Apart from 
that i don't konw what you exactly like to achieve. There is also a possibility 
to use maven-assembly-plugin via a a descriptor (dir format might be suitable) 
to gather all dependencies together or appassembler-maven-plugin 
(create-repository)...and may be other possibilies exist..So the best would 
be to completely describe what you like to achieve and may be post your pom 
files ...so i can help..but this should be done on the users mailing list...

 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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-05 Thread Lenny Primak (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352400#comment-352400
 ] 

Lenny Primak commented on MDEP-451:
---

Thanks for the suggestion. I tried copy-dependencies as well but it didn't work 
for me either. 

 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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-05 Thread Lenny Primak (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352401#comment-352401
 ] 

Lenny Primak commented on MDEP-451:
---

I will try assembly and will let you know

 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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-04 Thread Karl-Heinz Marbaise (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352321#comment-352321
 ] 

Karl-Heinz Marbaise commented on MDEP-451:
--

The fix for the problem is easy:
{code}
Index: 
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
===
--- 
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
(revision 1622302)
+++ 
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
(working copy)
@@ -37,7 +37,7 @@
  * @version $Id$
  * @since 1.0
  */
-@Mojo( name = copy, defaultPhase = LifecyclePhase.PROCESS_SOURCES, 
requiresProject = false, threadSafe = true  )
+@Mojo( name = copy, defaultPhase = LifecyclePhase.PROCESS_SOURCES, 
requiresProject = true, threadSafe = true  )
 public class CopyMojo
 extends AbstractFromConfigurationMojo
{code}

The problem is that dependency:copy goal is intended to work outside the life 
cycle and outside off the project context. So i don't see a chance to change 
the current behaviour. But what i could imagine is to create a separate goal 
like copy-with-project.

 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
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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-04 Thread Karl-Heinz Marbaise (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352321#comment-352321
 ] 

Karl-Heinz Marbaise edited comment on MDEP-451 at 9/4/14 5:10 PM:
--

The fix for the problem is easy:
{code}
Index: 
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
===
--- 
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
(revision 1622302)
+++ 
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
(working copy)
@@ -37,7 +37,7 @@
  * @version $Id$
  * @since 1.0
  */
-@Mojo( name = copy, defaultPhase = LifecyclePhase.PROCESS_SOURCES, 
requiresProject = false, threadSafe = true  )
+@Mojo( name = copy, defaultPhase = LifecyclePhase.PROCESS_SOURCES, 
requiresProject = true, threadSafe = true  )
 public class CopyMojo
 extends AbstractFromConfigurationMojo
{code}

The problem is that dependency:copy goal is intended to work outside the life 
cycle and outside off the project context. So i don't see a chance to change 
the current behaviour. But what i could imagine is to create a separate goal 
like copy-with-project.

Furthermore i have checked to run dependency:copy on the root of the project 
and i don't have any difference between Maven 2.2.1, 3.0.3, 3.0.5, 3.1.1, 
3.2.1, 3.2.2 and 3.2.3...in all versions the same behaviour. Have you allways 
specified the same version of maven-dependency-plugin ?


was (Author: khmarbaise):
The fix for the problem is easy:
{code}
Index: 
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
===
--- 
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
(revision 1622302)
+++ 
src/main/java/org/apache/maven/plugin/dependency/fromConfiguration/CopyMojo.java
(working copy)
@@ -37,7 +37,7 @@
  * @version $Id$
  * @since 1.0
  */
-@Mojo( name = copy, defaultPhase = LifecyclePhase.PROCESS_SOURCES, 
requiresProject = false, threadSafe = true  )
+@Mojo( name = copy, defaultPhase = LifecyclePhase.PROCESS_SOURCES, 
requiresProject = true, threadSafe = true  )
 public class CopyMojo
 extends AbstractFromConfigurationMojo
{code}

The problem is that dependency:copy goal is intended to work outside the life 
cycle and outside off the project context. So i don't see a chance to change 
the current behaviour. But what i could imagine is to create a separate goal 
like copy-with-project.

 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
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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-09-04 Thread Lenny Primak (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352327#comment-352327
 ] 

Lenny Primak commented on MDEP-451:
---

Yes, the maven dependency plugin version remained constant. 
The reason that I noticed the breakage is because my build started failing when 
upgrading maven, so the behavior definitely changed. 

I would gladly use a new goal if the change to existing one breaks things. 
Thanks 

 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
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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-08-11 Thread Lenny Primak (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351306#comment-351306
 ] 

Lenny Primak commented on MDEP-451:
---

Any updates on this issue?  Thanks

 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
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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-07-31 Thread Dan Tran (JIRA)

 [ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Tran updated MDEP-451:
--

Summary: Regression: mvn dependency:copy doesn't run under maven 3.x 
multi-module project  (was: Regression: mvn dependency:copy doesn't run under 
maven 3.2.2 multi-module project)

 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
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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-07-31 Thread Dan Tran (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350797#comment-350797
 ] 

Dan Tran commented on MDEP-451:
---

I am not sure if this is high priority since it breaks since 3.0.x

 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
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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-07-31 Thread Lenny Primak (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350798#comment-350798
 ] 

Lenny Primak commented on MDEP-451:
---

There are some other sideffects that make it work with 3.0.x,
but it breaks in my project since 3.1
i.e. I can't run my project with maven 3.1+




 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
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)


[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

2014-07-31 Thread Lenny Primak (JIRA)

[ 
https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350799#comment-350799
 ] 

Lenny Primak commented on MDEP-451:
---

I am hoping for a fix because it's a showstopper for me.
Thank you for working with me on this, whether you fix it or not.

 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
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)