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