Mike Roberts: >There's been discussion of this on nantcontrib-dev this week Out of curiosity, does anyone have an idea of how much overlap there is between the two lists? (I am on both, and so I have been seeing this discussion in both forums) I ask, because if (as I suspect) most everyone that is on NAntCdev is also on NAntDev, this is further incentive to rejoin the two projects, and find a way to make the NAntC components optional downloads -- a single project doesn't mean a single install after all, and as someone pointed out, users don't care where something lives -- until they can't find it -- and just want to install and go. So, if there were only one project (i.e. no NAnt-Contrib) you could offer a complete download (that had the core engine, core tasks, and all optional tasks) and then ala carte downloads. For example, there could be the following items on the ala carte downloads: * core Nant (which would roughly what is now the NAnt project) * one group for each logical grouping of optional tasks (e.g. mono specific or database specific or something) * all optional tasks Given that NAnt itself is used by many of us for precisely for this purpose (to automatically build multiple versions of our products), it seems that it should be easy to set up -- if the projects were merged. Best, Bill William E. Caputo ThoughtWorks, Inc. -------- "Its the foolish cat that looks at the finger when it is pointing at the food" ------------------------------------------------------- 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 _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
