At 09:57 26/3/01 +0200, Stefan Bodewig wrote: > * Allow mappers to be genericised so that particular features can be modified > during mapping. Something similar to > > <fileset ...> > <include name="*.sh"/> > <mapper type="unix-permissions"> > <param name="user" value="ant"/> > <param name="group" value="ant"/> > <param name="mod" value="755"/> > </mapper> > </fileset>
Not sure if we should do it in the above manner yet but the general functionality +1. My only hesitation is that it may be complex in some cases but we can always offer a simplified DTD for web-guys that gets transformed into "real" tasks underneath. > * Allow include/exclude tow work with multiple characteristerics of a file. > ie include into fileset if file is readable, modified after 29th of Feb, > has a name that matches patter "**/*.java" and the property "foo.present" > is set. Something similar to +1 on functionality thou implementation needs to be thought about. >* provide datatypes through property tag and remove need for separate free > standing entities. ie > <property name="foo"> > <fileset dir="blah"> > <include name="*/**.java" /> > </fileset> > </property> +0 Either this or <datadef /> however if we add datatypedef we should expand the engine to handle special case datyapes or perhaps make base datatype class/interface. >* provide support for non-hardwired (ie loadable) low-level > components (mappers/itemset-filters/converters). Allow them to be > loaded in either global or a new classloader. +1 >* provide support for non-hardwired (ie loadable) converters. > > Q: What is a converter? Is this an implementation detail? > A: Not an implementation detail but a way to extend the engine > to convert more data types. Currently we have fixed set that is > expanded on occasion (ie includes primitive types + File). Instead > of spreading converting code through out tasks it can be centralized > into one component and used by engine. This becomes particularly > relevent if you build ant based testing systems and use ant in certain > web-related areas. +1 >* Make all datatypes interfaces to allow them to be customized in many > ways. +/-0 - maybe be relevent for particular types but not all of them >* Set arithmetic for fileset/patternset/*set +/- 0 may be useful but we need more time to think about it >* inheritance of ant properties/datatypes/context etc in project hierarchy +100000 ;) >* inheritance of between ant datatypes. ie fileset A inherits from fileset B (includes > all entries in A). +0 >* Homogenize notion of PATHs and filesets. +1 Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*
