Thanks to a recent patch from Martin Letenay I have committed some nice
improvements to the Synch process. See this thread for details:
Martin's fixes improve most of the refresh problems that have plagued the
Synch process. In general, it now does a better job refreshing itself
after commits/updates as well as when new stuff is added in the
That being said, it looks like there are still a few problems here and
there. However, it seems like those problems are less nagging and sort of
clean themselves up over time.
Here are some examples:
1) When just a new folder comes in from the repository it causes some
short term weirdness.
2) When deletes come in or go out, I see lots of errors go into the error
log. However, they do not have stack traces. I think this is due to
Martin solving a lot of the problems by using phantom resources. I think
we need to just track down the areas that are producing the messages and
clean up the code. It is all in UI, so it is probably happening in the
decorator code. I already fixed one exception where we tried to check if
the resource as dirty.
I would like to roll a new release in the next week or so, but I would
feel better if some other devs just banged on this a bit and possibly
committed a fix here and there. I think the problems that are left are
much more solvable than before.
PS - Our next Major Problem is this one where the case of the workspace
path in Eclipse does not match the file system. I imagine this would only
be a problem on Windows and OS X, since on Unix, Eclipse couldn't work
with an invalid case path. It would be great if someone could track this
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Tue Jun 14 23:30:33 2005