I have the same problem, and this is, I believe, due to a basic
misunderstanding about compatibility of older clients with the newer
*server*, versus compatibility of older clients with *local sandboxes*
created with a newer client from the newer server, then accessed with
Subclipse (and RapidSVN, for that matter).
Once the .svn/entries files on the local copy get changed from the old,
pre-1.4 xml format to the new, 1.4 format, Subclipse is no longer
compatibile and you will get the error message Kristian refers to. I can
confirm this same behavior on OS X and Win XP.
So yes, there is sever compatibility. If you only use Subclipse to access
your local working copy, you are fine. However, if you use the 1.4 CLI to
access the local working copy as well, it will convert the .svn/entries
files the first time it runs, and Subclipse barfs.
I use the svnant task and I was finally able to get things to work by using
the version 1.1.0-RC2 version, and then remove the ganymede.jar, javasvn.jar,
and javahl.jar, and set the javahl attribute in the svn task to "false" in
the build script, which forced svnant to use the command line interface
which is installed on the box.
It would be nice to see this get cleared up. Hope this helps sort it out.
On 11/10/06, Mark Phippard <firstname.lastname@example.org> wrote:
> Kristian Duske <email@example.com> wrote on 11/10/2006 03:07:20 PM:
> > I have just reinstalled Eclipse 3.2.1, along with the latest
> > Subclipse version (1.1.8). I have configured subclipse to use the
> > JavaSVN interface. Every time I want to commit anything, I get the
> > following error:
> > svn: This client is too old to work with working copy
> > '<path_to_resource>'; please get a newer Subversion client
> > <path_to_resource> being the actual file system path to the file I'm
> > trying to commit, obviously.
> > I have searched the mailing list and found this: http://
> > subclipse.tigris.org/servlets/ReadMsg?listName=users&msgNo=7969. It
> > doesn't help me though, since I am using Mac OS X 10.4.8. I have
> > installed the latest subversion binaries (1.4.2) from DarwinPorts,
> > but to no avail. But since I'm using the pure Java interface, I
> > wouldn't know why the svn binary would even need to be present on my
> > system, anyway.
> > The server I'm trying to connect to uses subversion 1.1.4, but I
> > guess this doesn't have to do anything with my problem. Everything
> > worked fine before I upgraded to the latest version of Subclipse.
> > Can anyone point me in the right direction on this? I'm at a loss
> > here as to how I might help myself.
> The version of JavaSVN included in 1.1.8 would not give this error. So I
> would review your install to see if an older version is present. Maybe
> restart Eclipse with the -clean option. Not sure how you do that on OS X.
> Maybe from Terminal?
> To unsubscribe, e-mail: firstname.lastname@example.org
> For additional commands, e-mail: email@example.com
Received on Fri Nov 10 21:48:52 2006