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

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

I have this nagging feeling that there have always been problems with
this kind of setup. I will do some searching. The ramifications of
the new working copy format with whatever bugs might have existed
might force us to look at those problems differently.

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

Yes. In my case it is only a couple dozen projects but definitely
more than one. I definitely recommend this setup, I have been
planning to blog about how nice it is for performance and memory usage
with the new 1.7 working copy format. When you do the Import, be sure
to NOT check the box that tells Eclipse to copy the projects. You
just want it to "point" to the projects. We have supported this
scenario in Subclipse for a long time. Our documentation, which has
not really been updated since 1.0, even describes it:

http://help.collab.net/topic/org.tigris.subclipse.doc/topics/wc-outside-workspace.html

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