This was also my rational of not just adding a flag to <call/>. The <depends/> task is just a dynamic form of the <target/> task's depends attribute..., in all other respect their ultimate functionality would be identical. The <depends/> task was not meant to be used as a way to call targets, but (more accurately), to assert that a set of dependencies were meet or handled (if needed) before continuing. This is similar a little bit to .NET security with the way you can request certain privileges up front (as assembly metadata), or dynamically by asserting them within code.
Heh... I just ran into the same problem you have. My workaround so far is to add the following attribute to all of my "execute-once" targets:
unless="${target::has-executed(target::get-current-target())}"
I would love to have the <depends/> task instead. :)
Matt.
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
