[
https://issues.apache.org/jira/browse/MRESOURCES-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15660550#comment-15660550
]
Christian Schulte commented on MRESOURCES-171:
----------------------------------------------
The IDE I am using writes unicode escapes into the properties files. There is
no way to disable that and IMHO it's the way to go. Doing it that way, no
conversion takes place as it pretty much makes the properties files contain
ASCII only. We maybe need to think about the filtering to use unicode escapes
as well. For example: Having a non-ASCII project name the substituted
$project.name should use unicode escapes. Maybe add a boolean
{{unicodeEscapes}} parameter to the plugin and make the filtering produce those
escapes.
> ISO8859-1 properties files get changed into UTF-8 when filtered
> ---------------------------------------------------------------
>
> Key: MRESOURCES-171
> URL: https://issues.apache.org/jira/browse/MRESOURCES-171
> Project: Maven Resources Plugin
> Issue Type: Bug
> Components: filtering
> Reporter: Alex Collins
> Priority: Minor
> Attachments: filtering-bug.zip
>
>
> Create:
> src/main/resources/test.properties
> And add a ISO8859-1 character that is not ASCII or UTF-8, do not use \uXXXX
> formatting.
> When adding this line:
> <resource><directory>src/main/resources</directory><filtering>true</filtering></resource>
> Expected:
> ISO8859-1 encoded file in jar.
> Actual:
> UTF-8 encoded file in jar.
> ---
> If there are any property files (which can only be ISO8859-1) they appear to
> be converted into UTF-8 in the jar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
