IMHO all stuff which relies on an external system (other than JDK or the OS :-) should be in an AntLib. And scm´s rely on the scm-server. So a quick view on the core task list gave me: - CVS: Cvs, CvsChangeLog, CvsVersion, CVSPass, CvsTagDiff mmh - not more ...
And of course the optional stuff ... The cvs task could try to load the java component and fall back to the command line client. Jan >-----Ursprüngliche Nachricht----- >Von: Kev Jackson [mailto:[EMAIL PROTECTED] >Gesendet: Dienstag, 9. August 2005 05:42 >An: Ant Developers List >Betreff: commons dev list CVS component > >It looks like there's a possibility that a java based CVS >component could soon be in commons/incubator, having noticed >comments in the CVS task source about using a pure Java >version (jCVS) and there being problems with IP, I can only >hope that this (potential) component would solve that issue >and allow us to remove the dependency in the current code - do >we also want to maintain CVS as part of Ant core? I know it's >there for historical reasons, but with svn already being in >antlibs, would now (with this component) be an appropriate >time to start moving stuff (all SCM) that really isn't core >into the antlibs? > >Thoughts >Kev > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] For >additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
