jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
Signup
Maven 2.x Dependency Plugin
  • Maven 2.x Dependency Plugin
  • MDEP-200

ArtifactId Namespace Conflict

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.1
  • Fix Version/s: None
  • Component/s: copy-dependencies
  • Labels:
    None
  • Environment:
    Any
  • Number of attachments :
    0

Description

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.

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
Herve Boutemy made changes - 28/Oct/12 5:07 AM
Field Original Value New Value
Assignee Brian Fox [ brianfox ]

People

  • Assignee:
    Unassigned
    Reporter:
    David Greenberg
Vote (1)
Watch (2)

Dates

  • Created:
    02/Mar/09 1:05 PM
    Updated:
    28/Oct/12 5:07 AM
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.