Conor MacNeill <[EMAIL PROTECTED]> wrote: > I think we need to have a debate about whether nested tasks is a > desirable concept to implement.
So let me chip in, even if I don't have a very strong opinion on it either. To me it's quite clear that asking, whether a TaskContainer concept (I'd prefer that name as well) is desirable, boils down to "Do we want to make it easier to write a foreach or a switch/case task?". If we wanted to support such stuff with as little impact on Ant's core as possible the TaskContainer approach looks like the way to go. OK, being the "purist" that I am ;-) I must say no. There should always be a better choice than writing tasks like these - take <execon> for example. On the other hand, there has been a very strong desire in the user community by advanced users for such a feature. Use cases have been provided that are quite inconvenient to solve without it. So we have one reason in favor of it "it makes it possible to write a <foreach> task" - which is not enough to make me vote >0 for that, not at all - and one against it "it makes it possible to write a <foreach> task" - which is not enough to make me veto it out (no thought police here ;-). This means I'm currently -0 on the issue unless somebody can give me a better reason to include/exclude a TaskContainer feature. Stefan
