> What would be helpful is if we can identify which tools
> are currently used
The CVS command line over SSH, obviously. TortoiseCVS. WinCVS. We could
all survey our projects, or put up a Wiki page to collect what people are
actively using.
--- Noel
FWIW, Subversion is working quite well for us in a Corporate Intranet. Blending
modules for
content management (that can be edited in WYSIWYG form, either in-situ or in
off-line modes) and
others for code make it a very compelling replacement for CVS at the project
level, and Wikis at
the
> From: Greg Stein [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 11, 2003 11:31 AM
> One of the previous concerns was tool support. Since then, we have SVN
> capability in ViewCVS, and there is also an SVN plugin for Eclipse and IDEA,
> and several GUIs. SVN itself has been stable for a long
One of the previous concerns was tool support. Since then, we have SVN
capability in ViewCVS, and there is also an SVN plugin for Eclipse and IDEA,
and several GUIs. SVN itself has been stable for a long while; the only real
concern [for the ASF] is the related tool support.
For Maven
I'm all +1 on moving our repositories forward, but I've got used to some
of the nice tools surrounding SVN that I don't want to miss.
And then there is the question of things like maven supporting SVN just
as well as CVS.
For bk there is some sort of "CVS compatible read-only view into the
