[
https://issues.apache.org/jira/browse/MDEP-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17949412#comment-17949412
]
ASF GitHub Bot commented on MDEP-976:
-------------------------------------
elharo commented on PR #523:
URL:
https://github.com/apache/maven-dependency-plugin/pull/523#issuecomment-2850703748
It absolutely is valid in Maven for two different artifacts to have the same
artifact ID but different group IDs. Artifact IDs are not unique or intended to
be. In fact, this is common with forked projects and likely occurs with other
common artifact IDs like "utils".
> artifactId is not guaranteed to be globally unique
> --------------------------------------------------
>
> Key: MDEP-976
> URL: https://issues.apache.org/jira/browse/MDEP-976
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: copy-dependencies
> Affects Versions: 3.8.1
> Reporter: Gili
> Priority: Major
>
> The copy-dependencies Mojo incorrectly assumes that a dependency's artifactId
> is globally unique. If a project depends on two different groupIds that
> happen to have the same artifactId then one dependency will overwrite the
> other.
> Consider adding ${groupId} to the default output filename and/or add an
> option for doing so in case users wish to retain backwards compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
