ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John.D.Ca...@mail.sprint.com
Subject [PATCH] allowing filters to resolve properties before substituting
Date Fri, 06 Apr 2001 13:26:56 GMT
This patch allows the user to OPTIONALLY specify that filters 
containing property names in the standard reference syntax ( 
${some.property} ) will be resolved to actual values before 
substitution.  This is useful if you dynamically generate classpaths 
during the build process that need to be substituted into shell 
scripts, etc...
I patched the copy task to optionally allow this behavior. Why the copy 
task?  Because I recognized that properties may change during the 
course of a build, and ideally the resolution of a filter should take 
place at the time of substitution, to get the most up-to-date property 
value.  I realize that this means anything else capable of filtering 
would also need patches, but I believe this is the "right" approach, 
and would be willing to submit patches for those tasks, if I know which 
ones they are (I don't have time to sort through all the tasks to find 
them, however...).

Please Note: You don't have to use this new feature.  By default, it is 
disabled on the copy task for backward compatibility.  To enable it, 
just use the substitute="true" attribute.

Thanks, and enjoy,

John Casey



  



Mime
View raw message