[
https://issues.apache.org/jira/browse/MEAR-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959028#comment-17959028
]
Matthias Bünger commented on MEAR-159:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-ear-plugin#338|https://github.com/apache/maven-ear-plugin/issues/338].
> encoding when filtering resources
> ---------------------------------
>
> Key: MEAR-159
> URL: https://issues.apache.org/jira/browse/MEAR-159
> Project: Maven EAR Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 2.8
> Reporter: Aleksey Kaigorodov
> Assignee: Karl Heinz Marbaise
> Priority: Major
> 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
(v8.20.10#820010)
