[
https://issues.apache.org/jira/browse/MDEP-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17948038#comment-17948038
]
ASF GitHub Bot commented on MDEP-976:
-------------------------------------
hboutemy commented on PR #523:
URL:
https://github.com/apache/maven-dependency-plugin/pull/523#issuecomment-2837814938
@Ndacyayisenga-droid please take time to review the checkboxes in the issue
description and fill them as necessary: keeping them not checked is not useful
on adding a new option just for copy-dependencies, I'm not clear: why?
`prependGroupId` is the configuration the user did not know about
I'd prefer either we change the default value for `prependGroupId`, or we
add code to detect when conflict happens and WARN with a hint on how to
configure `prependGroupId`
> 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)
