Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.5
-
None
-
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)
-
Patch
Description
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.
Attachments
Attachments
Issue Links
- depends upon
-
MSHARED-228 MultiDelimiterInterpolatorFilterReaderLineEnding() does not filter after a token is escaped
- Closed