ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Kavanagh <>
Subject Re: copy task addition
Date Tue, 27 May 2003 14:17:38 GMT
I was hoping you were right. I followed the docs on how to use the 
filterchain in my copy task and I can't get those values to be replaced. 
I even tried defining a property inside my build.xml file and that 
didn't get picked up either.
My stuff must function differently, but I can see that implementing it 
as a filterchain option would be better than the attribute I chose to use.

Here is my copy task... I did it properly, right?

      <copy toDir="${classes}" file="cocoon/WEB-INF/" 
overwrite="true" filtering="true">


Conor MacNeill wrote:

>On Tue, 27 May 2003 12:23 am, David Kavanagh wrote:
>>I just signed on to contribute something we found useful.
>>We wanted to filter files based on the project properties. This is
>>because we do something like this in the top of our build.xml file;
>>    <property file="${user.home}/" />
>>    <property file="${user.home}/" />
>>    <property file="${basedir}/" />
>>So, we couldn't use properties pulled from any arbitrary files without
>>modifying the copy task. So, what I did was to add a propsFiltering flag
>>that uses the project properties as a filter set. Here is the diff of
>>the file from the 1.5.3-1 src dist. We've used this and it
>>works great!
>Can't you use a filterchain?
>  <filterchain>
>    <expandproperties/>
>  </filterchain>
>To unsubscribe, e-mail:
>For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message