> To be honest I'd like to see us release a 1.0 with the current feature > set before implementing somthing like typed properties.
Agree. Still I'd like to see some verbosity patch and fileset extensions in 1.0 somehow. Hope those will find its way into 1.0 even they are not in release plan. > it would be kinda nice to unify properties and type references which are > both essentially different types of variables. However I do feel that > this is peripheral to what the majority of users want to do with nant. > ie its quite a big change which doesn't actually make that much of a > user-visible difference in many cases. Not that its not worth > investigating just that it might be sensible to set this out past a 1.0 > release. To yours 2nd mail: >Sure this is clean in a mathematical sense but personally I'd rather see >a more verbose layout that actually gives me an idea of what files the >fileset will match just by looking at it. Given that it can be hard to >determine what a given fileset will match right now I imagine it will be >that much more difficult trying to work out the result after a >difference operation has been performed. Agree. I have more and more feeling that just add <includes refid=""/> into fileset should be enough. It is not type-general but... Martin ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
