Accepted answer

I was having the same error message using subclipse with javahl on a project that is out of the workspace directory. Changing to svnKit has resolved my problem.


Sometime ago I had a similar issue. Seems that Subclipse (or Eclipse) stores the absolute path of your working copies. The cleanest solution is to export again your repository to the new path.

If you have non-committed code, then you can copy it on top of the clean export (without the .svn folder)


I too had this issue and I simply deleted the project from the workspace (leaving the files on the files system in tact).

I then imported an svn project into the workspace.

Import->SVN->Checkout Project From SVN.

I used my existing repository location to pull the files in.

This issue was caused when I changed Eclipse editions and used a Subclipse plug-in that was a version ahead of what I should have used.

I uninstalled the newer version and installed the correct older version and all worked well.


Hard to say without further information.

Did you move the whole workspace or just the content?

Also, you can try creating new workspace from scratch and check out the whole project again.

Alternatively, you may try deleting the .metadata directory and relink the project again using File -> import -> existing project into workspace and then relink the SVN data through Team -> Share projects (with an 's'), or maybe just do this last bit after first disconnecting the project from SVN.


I have the same problem

I had a new project, added it to SVN. Then everything works as normal, until I try and refactor-rename any java file, I get:

move D:/dev/sk_ws/ge-parent/ge-core/src/main/java/com/skillkash/ge/beans/ D:/dev/sk_ws/ge-parent/ge-core/src/main/java/com/skillkash/ge/beans/
    Path is not a working copy directory
svn: Path 'D:\dev\sk_ws\ge-parent\ge-core\src\main\java\com\skillkash\ge\beans\' is not a directory

Now the SVN URL is:


and the repository root is:


Obviously just sharing the project then trying to move a file using subclipe does not work - it must be a bug. I have to do all my refactoring outside eclipse, and hand edit all the files which are affected.


Right click the project folder : Team -> Update to Head

This will bring back the directory. Delete it again and Commit


In my case I had the folders of the projects in the Project Explorer and just had to reopen the project


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 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.


checkout the whole project to a temp dir, then I copied the first level .svn directory and replaced my working copy .svn folder with this.

It woks for me.


I had added a png file to my project, but I got this error trying to rename or delete it. Cleaning and refreshing the project didn't do anything.

I went into the svn Team Synchronizing perspective, right clicked on the file and deleted it. That solved my problem.


  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.


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.


I'm sure there are many causes with different solutions, but I found the one that worked for me at Dan Wilson's blog. Simply remove the offending folders from the workspace (probably saving them if they have new content), update (letting Subversion recreate the folders), then move the contents back into the fresh folders in your workspace.


I got the error when I tried to rename a class by changing the case from DAO to Dao in Eclipse.

I had to rename it to something like Dao2 and then was able to rename it to Dao.


What worked for me: Do a "refactor - rename" on the project => after that do it again to rename it back to the original name.


Edited to add: Nope, spoke too soon. This doesn't fix it. Some files just seem not to exhibit the problem.

The following seems to solve the problem:

  1. Team > Disconnect.
  2. Quit Eclipse.
  3. Blow away .metadata/.plugins/org.tigris.subversion.subclipse.*.
  4. Restart Eclipse.
  5. Team > Share.

Not sure how the old path was actually being stored in the plugin prefs, but it must have been in there somehwere. It's kind of pathetic of Subclipse to store absolute paths, but apparently it is.

There's a bug filed on this, or at least on the same error message. No context. Fifty cents says it gets rejected.


I just did a "Team -> Cleanup" and this exact error went away! I also got this error because I moved between machines and the path wasn't the same.

Using Eclipse 3.6 and the Subversion 1.6 plugin.

Update in 2016: Still works perfectly with Eclipse 4.5.2 and Subclipse 1.10.


You need to delete the .syncinfo files. This is easily done (in most cases) by closing and opening Eclipse, however you can also do so manually as in the following:

To delete the cache, close Eclipse. The cache is stored in:


So you can just find and delete all files named .syncinfo in


Quoted from this article:

Related Query

More Query from same tag