[
https://issues.apache.org/jira/browse/MNG-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699403#comment-17699403
]
Herve Boutemy edited comment on MNG-7655 at 3/12/23 10:23 PM:
--------------------------------------------------------------
I don't get why you could change the groupId but not the artifactId: everything
in Maven core classloader does not care about Maven coordinate, nor does the
exports in API classloader.
You should read
https://maven.apache.org/guides/mini/guide-maven-classloading.html and dig into
mechanisms for exports
was (Author: hboutemy):
I don't get why you could change the groupId but not the artifactId: everything
in Maven core classloader does not care about Maven coordinate
you should read
https://maven.apache.org/guides/mini/guide-maven-classloading.html and dig into
mechanisms for exports
> 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)
