Hi, When I was building the task I was really keen on a declarative name but there may be benefits to dropping the cvs task down a level and wrapping a number of version control systems in one namespace.
Actually what I hope might come out of an exercise like this is some common behavior to build a unified version control api (on my todo list (-:). I am with Ian on the second part though, I think these tasks should wrap what #cvslib is doing. Gives nant a little more flexibility if really#cvslib comes along to replace #cvslib :-). -----Original Message----- From: Ian MacLean [mailto:[EMAIL PROTECTED] Sent: June 7, 2003 8:28 PM To: Gert Driesen Cc: Clayton Harbour; [EMAIL PROTECTED] Subject: Re: [nant-dev] Nant cvs task using sharpcvslib Gert Driesen wrote: > Great job, Clayton ... > > I only have two minor concerns : > > - should we have a more general name for the namespace for scm related tasks > (and have a subnamespace for cvs ?), so we can add more scm tasks later on > (eg. for sourcesafe, pvcs, ...) ? that should be easy enough - just move it all down a directory level > - Can't these tasks actually be part of #cvslib itself ? That doesn't make so much sense. Should the ndoc task be part of ndoc, the zip tasks part of ziplib ? Ian ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
