Andera, The task does sound interesting, and much easier to work with than (for example) Ant's <parallel> task (at least IMHO). I think that the idea is useful enough that it would be worth looking at adapting your code to the more general case by implementing <forkcall> and <joincall> to call any target asynchronously (Project is thread-safe, right?)
Actually, I can see why asynchronous exec would be much simpler than asynchronous call... making everything (dependencies, properties, logging) behave correctly in a multithreaded environment would definitely need the cooperation of NAnt core, while multiprocess (with no interprocess communication) can be a bolt-on affair. I'd be happy to look at this, either way. I've got some improvements to the <exec> task that are waiting until after the 0.85 release to be merged in (changes to ExternalProgramBase == lots of regression testing) that would be extremely useful for the asynchronous version, if that's the path that's chosen. Picking this up would help ensure I don't forget the other :-) Regards, -- Troy ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_idt12&alloc_id344&op=click _______________________________________________ NAntContrib-Developer mailing list NAntContrib-Developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
