[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[
http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=150657#action_150657
]
Daniel Beland commented on MRESOURCES-29:
-
None of the suggested workarounds worked for me and I don't want to use the
2.3-SNAPSHOT.
So until it is released here is how we can achieve it, works for me:
Use $${property} when you want to escape a property and simply process the
resources with ant after the filtering is done
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idescape-properties/id
phaseprocess-resources/phase
configuration
tasks
replace dir=${project.build.directory}/classes
includes=**/*.properties,**/*.xml,**/*.vm
replacetoken![CDATA[$$]]/replacetoken
replacevalue![CDATA[$]]/replacevalue
/replace
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdorg.apache.ant/groupId
artifactIdant-nodeps/artifactId
version1.7.1/version
/dependency
/dependencies
/plugin
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
Assignee: Olivier Lamy
Fix For: 2.3
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
[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[
http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=147630#action_147630
]
Maik Ebert commented on MRESOURCES-29:
--
Will this also be documented on the plugin homepage?
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
Assignee: Olivier Lamy
Fix For: 2.3
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
[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[
http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=147634#action_147634
]
Olivier Lamy commented on MRESOURCES-29:
yup have a look here [http://svn.apache.org/viewvc?view=revrevision=694005]
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
Assignee: Olivier Lamy
Fix For: 2.3
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
[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[
http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=139763#action_139763
]
Dave O'Flanagan commented on MRESOURCES-29:
---
I've tried $${user.id} in maven 2.0.9 and it works fine. I get ${user.id} in
the output.
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
[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[
http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=139802#action_139802
]
Hendrik Schreiber commented on MRESOURCES-29:
-
Great.
Is this an old feature documented somewhere, or is this new and needs to be
documented?
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
[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[
http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=139805#action_139805
]
Felipe Kamakura commented on MRESOURCES-29:
---
Odd...
I've tried here the $${} in Maven 2.0.9 and it didn't work out. I'm using in
Linux.
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
[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[
http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111328
]
Richard Wallace commented on MRESOURCES-29:
---
Has there been any movement or further discussion of this elsewhere? I've
looked through the mailing list and can't find any further references and as
far as I can tell no one has found a solution that works.
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
[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[
http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111362
]
Ian Springer commented on MRESOURCES-29:
I'm still willing to code up my previously suggested fix for this and submit a
patch, if I can get a confirmation from one or more committers that they are ok
with the fix.
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
[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[
http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99314
]
Ian Springer commented on MRESOURCES-29:
An way to escape $'s should certainly be provided.
But further, as the original poster suggested, there should be a way to
configure what the token format is. Here is a use case for providing this:
I am using the resources plugin to copy over a bunch of JBoss config files. If
you've used JBoss, you know that it supports runtime replacement of ${foo}
tokens with system properties. So, in most cases, I don't want Maven messing
with the ${foo} tokens in these files. However, there are a handful of tokens I
do want Maven to replace. If I could change the token format to something other
than the ${foo} default, then I could use that alternate format for the tokens
I do want Maven to replace.
Here's an example of how this might be specified in the POM:
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
tokenStartDelimiter@@/tokenStartDelimiter
tokenEndDelimiter@@/tokenEndDelimiter
/resource
...
/resources
This would tell the resources plugin to replace tokens of the form @@foo@@
instead of the default form ${foo}.
If others could benefit from this feature, say so. If there's enough interest,
I'll whip up a patch.
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
[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[
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 $ - #36; - 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
idwithout-tomcat/id
activation
property
nameappserver.root/name
value#36;{env.APPSERVER_ROOT}/value
/property
/activation
properties
webapp.dirtarget/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 @[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
[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[
http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93015
]
Immo Huneke commented on MRESOURCES-29:
---
Oops - the comment above interpreted the XML escape for $ as $. The actual code
is of course amp;#36; .
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
[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[
http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93016
]
Immo Huneke commented on MRESOURCES-29:
---
No, actually I have verified that writing amp;#36; is PRECISELY equivalent to
writing $ - if you use it to introduce a property reference then the value is
interpolated. So we're still looking for a workable escape mechanism.
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
[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[
http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86181
]
Dan Hardiker commented on MRESOURCES-29:
I have tried the following, none of which work:
* *$\{dollarSign}\{id}* where dollarSign = $
* [EMAIL PROTECTED]@[EMAIL PROTECTED]@* where dollarSIgn = $, start = \{, end =
}
* [EMAIL PROTECTED]@[EMAIL PROTECTED]@* where start = ${, end = }
All yeild in the same result - the artifact's full ID being spat out. What I am
looking for is a simple solution where I can put down *$$\{id}* or *\$\{id}*
and have that come out the other side as literally *$\{id}*.
Any _working_ work-arounds are appreciated!
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
[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.
[ 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
