[ 
https://issues.apache.org/jira/browse/MNG-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653070#comment-17653070
 ] 

ASF GitHub Bot commented on MNG-7655:
-------------------------------------

hboutemy commented on PR #942:
URL: https://github.com/apache/maven/pull/942#issuecomment-1367796459

   oh, back to plexus-utils https://codehaus-plexus.github.io/plexus-utils/ vs 
maven-shared-utils https://maven.apache.org/shared/maven-shared-utils/ 
discussion
   
   I suppose we can split maven-shared-utils 3 into maven-shared-xml 4 + 
maven-shared-utils 4
   
   using maven-shared-utils 4 instead of plexus-utils 4 in Maven core is not an 
issue
   
   but switching to maven-shared-xml 4 is not possible, because there is a java 
package change from plexus-xml 4
   
   




> 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: Sub-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)

Reply via email to