[
https://jira.codehaus.org/browse/MNG-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339883#comment-339883
]
Jason van Zyl commented on MNG-5514:
------------------------------------
Trying to get every plugin to adhere to this is not likely to work and I think
each plugin can document what it wishes to use as delimiters. I also wouldn't
want to force plugin implementers to try and conform to this as the particular
engines they use may not support it. If you want to have a common set of
delimiters and you know the plugins that you use will accept these parameters
then you can use simple properties in the POM.
> Global filter delimiters
> ------------------------
>
> Key: MNG-5514
> URL: https://jira.codehaus.org/browse/MNG-5514
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: POM
> Affects Versions: 3.1.0
> Environment: n/a
> Reporter: Trevor Baker
>
> In the maven-resources-plugin configuration we can specify which delimiters
> are used. For example, I can configure it to only accept $\{\*} tokens. I do
> this because the @*@ tokens sometimes conflicts with email addresses in the
> file being filtering. I'd like to have this be applied across all plugins
> that use filtering.
> However, with the maven-war-plugin it doesn't use the
> maven-resources-plugin's configuration for the delimiters and only uses the
> standard default tokens: $\{\*} and @*@. Now the maven-war-plugin can be
> enhanced to take in delimiters in it's configuration (see MWAR-225), which
> should happen.
> But ideally there should be a common markup in the pom for delimiters like
> there is for filters. Then the various plugins can use these global
> delimiters or override them in their own configuration.
--
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
