Re: new Task subclass

2004-07-22 Thread Mike Jennings
I haven't created hundreds of ANT build files, but my intuition is that being restricted from property evaluation isn't that bad. IMHO testing for the presence/absence of a property is fine at the level. I don't mind introducing yet another property name just for the conditional execution of a w

Re: new Task subclass

2004-07-21 Thread Mike Jennings
> Ok here is the argument about being not such a good idea (in general). > 1) For every contition you need to test in the whole of your buildfile > you need to come up with yet another property that will be use for > testing it. > > 2) Then you need to make sure that all your properties have been

Re: new Task subclass

2004-07-21 Thread Mike Jennings
> I knew. > But there is the hierarchy-depth problematic. > And if ALL tasks should have such a if/unless-handling the right place is > inside > oata.Task itself, so all tasks will have that implicit. And why only tasks? > Why > not all ProjectComponents? But we havent any consensus about if/unless

Re: new Task subclass

2004-07-20 Thread Mike Jennings
} } Jan > -Ursprüngliche Nachricht- > Von: Mike Jennings [mailto:[EMAIL PROTECTED] > Gesendet am: Montag, 19. Juli 2004 15:30 > An: [EMAIL PROTECTED] > Betreff: new Task subclass > > Hi, > > I was thinking that all of the core tasks

new Task subclass

2004-07-19 Thread Mike Jennings
Mike Jennings Southgate Software Ltd (250) 382-6851 tel (250) 818-5230 cel (250) 592-6851 fax