[MDEP-208] finalName of artifacts not in the reactor is not taken into account.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.2
• Component/s: copy-dependencies, unpack-dependencies
• Assignee: Brian E Fox
• Reporter: Maarten Billemont
• Created: 10/Apr/09 07:31
• Updated: 10/Mar/16 13:50
• Resolved: 14/Jul/11 02:35

Description

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.