This scripty notion is just plain silly. You almost always have to do builds conditionally. That's why make has them, and that's why ANT has them too, albeit in a very ugly way by means of <condition>/properties and if/unless/os on targets and other things too. Even Diane, the person who gives the best advise on ANT, seems to think <if>/<foreach>/<trycatch> are more than worthwhile, and their use makes build files 100 times better structured than all these targets if/unless/os triggered by properties, etc...
The objective to encapsulate all conditional/repetitive processes into tasks is great, and ANT has made good progress on many tasks, but preventing all ANT users out there of clean and elegant conditional/repetitive execution of tasks, well that's being very blind to users need. People will prototype their build processes with <if>/<foreach>/etc... and later streamline it into a cleaner task or two. Just try putting to a vote the inclusion of <if>/<foreach> into ANT core to ANT *users*!!! These are still XML, are XSLT transformable, are clean and elegant. They just formalize into a very natural way what ANT already does (in a very inelegant way). Meritocracy shouldn't mean dismissing the need of a very sizeable chunk of the ANT user community. --Dominique "scripty" Devienne -----Original Message----- From: Erik Hatcher [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 30, 2002 4:31 AM To: Ant Users List Subject: Re: "if" task Write your builds in Perl if you want "scripty". Hey, even call Ant from there if you like. :)) By the way, there is a <script> task too. Erik ----- Original Message ----- From: "Dave Bettin" <[EMAIL PROTECTED]> To: "Ant Users List" <[EMAIL PROTECTED]> Sent: Tuesday, April 30, 2002 12:04 AM Subject: Re: "if" task > > > It's considered too "scripty". > > What is the motivation to keep ant from being to > "scripty"? > > Thanks, > Dave > > __________________________________________________ > Do You Yahoo!? > Yahoo! Health - your guide to health and wellness > http://health.yahoo.com > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
