[
http://jira.codehaus.org/browse/MRESOURCES-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212262#action_212262
]
Cornel Masson edited comment on MRESOURCES-117 at 3/3/10 4:03 AM:
------------------------------------------------------------------
Why is Ant (and Maven + Antrun) capable of filtering @...@ tokens correctly in
files containing other @ symbols, but Maven resources-plugin not?
I welcome the @ delimeter as a default, but then it should work out of the box
with any file - @ is quite a common symbol in many text files, e.g. ones
containing e-mail addresses. Windows batch scripts also fall fowl of this bug.
was (Author: cornel.masson):
Why is Ant (and Maven + Antrun) capable of filtering @...@ tokens
correctly, but Maven resources-plugin not?
I welcome the @ delimeter as a default, but then it should work out of the box
with any file - @ is quite a common symbol in many text files, e.g. containing
e-mail addresses. Windows batch scripts also fall fowl of this bug.
> maven-resources-plugin 2.4+ filtering broken
> --------------------------------------------
>
> Key: MRESOURCES-117
> URL: http://jira.codehaus.org/browse/MRESOURCES-117
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Linux (CentOS) 2.6.18-164.el5
> Reporter: Sheldon Daigle
> Assignee: Olivier Lamy
> Priority: Critical
>
> Using maven-resources-plugin version 2.4 or newer, fails to filter some
> files. This was a nasty one to find because it only affects certain files. If
> you create a file to be filtered with the following lines:
> <%@ taglib prefix="NAME1" uri="http://www.sun.com/tags2"; %>
> <%@ taglib prefix="NAME2" uri="http://www.sun.com/tags"; %>
> <%@ taglib prefix="NAME3" uri="http://www.sun.com/test/tags"; %>
> ${taglibFnInclude}
> and define the taglibFnInclude property to some value, e.g:
> <taglibFnInclude>MY-STRING</taglibFnInclude>
> a "mvn resources:resources" build will will not filer the file. If you add
> another line above the property value or delete a line, the file gets
> filtered properly. E.g, the following work:
> <%@ taglib prefix="NAME1" uri="http://www.sun.com/line1"; %>
> <%@ taglib prefix="NAME2" uri="http://www.sun.com/line2"; %>
> <%@ taglib prefix="NAME3" uri="http://www.sun.com/line3/tags"; %>
> <%@ taglib prefix="NAME4" uri="http://www.sun.com/line4/tags"; %>
> ${taglibFnInclude}
> AND
> <%@ taglib prefix="NAME1" uri="http://www.sun.com/line1"; %>
> <%@ taglib prefix="NAME2" uri="http://www.sun.com/line2"; %>
> ${taglibFnInclude}
> If I go back to version 1.3 of this plugin, everything works as it should.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
