[jira] [Assigned] (MRESOURCES-232) Resource copy filtering should use different encoding for source and output
[ https://issues.apache.org/jira/browse/MRESOURCES-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg reassigned MRESOURCES-232: -- Fix Version/s: (was: 3.2.0) Assignee: (was: Dennis Lundberg) > 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} > > > ${project.basedir}/sbin-ebcdic > > > ${project.basedir}/sbin > > > IBM037 > > {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)
[jira] [Assigned] (MRESOURCES-232) Resource copy filtering should use different encoding for source and output
[ https://issues.apache.org/jira/browse/MRESOURCES-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold reassigned MRESOURCES-232: Assignee: Dennis Lundberg > 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 >Assignee: Dennis Lundberg >Priority: Major > Labels: maven > Fix For: 3.2.0 > > > 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} > > > ${project.basedir}/sbin-ebcdic > > > ${project.basedir}/sbin > > > IBM037 > > {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)