[
https://issues.apache.org/jira/browse/MRESOURCES-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801493#comment-16801493
]
Aaron Digulla edited comment on MRESOURCES-171 at 3/26/19 9:03 AM:
-------------------------------------------------------------------
My preferred solution is: The plugin uses ISO-8859-1 when reading and writing
.properties files by default and this encoding can be overridden with a config
option. So when people have found a way to work around the encoding in their
code (like creating their own {{Reader}}), they can configure the plugin to use
${project.build.sourceEncoding}.
was (Author: digulla):
My preferred solution is: The plugin uses ISO-8859-1 when reading and writing
.properties files by default and this encoding can be overridden with a config
option. So when people have found a way to work around the encoding in their
code (like creating their own {{Reader}}), they can configure the plugin to use
${{{project.build.sourceEncoding}}}.
> 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
(v7.6.3#76005)
