[
https://issues.apache.org/jira/browse/MRESOURCES-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159737#comment-17159737
]
Dennis Lundberg commented on MRESOURCES-171:
--------------------------------------------
After having slept on this I realize that we should do the same thing as we did
with the encoding parameter. We start out with an INFO about the situation and
encourage our users to set the new propertiesEncding parameter. Some time
later, say a year from now or so, we can turn that INFO into a WARN. That will
give people like Anders and myself plenty of time to adjust our POMs to ensure
that we don't get any warnings in our logs when we upgrade to the latest
version of the plugin a year from now.
What are your thoughts [~afloom] ?
> 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)
