and I'm sure Ant still ships cvs tasks as part of the core of tasks.
Ian
sorry but this isn't true either. if the cvslib api remains stable then its just a matter of dropping in the new version.
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 ...
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 thereof 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
