[ 
https://jira.codehaus.org/browse/MRESOURCES-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328393#comment-328393
 ] 

Emeric MARTINEAU commented on MRESOURCES-174:
---------------------------------------------

Hi,

I look if easy to make a patch.

For this new feature, the class org.apache.maven.model.PatternSet (part as 
Maven-Model) need to update cause include/exclude are String.
Actually, you cannot attach an encoding to each include/exclude.

Step for this feature is :
- submit a patch for Maven-Model (to update org.apache.maven.model.PatternSet),
- submit a patch for Maven-Filtering (to use the new 
org.apache.maven.model.Resource < PatternSet),
- submit a patch for Maven-Ressource-Plugin (to use nex maven filtering).

I don't know if it's possible to submit a patch for all or if submit one patch 
for each.

Regards,
                
> Loose encoding when filter resource
> -----------------------------------
>
>                 Key: MRESOURCES-174
>                 URL: https://jira.codehaus.org/browse/MRESOURCES-174
>             Project: Maven 2.x Resources Plugin
>          Issue Type: Bug
>    Affects Versions: 2.6
>         Environment: Maven 3.0.4
>            Reporter: Lefebvre JF
>
> When filtering resource the build.source.encoding is taken enven if there are 
> multiple encoding for properties, xml, ...
> Why do not use api to detect the original encoding ?
> http://code.google.com/p/juniversalchardet/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to