You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2011/01/16 14:16:58 UTC
[jira] Closed: (MPLUGIN-180) Encoding issues with reports
[ http://jira.codehaus.org/browse/MPLUGIN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Theussl closed MPLUGIN-180.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.7
Assignee: Lukas Theussl
Fixed in [r1059551|http://svn.apache.org/viewvc?rev=1059551&view=rev]. Snapshot deployed, please test.
> Encoding issues with reports
> ----------------------------
>
> Key: MPLUGIN-180
> URL: http://jira.codehaus.org/browse/MPLUGIN-180
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
> Affects Versions: 2.6
> Environment: MacOS 10.6.6, Maven 3.0.2
> also seen on Windows XP, Maven 3.0.2
> Reporter: Anders Hammar
> Assignee: Lukas Theussl
> Fix For: 2.7
>
> Attachments: mojo-details-encoding.zip
>
>
> When specify project.reporting.outputEncoding and using non-ascii chars in a mojo's description (and also for mojo param descriptions), the chars are incorrectly transferred to the mojo details site page. I think there's a general encoding issue, but this is where I've seen the problem and it is easy to reproduce.
> Steps to reproduce with attached project:
> * execute 'mvn site'
> * have a look in target/generated-site/xdoc/touch-mojo.xml
> * for example, check the description of the mojo. It should be "åäöÅÄÖ", but is garbage.
--
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