[
https://jira.codehaus.org/browse/MEAR-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MEAR-159.
------------------------------------
Resolution: Fixed
Assignee: Karl-Heinz Marbaise
Fixed in [r1661423|http://svn.apache.org/r1661423].
> 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
> Assignee: Karl-Heinz Marbaise
> Fix For: 2.10.1
>
> Attachments:
> maven-ear-plugin-2.10-test-project-resources-encoding.zip,
> 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)
