You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Felipe Cuozzo (JIRA)" <ji...@codehaus.org> on 2009/12/16 16:12:55 UTC

[jira] Commented: (MCHANGES-144) The encoding of JIRA xml file is not UTF-8

    [ http://jira.codehaus.org/browse/MCHANGES-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203044#action_203044 ] 

Felipe Cuozzo commented on MCHANGES-144:
----------------------------------------

Hi Benjamin,

I step in the same problem here, running the plugin on Windows (pt_BR locale, ISO-8859-1 encoding).

I was able to bypass this error setting the system property -Dfile.encoding=UTF-8 when running Maven2, so your comment about plataform encoding is probably right. I'll try to attach the generated files.

Here is the stacktrace:

{code}
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
org.apache.xerces.impl.io.MalformedByteSequenceException: Invalid byte 2 of 3-byte UTF-8 sequence.
        at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
        at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
        at javax.xml.parsers.SAXParser.parse(SAXParser.java:331)
        at org.apache.maven.plugin.jira.JiraXML.<init>(JiraXML.java:66)
        at org.apache.maven.plugin.jira.JiraReportGenerator.<init>(JiraReportGenerator.java:93)
        at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:249)
        at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:131)
        at org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:172)
{code}

And here is the GET respose from the Jira server:

{code}
HTTP/1.0 200 OK
Date: Wed, 16 Dec 2009 13:36:19 GMT
Server: Apache
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Wed, 31 Dec 1969 23:59:59 GMT
Content-Type: text/xml;charset=ISO-8859-1
X-Cache: MISS from xxxx
X-Cache-Lookup: MISS from xxxx:3128
Via: 1.0 pedra:3128 (squid/2.6.STABLE6)
Proxy-Connection: close

<!--  RSS generated by JIRA (Enterprise Edition, Version: 3.12.3-#302) at Wed Dec 16 11:36:19 BRST 2009 -->
<!-- If you wish to do custom client-side styling of RSS, uncomment this:
{code}

> The encoding of JIRA xml file is not UTF-8
> ------------------------------------------
>
>                 Key: MCHANGES-144
>                 URL: http://jira.codehaus.org/browse/MCHANGES-144
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Bug
>          Components: jira-report
>    Affects Versions: 2.1
>         Environment: JIRA Enterprise Edition V3.10.1, JDK 1.5.0_15, Maven 2.0.9
>            Reporter: Sonix William Legend
>
> If the JIRA encoding is not UTF-8, the program generated the jira report throws a exception. 
> "org.xml.sax.SAXParseException: Invalid byte 1 of 1-byte UTF-8 sequence."
> So I think you should add a parameter that set the 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