[jira] [Commented] (MDEP-776) copy-dependencies overwrites artifacts of the same artifact id

["Andreas Sewe (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MDEP-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482122#comment-17482122 ] 

Andreas Sewe commented on MDEP-776:
-----------------------------------

Seems almost like a duplicate of MDEP-772, although that is about the {{unpack}} goal, not {{copy-dependencies}}. Either way, emitting a warning would be good.

> copy-dependencies overwrites artifacts of the same artifact id
> --------------------------------------------------------------
>
>                 Key: MDEP-776
>                 URL: https://issues.apache.org/jira/browse/MDEP-776
>             Project: Maven Dependency Plugin
>          Issue Type: Bug
>          Components: copy-dependencies
>    Affects Versions: 3.1.2, 3.2.0
>            Reporter: Nikolaos Georgiou
>            Priority: Major
>
> 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)
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)