[
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
