[Subclipse-users] .svn being wiped out with subclipse 1.80 on a svn 1.7 repo

Had a twitter discussion with Mark Phippard, to recap:

Had used svn 1.6 for a while with few problems on eclipse indigo and subclipse.

Upgraded cygwin svn to 1.7, downloaded tortoise 1.7, used tortoise to upgrade my workspace to svn 1.7's format. The eclipse workspace is the top-level svn working directory, not the .metadata, just all the projects' project-specific stuff. Updated subclipse to 1.8. Booted up eclipse, and I find that my top-level .svn is gone (my repo became an un-repo). Did a clean check out from tortoise and kept the same .metadata. Booted up eclipse, .svn is gone again. Removed subclipse, created a new workspace with new metadata, checked out the source again, then tried to finally do some work :-).

Normally there would be issues (tree conflicts) using the subclipse with the workspace under top-level svn. I get around those by using tortoise to actually do updates and commits on workspace-level, then let subclipse do the right thing with regards to refactoring, marking things deleted, etc. With it wiping out the .svn directory, this workflow is no longer possible.

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2859920

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2011-10-21 16:42:46 CEST