| Summary: | allow property expansion in <filterset> property values | ||
|---|---|---|---|
| Product: | Ant | Reporter: | Leon J. Breedt <ljb> |
| Component: | Core tasks | Assignee: | Ant Notifications List <notifications> |
| Status: | NEW --- | ||
| Severity: | enhancement | CC: | admin, petr.kuzel |
| Priority: | P3 | Keywords: | PatchAvailable |
| Version: | 1.4.1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | other | ||
| Attachments: | An ancient hack I've used to work around this limitation. | ||
the version missing this functionality is 1.4.1, and reading the 1.5 docs on <filterchain> did not provide any obvious solutions to this problem in 1.5. Created attachment 1964 [details]
An ancient hack I've used to work around this limitation.
I've faced the same problem and modifier Filter to do the trick. In 1.5 I'm
using ExpandProperties filter with an added "prefix" attribute to limit which
properties get expanded - otherwise system properties such as ${java.home} would
get replaced by the ${java.home} of the build platform instead of being resolved
at runtime on the running platform!
I've submitted a request for enhancement with a diff included, see bug #9481.
Hmm. Maybe ReplaceTokens should support a filterfile and something like
expand="true|false" to control property expansion?
*** Bug 18253 has been marked as a duplicate of this bug. *** |
i currently have one set of properties for my build system, and these are loaded using <property file="xxx.properties"/>. they contain embedded references to other properties using ${} syntax. this works fine in general use in my build file, however, when i want to use these same properties for a filtercopy, the ${} variables are not expanded in the output files. i can't do a <replace> since i may not know which properties were used as @name@ tokens in the file, and i don't want to hardcode the list of properties to replace. i don't see how the <expandproperties> feature of <filterchain> of 1.5 helps me in this case, so i would request that the ability be added to the <filterset> and the <replace> task to expand the values of properties contained in the property files they load.