this does looks like this thread

we checked the situation and we had found that the problem can happen in case if working copy is locked by external process in time of update.

for example, the process tsvncache that related to tortoisesvn time-to-time produces conflicts with working copy access and javasvn library cannot complete working copy modification in correct way. as result working copy goes into "obstructed" state, i.e. it is damaged.

the same diagnosis related to any process which locks working copy in time of working copy meta-data modification. (we found same behavior for ms visual studio 2005 express edition, but i don't know why the studio locks wc?)

so be sure to make the checkout with the least possible number of application running.

another source of conflict could be:

the svn 1.4.x-compatible clients are automatically converts working copy into 1.4.x-compatible format. at the current moment subversive default client is incompatible with svn 1.4.x working copy format.

so, if you performed any modification of the working copy using command line svn client in your case you will get "obstructed" state indicated over the resources in the workspace tree.

in order to resolve the problem i will propose you to switch svn client option and select svn kit 1.1.0-based client or native javahl 1.4.2 client.
next, if resources already decorated as "obstructed", please close and then open again corresponding projects or simply restart eclipse ide in order to reload svn meta-information cache.

now : the exact version may not be the same for you, but that is another lead to check.

Related Query

More Query from same tag