On 1/19/07, Eugene Kuleshov <email@example.com> wrote:
> I've noticed a weird issue with Synchronize view. I have about two
> sets of projects (about 20 projects each) checked out locally. The only
> difference is that one set is for trunk and another is from some branch.
> I have to do that because Subclipse don't allow to switch multiple
> projects to another branch in one action (see bugs 472 and 596) it is
> easier/faster to delete projects from Eclipse and import different set
> when you need to jump between trunk and branch.
> I also have a working set for those projects and created
> synchronization for the whole working set in the Synchronize view. It
> all work nice, except that synchronization goes completely crazy after I
> delete and import projects from different location in svn. So, I have to
> delete synchronization and create it again after every reimporting.
> Created new bug for this. See
Saw the issue.
As you know Synch view is not really my area of the code, but I would guess
when the project is deleted nothing is capturing that event and removing it
from the synch view, or something along those lines. When new project is
added, you get all these change events where the local info has new values,
but the Synch view is still operating off a cache of the remote
information. Perhaps it could know this scenario and essentially re-run the
I have to confess that just talking about this I cannot even think of what
the "right" thing to do would be. I am guessing you do not want the
projects removed from the Synch view, and is re-running the Synch process
the right thing to do either?
Bigger question might be whether we have any contributors around any more to
look at this? Martin is the one who got the view really working well in its
current state. I think Brock knows a good deal about it too.
Received on Fri Jan 19 19:36:47 2007