[
https://issues.apache.org/jira/browse/MSHARED-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735409#comment-17735409
]
Elliotte Rusty Harold commented on MSHARED-1274:
------------------------------------------------
searching github I only see one use of
org.apache.maven.shared.utils.xml.pull.XmlPullParserException from outside the
maven-shared-utils repo and its forks by Maven team members:
https://github.com/search?q=org.apache.maven.shared.utils.xml.pull.XmlPullParserException&type=code
We can check other classes but since this exception is pretty fundamental to
any use of the other classes in this package, it's likely safe to go ahead and
deprecate the entirety of org.apache.maven.shared.utils.xml
> Deprecate the xml bits from maven-shared-utils
> ----------------------------------------------
>
> Key: MSHARED-1274
> URL: https://issues.apache.org/jira/browse/MSHARED-1274
> Project: Maven Shared Components
> Issue Type: Task
> Components: maven-shared-utils
> Reporter: Guillaume Nodet
> Priority: Major
>
> The xml bits from plexus-utils are a de-facto part of the maven 3.x api and
> we should not have two conflicting versions of it. Now that it has been
> extract in a separate project in plexus-xml, I think it is time to deprecate
> those classes in maven-shared-utils. Fwiw, the core implementation classes
> are mainly implemented with Maven 4.x maven-xml-impl module, and the Xpp3Dom
> class from plexus-xml is mainly a wrapper around the new XmlNode/XmlNodeImpl
> class from maven, however the parser is still present in plexus-xml.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
