maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emeric MARTINEAU (JIRA)" <j...@codehaus.org>
Subject [jira] (MRESOURCES-174) Loose encoding when filter resource
Date Tue, 09 Jul 2013 15:10:05 GMT

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

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

Hi,

I think it's cool feature.
The maven resources plugin do not filter any file.

Files are filter by other plugin like jar, assembly, war...
If you look source of this plugin, you can see all use a shared lib call "maven-filtering"
part at "maven-shared-components". 

You can close this ticket.

To implements this feature you must open feature request at http://jira.codehaus.org/browse/MSHARED/component/13380
and after, open feature request for all official plugin to use it.

You can add link to new feature request to https://jira.codehaus.org/browse/MRESOURCES-175
cause it looks like this ticket.

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

Mime
View raw message