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=18253>. 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=18253 filter task handles tokens differently if they come from a file Summary: filter task handles tokens differently if they come from a file Product: Ant Version: 1.5.2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In my build file I load different properties files for properties depening on the environment. I then Use these properties as values forow tokens during file copy. However I have the problem that tokens comming from a properties files, does not have its values property expanded while token set directly in the build file does example (this one works) <target ...> <property name="resin_install_dir" value="/opt/java/resin"> (this normally comes from a file) <filter token="resin_dir" value="${resin_install_dir}/doc"> <copy ....> </target> In this example the file copied contains "/opt/java/resin/doc/" as the replaced tokens, which is what I was expecting now having many tokens I moved them to a seperate file and did: <target ...> <property name="resin_install_dir" value="/opt/java/resin"> (this normally comes from a file) <filter filtersfile="tokens.properties"> <copy ....> </target> In this example the file copied contains "${resin_install_dir}doc/" as the replaced tokens, which is certainly not what I want.... :-( While waiting for the fix: Is there another workaound for the desired feature,without doing example 1 for all the tokens ?
