[
https://issues.apache.org/jira/browse/MSHARED-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736736#comment-17736736
]
Guillaume Nodet commented on MSHARED-1274:
------------------------------------------
I missed that they had been rewritten too.
Anyway, I'd like to challenge a bit the assertion
{quote}It's a mess that has never properly implemented the XML specs, and
building Maven around what plexus-xml thinks XML is makes it very challenging
to use tools that do properly implement XML like XSLT to do anything with
poms.{quote}
I think the problem is more in the generated modello readers which do not
handle namespaces, rather than the xpp3 parser which can not read them.
Changing the underneath parser won't have any effect unless we change the way
the xml is actually processed. Anyway, I'm going to experiment a bit...
> 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)
