[ http://jira.codehaus.org/browse/MRESOURCES-29?page=comments#action_72461
]
Franz Allan Valencia See commented on MRESOURCES-29:
----------------------------------------------------
Actually, your workaround works with the current maven-resources-plugin.
maven-resources-plugin supports two token formats: %{token} , and @token@
> An escape mechanism for property interpolation is missing.
> ----------------------------------------------------------
>
> Key: MRESOURCES-29
> URL: http://jira.codehaus.org/browse/MRESOURCES-29
> Project: Maven 2.x Resources Plugin
> Issue Type: New Feature
> Affects Versions: 2.3
> Reporter: Hendrik Schreiber
>
> It would be great, if there was a mechanism that let's you escape a property
> so that it is not replaced by the filtering machism. E.g. in a log4j.xml
> configuration file you might want to preserve ${user.home}, but replace some
> other property like ${log.dir}. Currently there is no convenient way to
> achieve that.
> Alternatively to escaping, it would be helpful, if one could choose the token
> format. So, if one could say, only honor @token@ and not ${token} (or the
> other way around) one could easily work around the escape problem.
> Workaround for the problem mentioned above:
> replace the ${user.home} in log4j.xml with @[EMAIL PROTECTED]@end@ and define
> start=${ and end=$} in the property file
--
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
