Calls to extensions would obviously go into a build.xml, but I *wouldn't* write a <for>, etc. tag, I would write the tag that does the for, etc. functionality within Java.
-Peter > -----Original Message----- > From: Diane Holt [mailto:[EMAIL PROTECTED] > Sent: Monday, January 15, 2001 5:54 PM > To: [EMAIL PROTECTED] > Subject: Re: To Script or not To Script... > > > Well, it's a bit longer, but I believe that's what I said > earlier -- allow > for easy extensibility of Basic Ant to do the sorts of scripting-type > tasks people feel they need (I certainly do), and, whether directly > connected to the Apache Ant or off in its own project somewhere else, > assemble a group of extensions to form Extended Ant. > > Although one thing I'm not clear about is where exactly > you're thinking > you -would- put the "extension tags" (eg., <for>, <if>, etc.) > if not in a > build.xml file. > > Diane > > ===== > ([EMAIL PROTECTED]) > > > > __________________________________________________ > Do You Yahoo!? > Get email at your own domain with Yahoo! Mail. > http://personal.mail.yahoo.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
