maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl-Heinz Marbaise (JIRA)" <j...@codehaus.org>
Subject [jira] (MEAR-159) encoding when filtering resources
Date Tue, 17 Feb 2015 19:45:18 GMT

    [ https://jira.codehaus.org/browse/MEAR-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=363482#comment-363482
] 

Karl-Heinz Marbaise commented on MEAR-159:
------------------------------------------

Is this true for 2.10 ?

> encoding when filtering resources
> ---------------------------------
>
>                 Key: MEAR-159
>                 URL: https://jira.codehaus.org/browse/MEAR-159
>             Project: Maven Ear Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.8
>            Reporter: Alex Kaigorodov
>             Fix For: waiting-for-feedback
>
>         Attachments: maven-ear-plugin-test-project-resources-encoding.zip
>
>
> Resources of our ear project contain non-ascii characters. This xml-files in windows-1251.
We use filtering resources when building ear.
> Building in the dev environment (Windows, file.encoding = Cp1251) goes well. The build
at the CI-server (Linux, file.encoding = UTF-8) non-ascii characters in xml-files are replaced
with a sequence of bytes 'efbfbd'.
> It would be convenient to be able to specify the encoding for the ear resources, similar
to how we can do it in the maven-resources-plugin.
> Sample project attached.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message