[
https://issues.apache.org/jira/browse/MRESOURCES-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159035#comment-17159035
]
Dennis Lundberg commented on MRESOURCES-171:
--------------------------------------------
True, you can use Unicode escapes to work around the problem. The downside of
that is that you loose the readability for humans. ResourceBundles used for
localization is an example where that workaround probably wouldn't work very
well.
Sorry, I forgot to write down my own assumptions about Herves suggestion :) I
saw that his configuration was meant for the plugin. However I discarded that
as a viable solution, since I don't think having almost the same configuration
for the same thing in 2 different locations in the POM is a wise move. It would
of course be technically possible to implement, but the amount of confusion for
our users and the amount of support questions would be massive in my opinion.
> 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)
