[
https://jira.codehaus.org/browse/MRESOURCES-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354230#comment-354230
]
Karl-Heinz Marbaise commented on MRESOURCES-189:
------------------------------------------------
Hm...That the resource filtering is failing is caused while filtering resources
which should *not* being filtered which is on the contrary a regression. It is
improved behaviour in comparsion to older versions which have done the
filtering (changed the target files) silently which ends with wrong results.
The failing is caused here by a coincedence cause the end-delimiter couldn't be
found.
The consequence out of this would be to enhance the configuration and add
appropriate {{<nonFilteredFileExtension>Extension</nonFilteredFileExtension>}}.
If you think about filtering a binary file you can never be sure that there are
never start-delimiters within such kind of files (see the above; where the
start delimiter has been found). So filtering binary files is in my opinion a
contradiction in terms.
> [Regression] Resource filtering fails when encounters binary files
> ------------------------------------------------------------------
>
> Key: MRESOURCES-189
> URL: https://jira.codehaus.org/browse/MRESOURCES-189
> Project: Maven Resources Plugin
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Dan Tran
>
> see MRESOURCES-186
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
