Re: org.tigris.subversion.javahl.ClientException: Working copy no t lo cked

[Tom Henricksen <To...@A-t-g.com>]

Mark,
Thanks a lot!  That was it we modified our build.xml to not delete the .svn
folder and it now works.
Thanks,
Tom

-----Original Message-----
From: Mark Phippard [mailto:markp@softlanding.com] 
Sent: Wednesday, August 23, 2006 3:05 PM
To: Tom Henricksen
Cc: users@subversion.tigris.org
Subject: spam Re: org.tigris.subversion.javahl.ClientException: Working copy
not lo cked

Tom Henricksen <To...@A-t-g.com> wrote on 08/23/2006 03:45:22 PM:

> We have a machine with Eclipse 3.1.2, Java 1.4 and Subclipse 1.0.3. When 
we
> checkout from Subversion then run our ant build and then try to 
Synchronize 
> we get the following error
> Problems reported while synchronizing SVNStatusSubscriber. 0 of 1 
resources 
> were synchronized.
>   An error occurred synchronizing /bop-med: Error getting status for 
> resource P/bop-med org.tigris.subversion.javahl.ClientException: Working 

> copy not locked; this is probably a bug, please report
> svn: Working copy 'C:\Documents and 
Settings\mikel\workspace\bop-med\merge' 
> is missing or not locked
>     Error getting status for resource P/bop-med org.tigris.subversion.
> javahl.ClientException: Working copy not locked; this is probably a bug, 
please report
> svn: Working copy 'C:\Documents and 
Settings\mikel\workspace\bop-med\merge' 
> is missing or not locked
>       org.tigris.subversion.javahl.ClientException: Working copy not 
locked;
> this is probably a bug, please report
> svn: Working copy 'C:\Documents and 
Settings\mikel\workspace\bop-med\merge' 
> is missing or not locked 
> We tried the fix from the FAQ with no luck.  We have tried reinstalling 
> Eclipse and Subclipse resulting in the same error.

Reinstalling software is not going to make a difference, it is your 
working copy that has the problem.  When you ran your ant build it likely 
has a step that is deleting a folder or everything in that folder.  If 
that folder is "versioned", then it contains a folder named ".svn".  This 
is what makes it a working copy.  Once ant deletes that folder, the 
working copy is corrupt.  The best answer is usually to not have the 
folders that contain your build output versioned.  But otherwise, you need 
to take steps to protect any of your .svn folders.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org