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/jrules.properties" overwrite="true" filtering="true">
<filterchain>
<expandproperties/>
</filterchain>
</copy>
David
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}/.membership-build.properties" /> <property file="${user.home}/.build.properties" /> <property file="${basedir}/.build.properties" />
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 Copy.java 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>
Conor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
