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

Re: [Subclipse-users] Subclipse error

From: Nayan Hajratwala <nayan_at_chikli.com>
Date: 2006-01-20 15:54:57 CET

On 1/20/06 9:24 AM, "Mark Phippard" <markp@softlanding.com> wrote:

> Nayan Hajratwala <nayan@chikli.com> wrote on 01/20/2006 09:19:40 AM:
>
>> Problems reported while synchronizing SVNStatusSubscriber. 0 of 1
> resources
>> were synchronized.
>> An error occurred synchronizing /myproject: Error
>> getting status for resource P/myproject
>> org.tigris.subversion.javahl.ClientException: Working copy not locked;
> this
>> is probably a bug, please report
>> svn: Working copy
>> '/Users/nayan/eclipse/workspace/myproject/server/target' is missing or
> not
>> locked
>
> This is an error coming from the Subversion client adapter such as JavaHL
> or JavaSVN. Usually it means something has corrupted your working copy.
> For example, perhaps an Eclipse build process deleted and recreated this
> folder named "target". So now the ".svn" folder that should exist inside
> of "target" no longer exists.
>
> Check if "target" exists. If it does, see if the ".svn" folder still
> exists inside it. It could be that this folder should not be versioned in
> which case you should delete it from your repository and add it to the
> svn:ignore property of the "server" folder.
>
> Mark

Thanks Mark -- "target" is an eclipse generated directory, and should not
appear in the repository. I tried various combinations of what you
described and nothing seemed to work. In the end, I deleted my local copy
and got a whole new fresh project from the server. That seems to have taken
care of the problem.

Thanks!

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Jan 20 15:56:27 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.