To tell you the truth I think that the 5(?) tasks of antcontrib are just a necesity if you try to write large ANT scripts that must be maintainable by more than one person.
The <if/> task helps reduce the amount of temporary variables ant special init-targets and intermediate targets whose only need is to check for a property being set or not. <trycatch/> speaks for itself. In my builds, at least, <foreach/> is a necesity, since many of my modules must be build several times with different configuration parameters. And the number of configurations is configurable. The other ones, <propertycopy> and others are just good. This is why I think we should ask for permission to ship it as an antlib. It will serve as an example of the power of the framework. > -----Original Message----- > From: Gus Heck [mailto:[EMAIL PROTECTED] > Sent: 08 October 2003 19:58 > To: Ant Developers List > Subject: Re: failonerror; general solution > > > > >I'm not as eager to see the tasks in Ant proper as others, > that's why I > >haven't taken any initiative here (in Apache speak, that's the > >difference between my +0 and the +1s that have been cast by others). > > > > > > > Are we talking about all ant-contrib tasks or just try/catch? > I thought > just try/catch... > > -Gus > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
