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

Re: [Subclipse-users] Building workspace takes a long time after merge

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-06-04 22:57:38 CEST

On 6/4/07, Ruslan Sivak <rsivak@istandfor.com> wrote:
> We have a fairly large codebase (65k files, 37k folders, 3.5GB including
> the .svn folders). When I do a merge, building workspace seems to take
> several minutes even if there is only 1 file that's updated. I think
> this is because subclipse does not tell eclipse what files have changed,
> and therefore eclipse is forced to refresh and rebuild the workspace.
> I'm not sure if I'm on the right track here, but if this is the case, is
> there anything I can do to fix this? Is there another plugin, perhaps,
> that is better able to deal with large projects?

Subclipse does both. We notify Eclipse but then we ask Eclipse to
refresh your project. There are scenarios with merge and switch where
if we do not do this, then all the decorators do not refresh.
Generally, even on a very large project if it is all in synch with
Eclipse a refresh does not take long. For example, after doing a
merge, right-click on the same project and choose the Refresh option.
It should run fairly quickly. There is no reason the refresh after
the merge should take a long time either, but if you have done
something like an external build using Ant, then it can.

We tried to remove the refresh duing the 1.1.x release cycle but new
problems quickly were reported and we put it back.

Mark Phippard
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Jun 4 22:57:46 2007

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.