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

On Mon, Oct 24, 2011 at 12:42 PM, Rich <collabnet.rich_at_xoxy.net> wrote:
> Thanks for the quick response.  I just did a quick grep of the code to see if there were any obvious culprits... might SVNUIPlugin.cleanProjects() be the cause?  Admittedly I don't know the code but it seems to be deleting any .svn folders that sit in the parent folder of a subclipse managed project if they don't contain a 'text-base' folder, which they won't once they been upgraded to the SVN 1.7 working copy format.

That sounds like a good lead and if nothing else that code should be
changed to look for the new folder name. I am not sure why the code
exists in the first place. My guess is that is has something to do
with the hack we had to do to allow projects to do a single atomic
commit. Maybe this code was in place in case Eclipse crashed before
the hack cleaned up the .svn folder it created? SVN can do this
natively now so we no longer need the hack so maybe this code can be
removed.

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