Getting tasks into a place that doesn't generalize them into just "optional" sounds good.
I'm all for moving the stable and useful tasks from NAntContrib into NAnt proper. But are we planning on getting rid of NAntContrib all together? What should be done with the NAntContrib tools like slingshot and the vs.net addin? ----- Original Message ----- From: "Tomas Restrepo" <[EMAIL PROTECTED]> Subject: RE: [NAntC-Dev] RE: [nant-dev] NAntContrib update was ( Updating Nant-Contrib to latest Nant) > > Hi Ian, > > << > totally. I have been meaning to move about 6 tasks into Nnt.DotNet ( gac, > xsd etc ) and some others into NAnt.Win32 ( comRegister etc ) First > priority was to get everything compiling. We can move tasks to their > appopriate namespaces as needed. However I would still consider tasks like > starteam optional - apologiesto those starteam users who consider them > crucial. > >> > > 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.... ------------------------------------------------------- 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
