[MRESOURCES-70] Filter does not process nested ${} variables

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Auto Closed
• Affects Version/s: 2.2
• Component/s: delimiters
• Assignee: Unassigned
• Reporter: Matt Steele
• Created: 30/Jul/08 15:22
• Updated: 06/Sep/15 20:51
• Resolved: 06/Sep/15 20:51

Description

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}

Issue Links

• is related to: MRESOURCES-104 while filtering resources the token replacement stops at the character @
• is related to: MRESOURCES-105 Custom Delimiters does not work as expected - NPE with ${*} and comments in property file does break replacement