[jira] [Created] (MRESOURCES-232) Resource copy filtering should use different encoding for source and output

["Peng Cheng (JIRA)" <ji...@apache.org>]

Peng Cheng created MRESOURCES-232:
-------------------------------------

             Summary: Resource copy filtering should use different encoding for source and output
                 Key: MRESOURCES-232
                 URL: https://issues.apache.org/jira/browse/MRESOURCES-232
             Project: Maven Resources Plugin
          Issue Type: Bug
          Components: copy, filtering
    Affects Versions: 3.0.1
         Environment: Ubuntu 16.04 JDK 1.8 maven 3.3.4
            Reporter: Peng Cheng


In copy-resources goal. The configuration option 'encoding' is documented to be capable of changing the encoding of source files and copy to output directory, e.g.:

                    <configuration>
                        <outputDirectory>${project.basedir}/sbin-ebcdic</outputDirectory>
                        <resources>
                            <resource>
                                <directory>${project.basedir}/sbin</directory>
                            </resource>
                        </resources>
                        <encoding>IBM037</encoding>
                    </configuration>

However, it is pointed out in the answer section of this post:

http://stackoverflow.com/questions/40095716/why-maven-resources-plugin-ignores-my-charset-encoding-setting

that this option affects both reading of source file and writing of output file, resulting in most of the file encodings not converted. This should be corrected by dividing this option into 2:

sourceEncoding & outputEncoding, which controls reading and writing separately. This is the most simple way to make encoding conversion practical.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)