Affects Version/s: 2.8
Fix Version/s: 2.10.1
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.