[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.

["Immo Huneke (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93014 ] 

Immo Huneke commented on MRESOURCES-29:
---------------------------------------

I have tried using the XML escape for $ - $ - but to no avail. I suspect that the problem is not so much the value I am trying to match in my activation criterion, but the fact that the referenced property has not been defined yet. Does anyone have information on the order in which this happens?

My pom contains the following:{code}
. . .
    <properties>
        <appserver.root>${env.APPSERVER_ROOT}</appserver.root>
    </properties>
    <profiles>
        <profile>
            <id>without-tomcat</id>
            <activation>
                <property>
                    <name>appserver.root</name>
                    <value>&#36;{env.APPSERVER_ROOT}</value>
                </property>
            </activation>
            <properties>
                <webapp.dir>target/dummy-deploy</webapp.dir>
            </properties>
        </profile>
. . . 
{code}

There's a clue in that I had to use "target" instead of "${project.build.directory}" - the latter was not being expanded.

> 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 @start@user.home@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