"Marco Tedone" <firstname.lastname@example.org> wrote on 03/12/2006 05:33:32 PM:
> Hi, I had troubles trying to add one of my projects to a repository. I
> finally managed to get that added (by renaming it), and when I choose,
> the Eclipse plugin, to synchronize with the repository, I get the
> Problems reported while synchronizing SVNStatusSubscriber. 0 of 1
> were synchronized.
> An error occurred synchronizing /Jemos-sec: Error getting status for
> resource P/Jemos-sec org.tigris.subversion.javahl.ClientException:
> copy not locked; this is probably a bug, please report
> svn: Working copy
> is missing or not locked
> The error message asks to report this situation, which probably is a
> and here I am.
> Any help would be appreciated.
That message actually comes out of the Subversion library, so technically
they are asking you to report the bug to them. There are a lot of
scenarios that can lead to this error, but the one that Subclipse users
most often run into is that a build folder gets added to the repository.
Based on your folder structure above, this does not sounds like the case.
But the underlying problem is that for example the "tomcat" folder above
is likely missing the ".svn" metadata folder that should live inside it.
If that is not the case, you can try running Team -> Cleanup but the error
message that comes out of Subversion usually tells you if it thinks
running Cleanup will help.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
Received on Mon Mar 13 02:52:03 2006