[
https://issues.apache.org/jira/browse/MSHARED-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736767#comment-17736767
]
Guillaume Nodet commented on MSHARED-1274:
------------------------------------------
Here's my experiments: https://github.com/gnodet/maven/tree/xml-experiments
The results of the performance tests are the following:
{code}
Benchmark Mode Cnt Score Error Units
Xpp3DomPerfTest.readWithStaxAlto avgt 5 180.467 ± 1.921 ms/op
Xpp3DomPerfTest.readWithStaxJdk avgt 5 308.447 ± 7.208 ms/op
Xpp3DomPerfTest.readWithStaxXpp3 avgt 5 219.544 ± 3.496 ms/op
Xpp3DomPerfTest.readWithXpp3 avgt 5 197.684 ± 3.535 ms/op
{code}
So I'm willing to investigate switching to the Stax API and Aalto XML parser.
The work is already half done with the above branch anyway...
> 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)
