[jira] Commented: (MRRESOURCES-36) ${project.build.sourceEncoding} not honoured.

["Christian Schulte (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRRESOURCES-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156222#action_156222 ] 

Christian Schulte commented on MRRESOURCES-36:
----------------------------------------------

Correct solution would be to make the sourceEncoding an attribute of the RemoteResourcesBundle model so that a bundle created with, for example, UTF-8 can be used in a project using a different encoding. See the second patched attached.

> ${project.build.sourceEncoding} not honoured.
> ---------------------------------------------
>
>                 Key: MRRESOURCES-36
>                 URL: http://jira.codehaus.org/browse/MRRESOURCES-36
>             Project: Maven 2.x Remote Resources Plugin
>          Issue Type: New Feature
>    Affects Versions: 1.0-alpha-1, 1.0-alpha-2, 1.0-alpha-3, 1.0-alpha-4, 1.0-alpha-5, 1.0-alpha-6, 1.0-beta-2, 1.0
>         Environment: Maven version: 2.0.9
> Java version: 1.6.0_07
> OS name: "linux" version: "2.6.27.6-workstation" arch: "i386" Family: "unix"
>            Reporter: Christian Schulte
>            Priority: Blocker
>         Attachments: MRRESOURCES-36
>
>
> Velocity has its own default encoding (ISO-8859-1) when reading templates and does not honour the current environment setting. Also the plugin ignores any source encoding which leads to encoding issues for any non-ASCII resources. The attached patch adds a new mojo parameter sourceEncoding which defaults to ${project.build.sourceEncoding} and makes copying and appending to resources encoding aware.

-- 
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