Re: Obsolescing NAntContrib [was RE: [nant-dev] Re: [Nant-users] 0.8.3 final]

[Tomas R. <to...@mv...>]

Hi David,

<<
I think what Cash is asking is the same thing I proposed a week or two
ago: solve the NAntContrib problem by merging the projects and
obsolescing the contrib project completely.  The NAntContrib tasks are
*core* to what most of us use NAnt for anyway!  Just move all the
NAntContrib tasks into the mainline NAnt source before streeting 1.0.
>>

It's funny this is brought up again, as it isn't the last time (I proposed
this  myself a couple of months ago, but the opinion that it should be left
alone prevailed then). FWIW, I still support this proposal.

<<
I have attempted and failed a couple times to build NAntContrib from the
sources I downloaded from cvs.  There are no released files for the
project.  There have been no nightly builds since June 03.  There's no
traffic on either the user or developer lists to speak of; the last post
to the dev list was July 30.  It seems prima facie an abandoned project
sans-maintainer and with no community or activity.
>>

I personally haven't been tracking nant and nantcontrib's development for a
while because of work-related activities, but if you've got a specific patch
you want to submit to nantcontrib, let me know and at least I'll do my best
to ensure it is committed (fwiw, the verboseness problem with the sql task
was the result of the last attempt made to ensure nantcontrib compiled
against nant when the logging changes were made).

We should also try to ensure it at least builds..

-- 
Tomas Restrepo
to...@mv...