Simon Whittaker wrote:
> Deadman, Hal wrote:
>> Subversion is supposed to minimize network traffic but it assumes your
>> working copy is local and the repository is remote. Accessing a
>> repository over a VPN shouldn't be slow (aside from the initial checkout
>> of a large file set). When I watch the SVN console in subclipse it seems
>> that the subversion access is fairly quick and then it takes awhile for
>> Subclipse to update icon overlays or whatever it does post commit. I run
>> it in the background so it doesn't bother me much.
> Is there anyway to control what subclipse does post-commit? It seems to
> me as well that the actual commit is reasonably quick but that it takes
> an absolute age to do whatever it does afterwards.
If I know that a huge post commit action is coming, I usually turn off
auto build before.
I am not sure, why the post commit takes so long, but since I get the
message regularily from eclipse that the file was altered on the local
filesystem after commit, I am sort of sure, that the Subclipse plugin
marks the files as dirty for whatever reason (probably it pushes up the
date) and then eclipse recompiles all the dirty files, which at a stage
of a huge commit results in a long post commit for doing the compile.
I could be wrong with my guessing here, but I am rather certain I am not.
Received on Sat Jun 4 06:52:15 2005
This is an archived mail posted to the Subclipse Users