On 6/4/05, Mark Phippard <MarkP@softlanding.com> wrote:
> > But I've also gotten them when a file is out of sync with the
> > repository somehow. This used to happen, but no longer does, when
> > using a plugin to an IDE which used the javaSVN library. This has
> > since been fixed. It is entirely possible that something like
> > tortoise or other clients can cause this problem.
>
> This isn't really true. JavaSVN is a reverse-engineered Subversion client.
> It is going to be susceptible to errors like this, especially before it
> gets to a 1.0 state. I am not aware of any other project that is
> attempting to do this.
>
> TortoiseSVN, RapidSVN, Subclipse via JavaHL etc... are just GUI's wrapped
> around the Subversion API, the same API that the Subversion command line
> uses. So with the possible exception of using the API incorrectly, any
> problems like this would have to exist in the Subversion API itself to
> effect the GUI clients.
Slightly OT:
That isn't exactly true either...JavaSVN isn't a "reverse engineering"
of the client. That would imply not knowing the protocol. The protocol
is documented, so in effect, it's just another implementation, albeit
with some bugs still. I know that's a nitpick, but I think it's an
important distinction.
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jun 4 15:49:25 2005