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

["Dennis Lundberg (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MRESOURCES-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158130#comment-17158130 ] 

Dennis Lundberg commented on MRESOURCES-232:
--------------------------------------------

Could you please add a reference to where in the documentation it states that encoding can be changed during filtering, so that we can correct that. With the current implementation that is not possible.

Do you have a use case where you want the source-resources to be one encoding and the target-resources be another encoding?

> 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: New Feature
>          Components: copy, filtering
>    Affects Versions: 3.0.1
>         Environment: Ubuntu 16.04 JDK 1.8 maven 3.3.4
>            Reporter: Peng Cheng
>            Priority: Major
>              Labels: maven
>
> 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.:
> {code}
>                     <configuration>
>                         <outputDirectory>${project.basedir}/sbin-ebcdic</outputDirectory>
>                         <resources>
>                             <resource>
>                                 <directory>${project.basedir}/sbin</directory>
>                             </resource>
>                         </resources>
>                         <encoding>IBM037</encoding>
>                     </configuration>
> {code}
> 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
(v8.3.4#803005)