[
https://jira.codehaus.org/browse/MWAR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276326#comment-276326
]
philippe tseyen commented on MWAR-225:
--------------------------------------
Same here.
I need to be able to filter with {}, because flex forces me to use that
notation.
Does anyone have a workaround for this?
> Add support for customizing filtering delimiters like the resources plugin
> --------------------------------------------------------------------------
>
> Key: MWAR-225
> URL: https://jira.codehaus.org/browse/MWAR-225
> Project: Maven 2.x WAR Plugin
> Issue Type: Improvement
> Affects Versions: 2.1-beta-1
> Reporter: Peter Runge
> Priority: Minor
>
> After recently upgrading to Maven3 beta1 from alpha7 I noticed that our
> filters were not taking effect any more. We were using '@' for creating
> filer tokens, which used to work alpha7 but no more with beta1.
> In any case, looking at the resources plugin, it has a delimiters property
> that can be used to customize the delimiters when filtering. As suggested by
> http://stackoverflow.com/questions/2315009/override-mavens-default-resource-filter-replacement-pattern
> I set an appropriate property on the resources plugin, but no such property
> exists for the WAR plugin at the moment which means I am stuck. I need to
> keep the delimiter token as '@' because we need to maintain Ant compatibility
> for the time being.
> It would be nice if this property also existed on the WAR plugin so that
> filtering delimiters could be customized.
> The code in the resources plugin that does the job:
> http://maven.apache.org/plugins/maven-resources-plugin/xref/org/apache/maven/plugin/resources/ResourcesMojo.html#233
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
