[
https://jira.codehaus.org/browse/MRESOURCES-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354160#comment-354160
]
Aaron Digulla commented on MRESOURCES-171:
------------------------------------------
@Karl-Heinz Marbaise: What would be a correct/working POM which just applied
this encoding to property files and use the default encoding for everything
else?
I'd suggest to use the encoding iso-8859-1 for copying and resource filtering
since it's a 1:1 encoding (each byte just passes through) but that doesn't work
when the resource plugin expands a variable with a value that contains Unicode
characters (code point > 256) since those can't be mapped to iso-8859-1
anymore. So we would have a situation where most parts of a file would make it
into the target folder unscathed but in some corner cases, it would fail.
> ISO8859-1 properties files get changed into UTF-8 when filtered
> ---------------------------------------------------------------
>
> Key: MRESOURCES-171
> URL: https://jira.codehaus.org/browse/MRESOURCES-171
> Project: Maven Resources Plugin
> Issue Type: Bug
> Components: filtering
> Reporter: Alex Collins
> Priority: Minor
> Fix For: backlog
>
> 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.1.6#6162)
