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

[Subclipse-users] Locked jars because of a running program, then updating those..

From: Johan Compagner <jcompagner_at_gmail.com>
Date: Fri, 30 May 2008 16:06:07 +0200


This will result in a invalid state of things..

First suddenly i cant update my project anymore:

update F:/workspace/j2db_core -r HEAD --force
    Attempted to lock an already-locked dir
svn: Working copy 'F:\workspace\j2db_core\build\lib' locked

Second the jar that was deleted in this case is suddenly is an outgoing
But synchronizing gives me this:

    Can't find an entry
svn: 'F:\workspace\j2db_core\build\lib\concurrent.jar' is not under version

How can i set this straight?

And the subclipse code should be able to handle this case a bit better i
If a file that he wants to overwrite or delete because of an update. If that
doesnt work
he should just rollback the complete update (or just that file) and set that
one as a one that still has to be done.?

Received on 2008-05-30 16:06:20 CEST

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.