You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2002/05/10 12:54:26 UTC
DO NOT REPLY [Bug 8972] New: -
allow property expansion in property values
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8972>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8972
allow property expansion in <filterset> property values
Summary: allow property expansion in <filterset> property values
Product: Ant
Version: 1.5Beta1
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: Core tasks
AssignedTo: ant-dev@jakarta.apache.org
ReportedBy: ljb@itouchlabs.com
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.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>