From: "Stefan Bodewig" <[EMAIL PROTECTED]> > The stuff that didn't get enough - or negative - votes in the first > pass. > > >> * Unify <available> and <uptodate> into a more general <condition> > >> task, support AND/OR of several tests here.
+1 > > >> * Add an <ant> task that will find build files according to a > >> * fileset and invokes a common target in them. > >> > >> * Add a JavaApply task that executes a given class with files from a > >> fileset as arguments - similar to <apply>. > +1 > > >> * Include some more sophisticated loggers with the Ant distribution > >> * - especially for sending emails. Make the existing one more > >> * flexible (stylesheet used by XmlLogger). > +1 > ------------------ > > >> * make the default logger's output clear, informative, and terse. > Still -1. > > >> * add an attribute to <property> to read in an entire file as the > >> value of a property. > > Peter Donald wrote: > > > -1. One thing I would like to see is property/available and other similar > > tasks simplified by not overiding the tasks. Instead new tasks like > > > > <file-property ... /> > > <data-property ... /> > > <load-properties ... /> > Not sure why this would be preferable. > ------------------ > > >> * make PATH handling consistent. Every task that has a PATH > >> * attribute must also accept references to PATHs. > -1. Let task writers be smart :-)
