Easy way to complicate your day

…. corrupt your .svn file structure on your local system. Then, disconnect your project from Subversion via the Subclipse plug-in. Now, try to get things up and running again.

Steps thusfar:

* copy my working copy to an -old folder (just in case I need something).

* remove the working copy

* Do a new checkout from Subversion (command-line style, since Eclipse is still unhappy).

* Hmmmm…. that didn’t help me within Eclipse. OK, do a checkout from the SVN Repository tab within Eclipse: that’s deleting my new working copy folder and getting a fresh new checkout.

Ugh. I hate it when I have to wrestle with configuration management.

Useful resources:

(1) help files in Eclipse for Subclipse plug-in. (Team –> Share didn’t help me much, but was useful to find out about.)

(2) Version Control with Subversion

1 comment

  1. It sounds like you are running into a problem sort of caused by Subversion 1.4. It introduced a new working copy format, to local working copies touched/created by a SVN 1.4 client can no longer be read by a Subversion 1.3 or earlier client.

    The latest versions of Subclipse (1.1.9 and 1.0.4) include SVN 1.4 clients but earlier versions were using 1.3.

    Update your Subclipse to the latest version OR be careful to only touch a given working copy with one specific client and you will be OK.

    Mark Phippard
    http://markphip.blogspot.com

Leave a Reply

Your email address will not be published. Required fields are marked *