I am thinking that we should remove the CommandLine adapter as an option
in Subclipse. There are just several key features that are not
implemented reliably and I think users would be much better off using
JavaSVN, even if that means they have to setup a local svnserve instance
to access local repositories.
I am not talking about dropping it from svnClientAdapter. The CommandLine
is still an excellent choice for svnAnt users as it implements the
features an Ant user would need fairly well.
I just do not think it makes sense to offer an option in Subclipse that we
know does not work completely especially when there are good alternatives.
It is not that difficult to obtain JavaHL anymore and the only barrier to
using JavaSVN is file:// access for which there is a workaround.
Does anyone have any strong feelings against this? And if you do, are you
willing to invest the time to make the CommandLine adapter work? With the
new --xml options in Subversion 1.3, most features could probably be
implemented reliably if someone wanted to invest the time to do so. I do
not have the time or inclination to do so.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
Received on Sat Dec 3 01:01:00 2005