[
https://issues.apache.org/jira/browse/MNG-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699334#comment-17699334
]
Elliotte Rusty Harold commented on MNG-7655:
--------------------------------------------
You can only keep them as is by leaving the package names, class name AND maven
coordinates the same. If you change the Maven coordinates (group ID, artifact
ID) but leave the fully qualified class name the same, users will experience
broken builds and bugs due to classpath conflicts, diamond dependency problems,
and loading unexpected versions of the classes.
I understand that it might be necessary not to change the package name, but in
that case they have to be published in the same artifact.
> rename Maven core's plexus-utils to more explicit artifactId
> ------------------------------------------------------------
>
> Key: MNG-7655
> URL: https://issues.apache.org/jira/browse/MNG-7655
> Project: Maven
> Issue Type: Task
> Affects Versions: 4.0.0-alpha-2
> Reporter: Herve Boutemy
> Priority: Major
>
> in https://github.com/apache/maven/pull/829 , Maven's internal plexus-utils
> repackaging is used, switching from Plexus original
> {{org.codehaus.plexus:plexus-utils}} to {{org.apache.maven:plexus-utils}}
> this switch keeping the exact same artifactId but just changing only the
> groupId is confusing: we need another artifactId
> {{maven-plexus-utils}}?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
