Re: JavaSVN (Re: Subversion Branding / "whole product" (Was: Re: SmartSVN - a new Subversion client))

> It is not /necessary/, that the working copy of the client using
> JavaSVN must be compatible to the one of the command line SVN client.

I both agree and disagree with this.

On the one hand, I think JavaSVN could have chosen to invent their own WC
format, and that would have been fine, and perhaps even desirable.
However, once they decided to go with an SVN-like WC format, it then
becomes imperative that what JavaSVN does with that WC is 100% compatible
with the CLI.

I partly wish JavaSVN had tried creating its own WC concept, if for no
other reason than to see if some of the "WC-issues" like pristine copies
could be improved upon, but at the same time it is nice to be able to fall
back to the CLI for functions that JavaSVN has not implemented yet. So
they probably made the right choice.

I agree with everything else that has been said. It would be great to get
JavaSVN brought into the Subversion repository.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 26 17:29:41 2005