maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <>
Subject [jira] [Commented] (MRESOURCES-171) ISO8859-1 properties files get changed into UTF-8 when filtered
Date Tue, 05 Jan 2016 00:44:40 GMT


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
              <encoding>default encoding for the mojo</encoding>
                  <encoding>optional encoding for this resource</encoding>

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"


> ISO8859-1 properties files get changed into UTF-8 when filtered
> ---------------------------------------------------------------
>                 Key: MRESOURCES-171
>                 URL:
>             Project: Maven Resources Plugin
>          Issue Type: Bug
>          Components: filtering
>            Reporter: Alex Collins
>            Priority: Minor
>         Attachments:
> Create:
> src/main/resources/
> 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

View raw message