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

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

From: Mark Phippard <markphip_at_gmail.com>
Date: Mon, 24 Oct 2011 11:47:16 -0400

On Mon, Oct 24, 2011 at 11:26 AM, Rich <collabnet.rich_at_xoxy.net> wrote:
> We've run into the same problem.  It took a while to figure out that subclipse was the cause as we also use TortoiseSVN as well as other tools on the same working copy but since uninstalling subclipse it hasn't happened again.  I've got the same workspace layout as gtrak - we have many related Eclipse projects in a large repo, so we simply checkout a trunk working copy somewhere, open the folder as an eclipse workspace and then go to File->Import->Existing projects.  This has always worked well for us in previous versions of subclipse and we had no idea that it wasn't a recommended use case.  Does anyone have any workarounds or ideas where the problem may lie?

Workaround is simple. Just make a small change in how you do it so
that it complies with what Subclipse expects. When you open Eclipse
and create a workspace, specify a new non-existing folder somewhere.
Then use your same File > Import >Existing projects option. Having a
.svn folder in the root of the workspace is unexpected. We have not
tracked down what causes the folder to be deleted yet, but the
workaround will not have the same problem as this how I have always
used Eclipse.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2862422
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2011-10-24 17:47: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.