Folke Lemaitre <folke@landc.be> wrote on 05/23/2006 09:27:25 AM:
> 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...
Subclipse does not mark all of the files dirty. I also think if you were
to look at the generated .class files you would see that the right files
were rebuilt. The issue is that the svn up likely triggered a Subclipse
status crawl and the build process is waiting for it to complete. So the
time is really being taken by Subclipse's updating of status information,
not the actual build.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
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:41:26 2006