On Thu, Nov 27, 2008 at 3:59 PM, Nick Boldt <nickboldt_at_gmail.com> wrote:
> Using Eclipse 3.4.1, Subclipse 1.4.6, I keep getting errors like these
> trying to synchronize projects in my workspace w/ the SVN repo.
>
> Problems reported while synchronizing SVNStatusSubscriber. 2 of 3
> resources were synchronized.
> An error occurred synchronizing /devstudio-workspace: Error
> getting status for resource P/devstudio-workspace
> org.tigris.subversion.javahl.ClientException: svn: This client is
> too old to work with working copy
> '/home/nboldt/eclipse/workspace-jboss/devstudio-workspace'; please
> get a newer Subversion client
> Error getting status for resource P/devstudio-workspace
> org.tigris.subversion.javahl.ClientException: svn: This client is
> too old to work with working copy
> '/home/nboldt/eclipse/workspace-jboss/devstudio-workspace'; please
> get a newer Subversion client
> org.tigris.subversion.javahl.ClientException: svn: This client
> is too old to work with working copy
> '/home/nboldt/eclipse/workspace-jboss/devstudio-workspace'; please
> get a newer Subversion client
> org.tigris.subversion.javahl.ClientException: svn: This client
> is too old to work with working copy
> '/home/nboldt/eclipse/workspace-jboss/devstudio-workspace'; please
> get a newer Subversion client
>
>
> My svn client is:
>
> $ svn --version
> svn, version 1.5.4 (r33841)
> compiled Oct 27 2008, 05:40:26
>
> Is there a newer svn client than 1.5.4? Or is 1.5.4 not compatible w/
> Subclipse 1.4.6? I'm on the verge of switching back to subversive -- help!
Subclipse 1.4 only works with SVN 1.5, so that is not the issue. If
you check your preferences are you using JavaHL or SVNKit?
Technically, neither should be capable of having a problem as both are
either 1.5 compatible or will not load by Subclipse. I have an FAQ
for understanding and getting JavaHL working:
http://desktop-eclipse.open.collab.net/wiki/JavaHL
If your preferences show JavaHL is not available, then take a look at
those docs so that you can use JavaHL.
I can only think of two ways you could run into this problem:
1) You have built a copy of Subversion's trunk code (1.6) and touched
your working copy with it. This would silently update it to the new
format from 1.6 and a 1.5 client could no longer read it. This would
be easy to test. You have shown that your command line is running SVN
1.5.4, so go into this working copy and run a command like "svn
status". If your working copy is not a valid 1.5 format the command
line will give the same error.
2) You are using SVNKit and either your install is broken or they have
some kind of bug. I've not seen or heard of any problems like this
with SVNKit.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-11-27 22:31:19 CET