I'm not so sure. I see NAnt.optional as a place for new tasks that may or may not be useful. As such it will always have a place. So if we get a new task donated and we're not sure if it will be useful or not we can drop it in optional and use the feedback we get to decide whether to keep it or re-locate it to a different task assembly.
Humm.... That sounds much better. Still, I'd personally prefer not to end
with something like Nant.Optional :) I believe we could move these into
their own assemblies and then just do whatever we want in how to build them
(the organization thingie seems to be creeping up again :P). Anyway I'm
guessing the real problem is what should go on in the basic distribution....
and since NAnt.Optional.Tasks.dll + dependencies adds up to 1.2mb I don't have a problem shipping the whole thing.
OK - I'll get on to it. Ian
I also tried moving the sources last night but got a little bored after
around 1 hour... Had most of it compiling, too, but then again, I'm fairly
familiar with both Nant and NAntContrib (heck, I wrote my fair share of the
tasks in NantContrib, after all). The checklist sounds like a very good
idea!
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
