maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schulte (JIRA)" <j...@codehaus.org>
Subject [jira] (MJAVADOC-355) Encoding problem if platform encoding used to run Maven is different from default platform encoding.
Date Tue, 02 Oct 2012 08:25:36 GMT

     [ https://jira.codehaus.org/browse/MJAVADOC-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christian Schulte updated MJAVADOC-355:
---------------------------------------

    Attachment: MJAVADOC-355.patch

Patch passing the platform encoding to Javadoc.
                
> Encoding problem if platform encoding used to run Maven is different from default platform
encoding. 
> -----------------------------------------------------------------------------------------------------
>
>                 Key: MJAVADOC-355
>                 URL: https://jira.codehaus.org/browse/MJAVADOC-355
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Wish
>    Affects Versions: 2.9
>            Reporter: Christian Schulte
>            Priority: Trivial
>         Attachments: MJAVADOC-355.patch
>
>
> When setting up a platform encoding in MAVEN_OPTS (e.g. '-Dfile.encoding=UTF-8'), the
plugin writes command line argument files using that encoding. This encoding is not preserved
when executing Javadoc which then reads these command line files using the real platform encoding.
The platform encoding Maven is running with needs to be preserved in Javadoc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message