[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Subclipse-users] Working copy not locked - error, reporting as suggested

From: David Balazic <David.Balazic_at_hermes-softlab.com>
Date: 2007-10-25 09:45:08 CEST

Hi!

I use subclipse 1.2.4 in eclipse 3.3.1 on Sun JDK 1.5.0_13-b05 on windows XP Pro SP2.

In the "Team Synchronizing" perspective I selected Synchronize... , checked "Scope: Workspace"
and got this in the Console :

(note that I replaced all company internal names with "xxx#")

    Working copy not locked; this is probably a bug, please report
svn: Directory 'D:\eclipse_workspaces\331_1\xxx1\target\.svn' containing working copy admin area is missing

Also an error dialog appeared (title : "Problem Occured" , can not copy its text, it is roughly
"Synchronizing (Time of error: ..) Reason: Check the details" ) and following details :

Problems reported while synchronizing SVNStatusSubscriber. 10 of 11 resources were synchronized.
  An error occurred synchronizing /xxx1: Error getting status for resource P/xxx1 org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report
svn: Directory 'D:\eclipse_workspaces\331_1\xxx1\target\.svn' containing working copy admin area is missing
    Error getting status for resource P/xxx1 org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report
svn: Directory 'D:\eclipse_workspaces\331_1\xxx1\target\.svn' containing working copy admin area is missing
      org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report
svn: Directory 'D:\eclipse_workspaces\331_1\xxx1\target\.svn' containing working copy admin area is missing
      org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report
svn: Directory 'D:\eclipse_workspaces\331_1\xxx1\target\.svn' containing working copy admin area is missing

Then I did the same again got the same error again.

I use subclipse for weeks and this is the first time I got this error. Yesterday I upgraded
from eclipse-3.1.2/subclipse-1.0.6 to eclipse-3.3.1/subclipse-1.2.4

Regards,
David

 
Received on Thu Oct 25 09:45:23 2007

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.