[ http://jira.codehaus.org/browse/MJNCSS-10?page=comments#action_85280 ] 
            
Jean-Laurent de Morlhon commented on MJNCSS-10:
-----------------------------------------------

Thanks for your stacktrace.
Unfortunatly your solution is *not* working on MacOSX as is.
In fact the encoding to be given to the SAXParser must be the one used to write 
the original source code.
Since it seems that JavaNCSS is not taking into account encoding properly.
In fact, if some of the source files are under UTF-8 and some under ISO-8859-1 
the xml file produced by JavaNCSS will be flawed I think.
I'm still looking for a simple solution....


> Plugin crashes when Java elements have special characters
> ---------------------------------------------------------
>
>                 Key: MJNCSS-10
>                 URL: http://jira.codehaus.org/browse/MJNCSS-10
>             Project: Maven 2.x JavaNCSS Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-2
>            Reporter: Fabrice BELLINGARD
>         Assigned To: Jean-Laurent de Morlhon
>             Fix For: 2.0-beta-3
>
>
> 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"));

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to