You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sonix William Legend (JIRA)" <ji...@codehaus.org> on 2008/12/24 07:21:20 UTC
[jira] Created: (MCHANGES-144) The encoding of JIRA xml file is not
UTF-8
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
[jira] Updated: (MCHANGES-144) Add configuration if the encoding of
JIRA xml file is not UTF-8
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MCHANGES-144:
-------------------------------------
Component/s: announcement
Description:
If the JIRA encoding is not UTF-8, the program that generates 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.
was:
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.
Fix Version/s: 2.4
Assignee: Dennis Lundberg
Issue Type: Improvement (was: Bug)
Summary: Add configuration if the encoding of JIRA xml file is not UTF-8 (was: The encoding of JIRA xml file is not UTF-8)
> Add configuration if 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: Improvement
> Components: announcement, jira
> Affects Versions: 2.1
> Environment: JIRA Enterprise Edition V3.10.1, JDK 1.5.0_15, Maven 2.0.9
> Reporter: Sonix William Legend
> Assignee: Dennis Lundberg
> Fix For: 2.4
>
> Attachments: jira-results.zip
>
>
> If the JIRA encoding is not UTF-8, the program that generates 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
[jira] Commented: (MCHANGES-144) The encoding of JIRA xml file is
not UTF-8
Posted by "Felipe Cuozzo (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MCHANGES-144) Add configuration if the encoding
of JIRA xml file is not UTF-8
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250182#action_250182 ]
Dennis Lundberg commented on MCHANGES-144:
------------------------------------------
Felipe, it would be great if you could test the fix that Hervé just committed. Just run the plugin as you did before, without the new encoding parameter that I added and see if that works for you. If that works, we should remove the parameter that I added.
> Add configuration if 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: Improvement
> Components: announcement, jira
> Affects Versions: 2.1
> Environment: JIRA Enterprise Edition V3.10.1, JDK 1.5.0_15, Maven 2.0.9
> Reporter: Sonix William Legend
> Assignee: Dennis Lundberg
> Fix For: 2.4
>
> Attachments: jira-results.zip
>
>
> If the JIRA encoding is not UTF-8, the program that generates 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
[jira] Commented: (MCHANGES-144) The encoding of JIRA xml file is
not UTF-8
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159134#action_159134 ]
Benjamin Bentmann commented on MCHANGES-144:
--------------------------------------------
XML has an encoding declaration, so a parameter on the plugin shouldn't be necessary. Can you attach the XML file downloaded by the plugin, i.e. {{${project.build.directory}/jira-results.xml}}. It's written using platform encoding and I suspect that's where it gets messed up.
> 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
[jira] Updated: (MCHANGES-144) The encoding of JIRA xml file is not
UTF-8
Posted by "Felipe Cuozzo (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felipe Cuozzo updated MCHANGES-144:
-----------------------------------
Attachment: jira-results.zip
I've zipped the files to avoid any corruption of the character encodings.
Inside it you will find 2 files:
*jira-results.xml*: is the file generate using the default plataform encoding.
*jira-results-forcing-UTF-8.xml*: is the file generated when the -Dfile.encoding=UTF-8 system parameter was added to the Maven execution arguments.
> 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
> Attachments: jira-results.zip
>
>
> 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
[jira] Commented: (MCHANGES-144) Add configuration if the encoding
of JIRA xml file is not UTF-8
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252496#action_252496 ]
Dennis Lundberg commented on MCHANGES-144:
------------------------------------------
I have reverted r1054263, as it was the wrong way to solve this issue.
A new 2.4-SNAPSHOT has been deployed. Please test.
> Add configuration if 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: Improvement
> Components: announcement, jira
> Affects Versions: 2.1
> Environment: JIRA Enterprise Edition V3.10.1, JDK 1.5.0_15, Maven 2.0.9
> Reporter: Sonix William Legend
> Assignee: Dennis Lundberg
> Fix For: 2.4
>
> Attachments: jira-results.zip
>
>
> If the JIRA encoding is not UTF-8, the program that generates 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
[jira] Commented: (MCHANGES-144) Add configuration if the encoding
of JIRA xml file is not UTF-8
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250649#action_250649 ]
Dennis Lundberg commented on MCHANGES-144:
------------------------------------------
Hervé,
do you think that I should remove the parameter that was added? We can always add it back later is it is needed.
> Add configuration if 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: Improvement
> Components: announcement, jira
> Affects Versions: 2.1
> Environment: JIRA Enterprise Edition V3.10.1, JDK 1.5.0_15, Maven 2.0.9
> Reporter: Sonix William Legend
> Assignee: Dennis Lundberg
> Fix For: 2.4
>
> Attachments: jira-results.zip
>
>
> If the JIRA encoding is not UTF-8, the program that generates 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
[jira] Commented: (MCHANGES-144) Add configuration if the encoding
of JIRA xml file is not UTF-8
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252479#action_252479 ]
Herve Boutemy commented on MCHANGES-144:
----------------------------------------
The problem reported by Felipe is exactly what I fixed in r1054373: the calling plugin was using platform encoding of Maven JVM to save Jira result, which was not consistent with result's XML prolog.
Felipe's report is the most precise we have: I consider his problem has been be fixed now, without the new configuration parameter.
So I'm in favour of removing the new parameter and considering this issue fixed.
> Add configuration if 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: Improvement
> Components: announcement, jira
> Affects Versions: 2.1
> Environment: JIRA Enterprise Edition V3.10.1, JDK 1.5.0_15, Maven 2.0.9
> Reporter: Sonix William Legend
> Assignee: Dennis Lundberg
> Fix For: 2.4
>
> Attachments: jira-results.zip
>
>
> If the JIRA encoding is not UTF-8, the program that generates 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
[jira] Closed: (MCHANGES-144) Add configuration if the encoding of
JIRA xml file is not UTF-8
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MCHANGES-144.
------------------------------------
Resolution: Fixed
Fixed in [r1054263|http://svn.apache.org/viewvc?view=revision&revision=1054263].
A new 2.4-SNAPSHOT has been deployed. Please help us test it.
I added a new configuration parameter jiraXmlEncoding.
> Add configuration if 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: Improvement
> Components: announcement, jira
> Affects Versions: 2.1
> Environment: JIRA Enterprise Edition V3.10.1, JDK 1.5.0_15, Maven 2.0.9
> Reporter: Sonix William Legend
> Assignee: Dennis Lundberg
> Fix For: 2.4
>
> Attachments: jira-results.zip
>
>
> If the JIRA encoding is not UTF-8, the program that generates 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
[jira] Commented: (MCHANGES-144) Add configuration if the encoding
of JIRA xml file is not UTF-8
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250173#action_250173 ]
Herve Boutemy commented on MCHANGES-144:
----------------------------------------
another related fix in [r1054373|http://svn.apache.org/viewvc?view=revision&revision=1054373]: the file was *saved by the plugin* with platform encoding, not *generated by Jira* AFAIK
SNAPSHOT deployed
not sure at all that the jiraXmlEncoding parameter is needed, and IMHO it would better be named "forceJiraEncoding" or something like this
> Add configuration if 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: Improvement
> Components: announcement, jira
> Affects Versions: 2.1
> Environment: JIRA Enterprise Edition V3.10.1, JDK 1.5.0_15, Maven 2.0.9
> Reporter: Sonix William Legend
> Assignee: Dennis Lundberg
> Fix For: 2.4
>
> Attachments: jira-results.zip
>
>
> If the JIRA encoding is not UTF-8, the program that generates 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