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

Michael Osipov commented on MRESOURCES-281:
-------------------------------------------

Unless they aren't filtered, does it matter? 

> allow different encodings for files inside the same resource-directory
> ----------------------------------------------------------------------
>
>                 Key: MRESOURCES-281
>                 URL: https://issues.apache.org/jira/browse/MRESOURCES-281
>             Project: Maven Resources Plugin
>          Issue Type: Improvement
>          Components: filtering
>    Affects Versions: 3.2.0
>            Reporter: Carsten Rohde
>            Priority: Major
>              Labels: encoding, feature, newbie
>
> Currently each resource-directory has a single encoding, with the recent 
> exception of properties (MRESOURCES-171).
> If you need to filter differently encoded files, this can become quite a 
> hazzle: The only way (at least that I'm aware of) is to have different 
> resouce-directories, one for each encoding.  Apart from bloating the pom, it 
> also forces you to have related files at different locations if they are 
> encoded differently.
>  
> What I'm suggesting is to generalize what has been done for properties by 
> allowing to override the <encoding> for specific files/patterns.
> Ideally this would be part of the resource-declaration but being able to 
> configure the resources plugin accordingly would already help a lot:
> {code:java}
> <configuration>
>    <encodingOverrides>
>        <encodingOverride>
>           <encoding>UTF-16</encoding>
>           <includes>**/*.myfile</includes>
>        </encodingOverride>
>        <encodingOverride>
>            <encoding>iso-latin-1</encoding>
>            <includes>**/*.other</includes>
>        </encodingOverride>
>    </encodingOverrides>
> </configuration>
> What do you think?{code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to