On 21 Sep 2001, Matthew Inger <[EMAIL PROTECTED]> wrote: > But to be so blind as to not even open the possibility of including > it as part of the optional tasks is silly, from my point of view.
I agree with you - or at least I would if there was an optional package that doesn't impose additional maintenance burden on the Ant committers. As things are now, we have no way to give people commit access to just a single source file - so every modification to a contributed task takes some time for one of the committers to pick it up. Ask Les Hughes about his contributions in the Perforce area to see what that means. When you look through the stuff for Ant2, you'll see that we want to make extending Ant a lot easier than it is right now - with the concept of task libraries I guess custom tasks from external sources will become more common than they are right now. As for SourceForge-ing an ant-contrib module - go ahead. I don't know what has happened to taskdefs.org, though. I wouldn't use org.apache.tools.ant as base package but org.apache.ant BTW - this is where Ant2 is going to live (once it is going to be alive). Who would decide what goes into this module - whom am I going to ask if I want to contribute my IfTask? 8-) Finally on the subject of a foreach task, I'd recommend to simply rely on TaskContainer for the "task embedding" part and to not guarantee the order of execution so you are free to change the implementation as Ant's core evolves (or even throw in parallel execution of the "foreach" block for different arguments). Stefan
