[MDEP-776] copy-dependencies overwrites artifacts of the same artifact id

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.1.2, 3.2.0
• Component/s: copy-dependencies
• Assignee: Elliotte Rusty Harold
• Reporter: Nikolaos Georgiou
• Created: 05/Nov/21 11:23
• Updated: 2 days ago 12:01

Description

We have a project which has 2 dependencies of different groupId but same artifactId and version, e.g. com.acme:foo:1.2.3 and com.ecorp:foo:1.2.3

We use the copy-dependencies goal of the plugin to copy libraries under target/lib folder.

Actual Result:

• only one foo.jar survives in the target/lib folder. The other one silently gets overwritten. This leads to difficult to diagnose runtime errors, as one JAR is missing.

 

Expected Result:

• it should at least give a warning, if not an error, that it has overwritten an artifact during this process

 

Known workaround:

• we activated useRepositoryLayout, which allows both artifacts to survive under a directory structure, which complicates a bit our classpath building process (from target/lib/* we need to find all the JARs with a bit of bash glue)

 

Issue Links

• relates to: MDEP-772 "failOnDuplicates" option for "unpack" goal
• links to: GitHub Pull Request #463