[ 
https://issues.apache.org/jira/browse/MDEP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MDEP-200:
-------------------------------------
    Fix Version/s: more-investigation

> ArtifactId Namespace Conflict
> -----------------------------
>
>                 Key: MDEP-200
>                 URL: https://issues.apache.org/jira/browse/MDEP-200
>             Project: Maven Dependency Plugin
>          Issue Type: Improvement
>          Components: copy-dependencies
>    Affects Versions: 2.1
>         Environment: Any
>            Reporter: David Greenberg
>             Fix For: more-investigation
>
>
> When copying a lot of dependencies into the same directory, it is possible 
> that some will have the same artifactId and version.  This will result in 
> only one of the dependencies getting copied.  This is not an issue if you are 
> using a repository-like target directory, but in the default case it is an 
> issue.  It would be better if copy-dependencies did something similar to how 
> WAR files are built where, if there is a conflict, the groupId is prepended 
> to the name of the artifact.
> If anyone has a decent workaround to this, please let me know.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to