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

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

From: Gary Trakhman <gary.trakhman_at_gmail.com>
Date: Fri, 21 Oct 2011 08:02:17 -0700 (PDT)

> On Fri, Oct 21, 2011 at 10:41 AM, Gary Trakhman <gary dot trakhman at gmail dot 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
>

Like this one ^^, except in 1.6 time, each Project folder and subfolder would have its own svn. All projects are under the same repo.

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

An example of a similar setup:
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1046&dsMessageId=2639358

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

when you do "Import Existing Projects into Workspace", do you import more than one? A svn working copy contains multiple eclipse projects for me, and though it's kind of bad, we treat projects as basically slightly larger aggregations of java packages, so my workspace has about 180 projects.

>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2011-10-21 17:02:23 CEST

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.