[
https://issues.apache.org/jira/browse/MNG-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699289#comment-17699289
]
Herve Boutemy commented on MNG-7655:
------------------------------------
keeping 4 XML parsing classes as-is is a MUST =
{code:xml}
<!-- plexus-utils (for DOM-type fields in maven-model) -->
<exportedPackage>org.codehaus.plexus.util.xml.Xpp3Dom</exportedPackage>
<exportedPackage>org.codehaus.plexus.util.xml.pull.XmlPullParser</exportedPackage>
<exportedPackage>org.codehaus.plexus.util.xml.pull.XmlPullParserException</exportedPackage>
<exportedPackage>org.codehaus.plexus.util.xml.pull.XmlSerializer</exportedPackage>
{code}
from https://maven.apache.org/ref/3.9.0/maven-core/core-extensions.html
> 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)
