I'd vote +1 on using filterchains and -1 on filtersets. It seems like with the right combination of standard filterchains we can replace the functionality of filtersets all together.
----- Original Message ----- From: "Gert Driesen" <[EMAIL PROTECTED]> Sent: Tuesday, October 07, 2003 11:19 AM Subject: Re: [nant-dev] filterchains/sets other was: [Fwd: Ready to tackle next release] > > ----- Original Message ----- > From: "Ian MacLean" <[EMAIL PROTECTED]> > > > I think I need to read up on filterchains a bit more. Is the > > functionality of filterchains a superset of filtersets ? > > Yes, filtersets are in fact very limited as they only support token > replacement. > > > > > It should be possible to use the same type discovery mechanism we now > > use for Tasks and referencable elements to discover filterreader classes > > in a given assembly. Or somthing similar using attributes. > > Yes, the discovery mechanism shouldn't be all that hard. > > Should I comment out the filterset code in the <copy> and <move> tasks to > prevent users from using these until we've decided if we'll replace it by > filterchain support (shortly) ? > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
