I know I'm jumping in on this a bit late, but I think something important has been overlooked...
In the example below, if the build must run generate THEN compile, you should define the generate target to depend on the compile target. By fully defining all your dependencies, you will never need to sequentially execute targets in the depends list. This seems like the proper solution to me - no new syntax, no new rules, just a requirement to use the depends attribute properly. However, Jose's point about breaking builds probably stands - even if those builds are incompletely defined ;) Glenn. -----Original Message----- From: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 25, 2001 4:06 AM To: [EMAIL PROTECTED] Subject: RE: [RESULT] multithrading <<stuff deleted>> Well, the cold reality is that we do give guarantees that things will be done sequentially. I think we will be breaking lots of builds if we were to just change that, unfortunately. Now, there is no reason to just add a little bit more of new syntax to diferentiate between sequential-exec-required (",") and sequential-exec-optional (";" for example). So the target in your example would be written: <target name="build" depends="compile;copy_properties"/> or you could say: <target name="build" depends="generate,compile;copy_properties"/> which means execute "generate" and "compile" ensuring sequential execution, and "copy_properties" can be done in any order. <<more stuff deleted>> Jose Alberto
