[
https://jira.codehaus.org/browse/MRESOURCES-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301534#comment-301534
]
Olivier Lamy commented on MRESOURCES-166:
-----------------------------------------
ouppps.
No that's fine
> Escaping on a line suppresses filtering for the rest of the token/line
> ----------------------------------------------------------------------
>
> Key: MRESOURCES-166
> URL: https://jira.codehaus.org/browse/MRESOURCES-166
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: escape string
> Affects Versions: 2.5
> Environment: java version "1.6.0_33"
> Java(TM) SE Runtime Environment (build 1.6.0_33-b03-424-10M3720)
> Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03-424, mixed mode)
> Reporter: Graham Leggett
> Assignee: Olivier Lamy
> Attachments: MRESOURCES-166.tar
>
>
> When an attempt is made to filter the following shell script with the
> filtering option on the maven-resource-plugin, attempting to resolve one
> variable while keeping another variable intact, the second variable is not
> resolved:
> export SERVER_ENV=\${SERVER_ENV:${httpd.server.env}}
> The escape character "\" ends up escaping the entire token, or failing that
> the entire line, and the filter "${httpd.server.env}" is unresolved.
> Expected:
> export SERVER_ENV=${SERVER_ENV:sandbox}
> Actual:
> export SERVER_ENV=${SERVER_ENV:${httpd.server.env}}
> The problem lies inside maven-filtering, and a fix and patch has been
> submitted in http://jira.codehaus.org/browse/MSHARED-228 for maven-filtering
> v1.1-SNAPSHOT.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
