# Re: [Subclipse-users] WC state problems

From: Mark Phippard <markphip_at_gmail.com>
Date: Thu, 8 Oct 2009 09:19:48 -0400

On Thu, Oct 8, 2009 at 9:14 AM, David Balažic
<david.balazic_at_hermes-softlab.com> wrote:

> I use subclipse 1.6.5 with Eclipse Java EE v3.4.2 (M20090211-1700).
>
> It happens "all the time", that SVN is confused, when something in the
> working is not as it would like it. Example:
>  - I delete a folder with contents.
>  - I call Team / Cleanup on the parent project

Cleanup is a very-specific Subversion command that only cleans up
after certain Subversion commands that are killed in the middle of
running.

> org.tigris.subversion.javahl.ClientException: Path is not a working copy directory
> svn: 'F:\data\eclipseWS\X\Y\Z' is not a working copy directory
>
> org.tigris.subversion.javahl.ClientException: Path is not a working copy directory
> svn: 'F:\data\eclipseWS\X\Y\Z' is not a working copy directory
>
> (the same error twice)
>
> The directory has been since recreated by the build process, but the .svn folders are missing.
>
> So why is SVN not able to resolve this situation? It keeps repeating the above error
> each time I run "Cleanup".

If you delete .svn folders your working copy is broken and cannot be
repaired other than via checkout. In some cases, you can remove the
folder that is missing the .svn folder and then run svn update on a
parent and it will recreate it. I think that might actually only work
with missing files though.

Subversion 1.7 is rewriting the working copy code to remove the .svn
folders. This will immediately make all problems like this disappear.

For now, it is your responsibility to make sure you do not do things
that delete or alter the .svn folders.

```--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2404952
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
```