Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0.8
-
Component/s: POM::Encoding
-
Labels:None
-
Complexity:Intermediate
-
Patch Submitted:Yes
-
Number of attachments :
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.
Issue Links
- depends upon
-
PLXUTILS-11
MXParser can't handle the encoding declaration in XML declaration
-
- is depended upon by
-
MANTTASKS-14
Ant Tasks do not work on the ZOS
-
-
MANTTASKS-79
add XML encoding support for pom.xml and settings.xml
-
- is duplicated by
-
MNG-2025
POM is still not read using the right encoding
-
-
MNG-2057
The Maven 2.0.2 XML parser fails to parse a UTF-8 POM that begins with the optional byte-order mark.
-
-
MNG-2618
pom.xml with amperstands and variables
-
-
MNG-2818
maven 2 requires a UTF-8 locale to build properly
-
-
MNG-2932
Encoding chaos
-
- is related to
-
MNG-2362
Deployed POM is not valid XML
-
-
MRELEASE-87
Poms are written with wrong encodings
-
-
MNG-2216
Add default encodings section to POM
-
-
MNG-2215
Change the default input/output encoding to UTF-8 instead of ISO-8859-1
-
-
MNG-2187
Improve error message when the pom is encoded in the wrong charset
-
- relates to
-
MPLUGINTESTING-5
Respect file encoding of POMs
-
-
CONTINUUM-2507
Error releasing project with POM encoded in UTF-8 with BOM
-
-
DOXIA-60
Use a external XML Pull parser instead of plexus one
-
-
MNG-2255
Use a external XML Pull parser instead of plexus one
-
-
MDEPLOY-66
add XML encoding support for POM reading/writing
-
-
MINSTALL-44
add XML encoding support for POM reading/writing
-
-
MREPOSITORY-10
add XML encoding support for POM reading/writing
-