[
https://issues.apache.org/jira/browse/MRESOURCES-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158970#comment-17158970
]
Anders Hammar commented on MRESOURCES-171:
------------------------------------------
As I mentioned earlier, the same encoding problem could happen with xml files
if they're using a different encoding than configured for the source files. So
instead of creating a special fix (config property) for just properties files,
why not create something generic like Herve suggested
(https://issues.apache.org/jira/browse/MRESOURCES-171?focusedCommentId=15082113&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15082113)?
I think the implementation shouldn't be much more work as instead of checking
if a file has the .properties extension you'd check if there is a encoding
config block for that file.
> 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
(v8.3.4#803005)
