You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2014/01/23 16:25:49 UTC
[jira] (MNG-5514) Global filter delimiters
[ https://jira.codehaus.org/browse/MNG-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-5514.
------------------------------
Resolution: Won't Fix
> 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