Details
-
Improvement
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
2.0.4
-
None
Description
To avoid maintaining the plexus XMLPullParser we should move to a standard implementation like StaX
As mentioned in DOXIA-60:
There's a performance white paper
http://java.sun.com/performance/reference/whitepapers/StAX-1_0.pdf
The best implementation seems to be http://woodstox.codehaus.org/
Another nice set of utilities at http://wiki.java.net/bin/view/Javawsxml/StaxUtilsProject
The indentator could be used instead of the PrettyPrintXMLWriter
Attachments
Issue Links
- is related to
-
MNG-2593 Maven 2 stumbels upon non ASCII characters in the value of a <localRepository> value in the $HOME/.m2/settings.xml
- Closed
-
MNG-2362 Deployed POM is not valid XML
- Closed
-
MNG-2057 The Maven 2.0.2 XML parser fails to parse a UTF-8 POM that begins with the optional byte-order mark.
- Closed
-
MNG-2254 the encoding parameter in xml declaration of POM is ignored
- Closed
-
MNG-2818 maven 2 requires a UTF-8 locale to build properly
- Closed
-
MNG-4708 I am not able to add name space prefixes to pom.xml
- Closed
-
MNG-2769 Use of POM namespace is confused and confusing in both the code and the documentation
- Closed
- relates to
-
MSHARED-255 create DomUtils, equivalent from Xpp3DomUtils but working on W3C DOM
- Closed
-
MPLUGIN-229 don't use Plexus' Xpp3 in generated HelpMojo to read XML files: XML parser in JDK is sufficient
- Closed
-
DOXIA-60 Use an external XML Pull parser instead of plexus one
- Closed
- supercedes
-
MNG-2715 Maven does not comply to XML rules regarding prefixes.
- Closed