Sam Ruby <[EMAIL PROTECTED]> wrote: > The 80% use case is for scripts to interact with something *outside* > of the build script itself.
I'm not sure. We've been telling people to use <script> for conditionals or loops and similar. For the conditionals we can probably get away with having Target.execute but for loops you will probably want access to the attributes of the task to run. But this is mere guesswork as I still have to use a <script> task in real world build files myself. Stefan
