If you have worked with SVN tools in Eclipse (Subversion, subversive) before, then you are likely familiar with the \'working copy \'XXX\' locked...\" error.
I found
This happened to me when I copied a directory from another subversion project and tried to commit. The soluction was to delete the .svn director inside the directory I wanted to commit.
Generally a .lock
file is created and it decides lock/unlock state checking the existince of this file. I think if you delete this .lock
file only, then the problem will go away.
After more exploration and testing, it appears that this issue was being caused by debugging the plugin and using breakpoints. SVN/Subclipse apparently didn't like having breakpoints midway through their execution and as a result this lock files were being created. As soon as I started just running the plugin, this issue disappeared.
Solution: Step1: Have to remove “lock” file which present under “.svn” hidden file. Step2: In case if there is no “lock” file then you would see “we.db” you have to open this database and need to delete content alone from the following tables – lock – wc_lock Step3: Clean your project Step4: Try to commit now. Step5: Done.
The following should unlock a locked working copy (tested on svn client version 1.6.11 and elipse version: Mars.2 Release (4.5.2))
step 1: (go to working copy directory) $cd working_copy_dir
step 2: (connect to svn sqlite database) $sqlite3 .svn/wc.db
step 3: (delete all records from table WC_LOCK) sqlite> delete from WC_LOCK;
step 4: (disconnect from sqlite 3 database) sqlite>ctrl + d
step 5: (from eclipse) right click on your working copy, then click Team -> Refresh/Cleanup
This will happen when something went wrong in one of your folders in you project.
You need to find out the exact folder that locked and execute svn cleanup
under the specific folder.
You can solve this as follows:
svn commit
command to find out which folder went wrong.svn cleanup
. Then it's done.