[
https://issues.apache.org/jira/browse/MRESOURCES-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082113#comment-15082113
]
Hervé Boutemy commented on MRESOURCES-171:
------------------------------------------
IMHO, we should, yes, find some new solution to this problem: encoding can't be
completely uniform in a project
what we set currently is default source encoding
and we should find a way to configure an association of other encodings to some
resources
idea: something like
{code:xml}<configuration>
<encoding>default encoding for the mojo</encoding>
<outputDirectory>${basedir}/target/extra-resources</outputDirectory>
<resources>
<resource>
<directory>src/non-packaged-resources</directory>
<filtering>true</filtering>
<encoding>optional encoding for this resource</encoding>
</resource>
</resources>
</configuration>{code}
instead of reopening this issue which is seen as a bug, I'd prefer create
another issue with title "add ability to define per-resource encoding when
filtering" and link to this one as "superceeded by"
WDYT?
> 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
(v6.3.4#6332)
