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

On Fri, Oct 21, 2011 at 10:41 AM, Gary Trakhman <gary.trakhman_at_gmail.com> wrote:
> 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).

For clarity, lets call these "working copies". They are not "repositories".

>  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.

If I were to draw a diagram of your Eclipse workspace would it look like this:

/workspace
|- .metadata
|- .svn
|- Project1
|- Project2

Or like this:

/workspace
|- .metadata
|- Project1
|-|- .svn
|- Project2
|-|- .svn

I have never seen one like the former. The second is what I would
call a "typical" workspace.

I do something else altogether, but sort of like what you describe. I
have Subclipse checked out here:

$HOME/work/subclipse

This has /trunk/plugins and that folder has a folder for each plugin project.

My Eclipse workspace lives at:

$HOME/Documents/workspaces/e3.7

This folder is empty except for .metadata. I use Eclipse File >
Import > Existing Projects into Workspace to point the workspace at my
external checkout.

Of course, I also have other more typical workspaces that look like
the second example I gave,

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2859931
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].