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

[Subclipse-users] Broken Working Copy after using JavaSVN

From: Gunnar Wagenknecht <gunnar_at_wagenknecht.org>
Date: 2006-08-07 14:04:57 CEST


I have a few working copies that seem to be broken. I "mass" committed
multiple projects at once and used JavaSVN to get one changeset instead
of many. First, it looked like the commit went well. At least I got no
error message.

But now I have three projects where I have problems. I noticed it
because Subclipse seemed to have wrong states. According to the
decorations in the Navigator everything is fine. But the Synchronize
view showed me removed files under the "bin" folders of those projects.
That is interesting because nothing should have been committed under
them. And the bigger problem is, that the missing files are ".java"
files, which for sure never existed in those folders. It's also sure
that they were never committed to the repository. (See

After some investigation I noticed that all folders below the bin folder
had ".svn" folders. That's weird. because these folders are not part of
the repository. Anyway, I tried updating it several times and a cleanup
but now I'm stuck.

Basically the error messages are as follow. When updating the project I
get an error, because the project is locked. So I tried a cleanup on the
project but this fails because "bin" is not a working copy directory. I
tried it from Subclipse (now with JavaHL) and TortoiseSVN with the same

Is there any solution or should I delete the projects completely and
check them out again? I'm lucky because I don't have modifications in
them but what happens the next time?

CU, Gunnar

Gunnar Wagenknecht
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Aug 7 14:05:38 2006

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.