Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-beta-2
-
Fix Version/s: 2.0-beta-2
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
One of my team mate found this bug when using a 'é' char on a Java method.
When JavaNCSS generates the XML report file, it doesn't specify the file encoding in the <xml> tag (at the very beginning of the file). So when the MOJO reads the report file, it doesn't know which encoding it should use and crashes when reading the report file.
Looking quickly at the NcssReportMojo class, it looks like specifying the file encoding in the #loadDocument(File file) method should fix the bug (but I haven't tested it):
reader.setEncoding(System.getProperty("file.encoding"));
Issue Links
| This issue relates to: | ||||
| MJNCSS-15 | UTF-8 Support |
|
|
|
| This issue is superceded by: | ||||
| JAVANCSS-5 | generated XML file is invalid: file content encoding is not consistent with encoding specified in XML prolog |
|
|
|
Jean-Laurent, as I know you authored this plugin, I assigned it to you.