Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 2.0
-
Fix Version/s: 2.0.8
-
Component/s: POM::Encoding
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
IIRC XML standard says that default encoding is UTF-8 for xml files
That can be overriden with
<?xml version="1.0" encoding="ISO-8859-1"?>
But files without header saved as UTF8 are not parsed in some systems (eg windows, solaris), while files saved as other encoding (I believe it was ansi) break under a Mac mini with yellowdog linux
Issue Links
- depends upon
-
PLXUTILS-11
MXParser can't handle the encoding declaration in XML declaration
-
- duplicates
-
MNG-2254
the encoding parameter in xml declaration of POM is ignored
-
- is depended upon by
-
MECLIPSE-56
Generated .project-file misses encoding declaration
-
This issue is a clone of
MNG-1603. Sorry, The Fix Version is not correct due to cloning (I misunderstood this cloning feature slightly.)My experiences working with encodings is, that Maven actually DOES NOT read model files using the right encoding. It might be true, that the declared encoding is read and attached to the model. But certain field like description are read using the default system character set, which isn't the same as the POM's encoding in all cases.
I'll provide test cases both for maven-model and maven-project to demonstrate the problem.
Again, sorry for the misleading issue data by cloning
MNG-1603.Regards,
Stefan