I have something similar.
My src directory contains about 13000 java source files and rebuilding
it takes about 15 minutes. What I've noticed is that after I perform an
update on the top-level directory, a complete rebuild occurs.
Is it possible that subclipse marks all files below the directory
selected for the update as dirty instead of only those files that were
updated?
The reason I think this is the problem is that an external "svn up"
followed by an eclipse "refresh" takes less time to complete...
Keep up the good work,
Folke
fuvo wrote:
> Hello,
>
> I'm using Eclispe and Subclipse (OS is Linux) for a long time. At the moment
> I'm using Eclipse 3.1.2 and updated subclipse to 1.0.1.
>
> After Eclipse is started, i make an update and everything is fine. But from
> this point it get's slower and slower. After nearly the 5th update the
> workspace needs 10 or more minutes to build and it is impossible to work
> with. It get's even worse, if i do a checkout on the commandline.
>
> Does anybody know how to fix this?
>
> Thank you,
>
> Volker
> --
> View this message in context: http://www.nabble.com/Help+needed%3A+Workspace+builds+%27forever%27-t1667868.html#a4519917
> Sent from the subclipse - users forum at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue May 23 15:27:40 2006