I have observed this bevaviour, too but found no way to reproduce it.
The Synchronize view can be regarded as broken, it works very
unreliable. The regular view works most of the time.
From: Geertgens, Scott [mailto:firstname.lastname@example.org]
Sent: Montag, 6. Juni 2005 23:24
Subject: Refresh issues
I'm curious if there are any known 'refresh' issues after various SVN
operations via subclipse (eclipse 3.1M7 + subclipse 0.9.31/SVN1.2.0). A
number of developers that I have using subclipse complain that both the
SVN Sync perspective and the standard Java perspective refuse to update
correctly after a commit - the commit itself works fine, but the GUI
still indicates an outgoing change. This is further reflected in the SVN
Resource History (you will see the new revision in the log, but it
indicates that you are still on the previous revision!). A full exit and
restart of eclipse will fix things. Of course, I'm unable to duplicate
the event on my system to provide a series of reproducable steps even
though I run in the same configuration, so I wanted to ask this on the
users list prior to submitting an actual issue. Thanks!
Scott J. Geertgens
Received on Tue Jun 7 17:39:08 2005