finalName of artifacts not in the reactor is not taken into account.
--------------------------------------------------------------------
Key: MDEP-208
URL: http://jira.codehaus.org/browse/MDEP-208
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: copy-dependencies, unpack-dependencies
Affects Versions: 2.0
Reporter: Maarten Billemont
Assignee: Brian Fox
Setting:
A project where module B has a dependency on module A.
Module B uses copy-dependencies to copy that dependency into a certain
directory.
What works:
When both module A and B are in the maven reactor, module A's finalName is
taken into account and the artifact that ends up copied into our directory uses
the filename as given by finalName.
What doesn't work:
When only module B is in the maven reactor, module A is copied from the local
repository where it has a different filename. Maven-dependency-plugin does not
correct the filename during copy and as a result we have an artifact in our
destination directory with a different name.
This behavior is inconsistent and a solution should be established. I propose
maven-dependency-plugin reads the dependency (A)'s POM and checks whether it
has a finalName set. If so, it should modify the destination filename of the
dependency copy operation accordingly.
--
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
