Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Patch
Description
DefaultMavenProjectBuilder reads POM in system default character encoding, and the encoding parameter in xml declartion is ignored.
to fix this problem, We should
- fix modello-plugin-xpp3 to use the xml parser which is able to handle the encoding parameter properly
- regenerate maven-model using fixed modello-plugin-xpp3
- fix DefaultMavenProjectBuilder to use regenerated maven-model properly.
Attachments
Attachments
Issue Links
- is depended upon by
-
MANTTASKS-14 Ant Tasks do not work on the ZOS
- Closed
-
MANTTASKS-79 add XML encoding support for pom.xml and settings.xml
- Closed
- is duplicated by
-
MNG-2025 POM is still not read using the right encoding
- 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-2618 pom.xml with amperstands and variables
- Closed
-
MNG-2818 maven 2 requires a UTF-8 locale to build properly
- Closed
-
MNG-2932 Encoding chaos
- Closed
- is related to
-
MNG-2362 Deployed POM is not valid XML
- Closed
-
MRELEASE-87 Poms are written with wrong encodings
- Closed
-
MNG-2215 Change the default input/output encoding to UTF-8 instead of ISO-8859-1
- Closed
-
MNG-2216 Add default encodings section to POM
- Closed
-
MNG-2187 Improve error message when the pom is encoded in the wrong charset
- Closed
- relates to
-
MPLUGINTESTING-5 Respect file encoding of POMs
- Closed
-
CONTINUUM-2507 Error releasing project with POM encoded in UTF-8 with BOM
- Closed
-
MNG-2255 Use a external XML Pull parser instead of plexus one
- Closed
-
MDEPLOY-66 add XML encoding support for POM reading/writing
- Closed
-
MINSTALL-44 add XML encoding support for POM reading/writing
- Closed
-
MREPOSITORY-10 add XML encoding support for POM reading/writing
- Closed
-
DOXIA-60 Use an external XML Pull parser instead of plexus one
- Closed