You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2009/09/28 18:24:56 UTC
[jira] Issue Comment Edited: (MRESOURCES-70) Filter does not
process nested ${} variables
[ http://jira.codehaus.org/browse/MRESOURCES-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192591#action_192591 ]
John Casey edited comment on MRESOURCES-70 at 9/28/09 11:23 AM:
----------------------------------------------------------------
I'm guessing MRESOURCES-104 hits the same snag as MRESOURCES-70, with the difference being that -104 is handling a nested expression involving two different sets of delimiters, both of which are enabled by default: ${\*} and @\*@. In the InterpolationFilterReader, it will not replace the contents of an expression for which the ending delimiter is never specified, as this isn't technically a valid expression.
So, it seems that if we solve the recursive expression problem, we can solve both of these issues.
was (Author: jdcasey):
I'm guessing MRESOURCES-104 hits the same snag as MRESOURCES-70, with the difference being that -104 is handling a nested expression involving two different sets of delimiters, both of which are enabled by default: ${*} and @*@. In the InterpolationFilterReader, it will not replace the contents of an expression for which the ending delimiter is never specified, as this isn't technically a valid expression.
So, it seems that if we solve the recursive expression problem, we can solve both of these issues.
> Filter does not process nested ${} variables
> --------------------------------------------
>
> Key: MRESOURCES-70
> URL: http://jira.codehaus.org/browse/MRESOURCES-70
> Project: Maven 2.x Resources Plugin
> Issue Type: New Feature
> Affects Versions: 2.2
> Reporter: Matt Steele
>
> When I try filtering this under src/main/resources:
> jms.username=${${env}.jms.username}
> with this filtering strategy:
> <resources>
> <resource>
> <directory>src/main/resources</directory>
> <filtering>true</filtering>
> </resource>
> </resources>
> Setting the property (from command line, <property>, etc.) fails to properly filter the nested element:
> jms.username=${${env}.jms.username}
> For example, I'd like the filter to convert to this (using a property of -Denv=dev):
> jms.username=${dev.jms.username}
--
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