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

Re: locking problems

From: Daniel Bradby <dbradby_at_bigpond.net.au>
Date: 2004-02-24 01:33:45 CET

You might want to try using "svn cleanup" from the command line (feature
to come in Subclipse) and of course upgrade to Subclipse 0.9.0

Hagen, Leila wrote:

> Hello,
>
> I’m running Subclipse 0.81 and eclipse 2.1.2. I believe we’re running
> SVN .37 (how do I find out the version number?). I was committing
> changes for 6 files and got an error that said the commit succeeded.
> After that, whenever I tried to do anything I got an error that said
> “Attempted to lock an already-locked dir” on just one of the two
> directories the commit affected.
>
> I used the svn cleanup command outside of eclipse against the affected
> directory to reset the locks in my working copy. Now eclipse is
> convinced that this directory and the associated files are not part of
> the repository. I’m getting a null pointer exception from the plugin:
>
Received on Tue Feb 24 11:33:45 2004

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.