You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "David Greenberg (JIRA)" <ji...@codehaus.org> on 2009/03/02 20:07:12 UTC

[jira] Created: (MDEP-200) ArtifactId Namespace Conflict

ArtifactId Namespace Conflict
-----------------------------

                 Key: MDEP-200
                 URL: http://jira.codehaus.org/browse/MDEP-200
             Project: Maven 2.x Dependency Plugin
          Issue Type: Improvement
          Components: copy-dependencies
    Affects Versions: 2.1
         Environment: Any
            Reporter: David Greenberg
            Assignee: Brian Fox


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 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