a more usual way to author a build file is to set up dependencies between targets with the depends attribute. Then you set the targetyou want to run last as the default and all its dependencies will be run automatically.
This dependency mechanismis why force is set to false by default so that if a task has already been run as part of the dependency chain it does not get called again.
so in your build file I would do
<target name="DEVDB04\LOCAL" description="reload the local customer databases for 04" depends="setup">
rather than calling "setup" directly.
The copy task takes a child fileset element as I mentioned in a previous post.Maybe this is why (clipped comment from a distantly related thread below) I didn't see this if it's already documented, but it took me a bit of serendipity (just happening to remember wondering why in tarnation the force attribute for <call/> was there to begin with from sleep-deprived reading many nights ago) to figure out how to get all my multiple calls to reused targets to execute properly...
(Kudos to whoever wrote the <sql/> task - it rawkz! Replacing oodles of batch files and a homegrown wrapper for ISQL is muy kewl. The only little fly in the ointment is that - like copy - it doesn't seem to take a fileset property, either. *pout* But I can work around that with foreach for now.)
Ian
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
