Somehow I've fallen into
Subversion hell.
Firstly, I wanted to play with a new Eclipse project here on my home machine -- not usually used for Java development. This is where things started to go wrong; trying to check out any SVN project would cause Eclipse to crash with an EXCEPTION_ACCESS_VIOLATION in 'org.tigris.subversion.javahl.SVNClient.info2'.
After reinstalling Eclipse and failing again with
Subclipse 1.2.x, some research led me to believe that the solution was to upgrade the Subclipse client to 1.4.x. I did so, slowly.
At the same time I upgraded my
TortoiseSVN from 1.4.x to 1.6.x, because it was having difficulty accessing existing subversion repositories on my system. Which seemed to be fine, except it required a system restart to work.
Once I got my Eclipse installation running, things were working fine for a few minutes. I could check out, update, branch and commit my folders. However, as soon as I did some refactoring within Eclipse, things started to go wrong. Now I can't check out or update anything from anywhere.
If I try $ svn info (svn --version = 1.5.3), I get "This client is too old to work with working copy '.'".
If I try it from within Subclipse (latest version), I get the exact same error message. Subclipse is using its own SVN client too, at version 1.5.6.
It appears TortoiseSVN includes its own SVN client 1.6.x, which is too advanced for any of my existing SVN tools. When did SVN tools decide to all use their own incompatible clients??
So all my other SVN clients are broken, until I either downgrade TortoiseSVN to 1.5.x, or they release a 1.6.x for Subclipse... sigh.
EDIT: It turns out you don't need to
download a proprietary client for SVN on Windows. You can still directly download the Subversion packages for Windows; they're just
hidden in the Apache 2.2 folder.