Subclipse complains "Path is not a working copy" after moving workspace

David_Moles_27358 0
Viewed 40858

I recently moved my Eclipse workspace directory and now Subclipse complains every time I open a file, dumping to the console something like:

Path is not a working copy directory

svn: '[original (pre-move) directory path]' is not a working copy

No such file or directory

This also happens when I explicitly try to view the history of a file. This persists across SVN cleanups, closing and re-opening Eclipse, etc.

Update, checkin, checkout and so on all seem to work fine, and Tortoise doesn't complain at all, so clearly it's not the SVN metadata that's screwed up, it's some Subclipse-specific metadata. Can anyone tell me how to blow this broken metadata away?

Edited to add: "Team > Disconnect" followed by "Team > Share" doesn't solve the problem.

Edited again to add: I've grepped through the whole .metadata directory and one of the project directories for a unique element of the old path and can't find it anywhere except in .metadata/.log (the error message itself) and some old Findbugs warnings. Very nice.

subclipse svn eclipse
18 Answers

For me, this error message was caused by an out-of-date installation of Subclipse, and the underlying SVNKit and JahaHL libraries. I have been using TortoiseSVN outside of Eclipse to manage my project directories, and my recent upgrade to the 1.8.x series of (Tortoise)SVN tools broke my working copies for Subclipse.

All I had to do to fix, was go to Help->"Install New Software..." and click "Add..." to add a new update site. I picked the latest update site for the latest release on http://subclipse.tigris.org/servlets/ProjectProcess?pageID=p4wYuA and upgraded Subclipse from there.

Then all my existing projects just worked, and I could reconnect to the one I had already tried disconnecting from without problems.

user_13904300
  1. Right click on the project and select Teams -> Switch to another Branch/Tag/Revision.
  2. Select the appropriate Branch/Tag/Revision that the project should be tied to and click OK.
  3. Give Eclipse some time to process the changes.
  4. Restart Eclipse for the changes to take affect.
user_37837500

I just got this error when I was trying to update some .java files. The problem was I was trying to update the files but the folder that contains that files didn't exist in the path so when I sync and update the folder it works at the first try.

So, dont try to sync files, try to sync the folder.

user_96034080
Related