[
https://jira.codehaus.org/browse/MRESOURCES-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=327839#comment-327839
]
Lefebvre JF commented on MRESOURCES-174:
----------------------------------------
It is exactly that
IT is not possible to define a ressource as encoding1 and another as encoding2
So, when filter ressource is activated, the file created will loose the
original enconding
Two solutions
Auto detect file encoding
Possibility to set encoding for a list of ressource
Regards
> Loose encoding when filter resource
> -----------------------------------
>
> Key: MRESOURCES-174
> URL: https://jira.codehaus.org/browse/MRESOURCES-174
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Environment: Maven 3.0.4
> Reporter: Lefebvre JF
>
> When filtering resource the build.source.encoding is taken enven if there are
> multiple encoding for properties, xml, ...
> Why do not use api to detect the original encoding ?
> http://code.google.com/p/juniversalchardet/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
