----- Original Message ----- From: "Ian MacLean" <[EMAIL PROTECTED]> To: "Gert Driesen" <[EMAIL PROTECTED]> Cc: "Clayton Harbour" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, June 08, 2003 11:39 AM Subject: Re: [nant-dev] Nant cvs task using sharpcvslib
> of course but we're not talking every system out there. We are talking > about cvs - the number 1 scm used by open source projects. I would argue > that the cvs tasks should ship with the core nant distribution simply > because a large number of nant users will find it useful. I do *not* > think that we should ship clearcase tasks however because they target a > much smaller set of users. > and I'm sure Ant still ships cvs tasks as part of the core of tasks. Yes Ant indeed does ship with cvs tasks, but the reasons for that probable are : - backward compatibility - lack of third party libraries that include such a task I do agree that its very useful to have support for cvs out of the box, but perhaps that could be accomplished by including #cvslib (which itself can then include the cvs nant tasks) I certainly don't want to make a crusade out of this, I just want what's best for nant and the community ... and no I'm not saying that what I want is best, but it certainly doesn't hurt to disucss such things ... I would find it appealing to just being able to plugin a new version of #cvslib and at the same time get the corresponding nant tasks .... we'll never be able to keep up with the functionality third party libraries offer if we include tasks for them ourselves .... how will we cope with attributes, element, or even enum values that are supported with one version of the library and not with another ? wouldn't it be better to just move this stuff to the thid party library itself, where possible ? ofcourse not every vendor will be interested in providing NAnt tasks for its products, but as NAnt gains popularity more vendors will be ... until then, we could provide tasks ourselves ofcourse ... But I don't think it would hurt to discusss this with the #cvslib, NDoc, NUnit (...) teams ... Gert > > Ian > > > > > this is exactly what the Ant team is trying to accomplish ... and its > > actually working right now... major vendors (like Bea) now ship supporting > > Ant tasks with their products ... and I really think it makes sense ... > > > > although I think this is only possible when the NAnt API has stabilized, but > > it should be possible in the end ... > > > > what if there are 20 different popular scm systems, do you think it would be > > more managable to have nant support these 20 vendors or would it be easier > > to have each vendor support its own system ? > > > > what if version X of cvslib offers more functionality than version Y ? To > > support this in NAnt we "should" actually have 2 tasks (emphasis on should) > > like we have with NUNit right now, but if you move the tasks from NAnt to > > the vendor library itself, you'll never have problems like these ... If you > > use cvslib version X, you automatically also get the NAnt task corresponding > > with that version ... > sorry but this isn't true either. if the cvslib api remains stable then > its just a matter of dropping in the new version. > nunit2 completely reworked the api but Nunit1 still had a large user > base - hence the 2 tasks. > > > I think its impossible to have nant support each and every system out there > of course it is. > > > Gert > > > > ------------------------------------------------------- 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
