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 2007/04/12 16:24:46 UTC
[jira] Commented: (MPJALOPY-12) Add a property that controls the
source code encoding
[ http://jira.codehaus.org/browse/MPJALOPY-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92722 ]
Lukas Theussl commented on MPJALOPY-12:
---------------------------------------
What happens if maven.compile.encoding is null (it is not set by default by the java plugin)?
> Add a property that controls the source code encoding
> -----------------------------------------------------
>
> Key: MPJALOPY-12
> URL: http://jira.codehaus.org/browse/MPJALOPY-12
> Project: maven-jalopy-plugin
> Issue Type: Improvement
> Environment: working on a machine with diffrent (default) encoding then the java source code
> Reporter: Joachim Bader
> Fix For: 1.5.1
>
> Attachments: patch.diff
>
>
> from http://jalopy.sourceforge.net/existing/plugin-ant-usage.html
> "encoding Sets the encoding that controls how Jalopy interprets text files containing characters beyond the ASCII character set. Defaults to the platform default 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