Re: [Subclipse-users] Oddness with eclipse 3.3

On 7/27/07, Nigel Magnay <nigel.magnay@gmail.com> wrote:
> I haven't tried refreshing the file directly - any solution around having to
> refresh individual files obviously isn't going to help me next time around
> (as I'd only noticed by chance), but I'll try before generating my bug
> report just to see.
>
> One other thing I've noticed is that in the package explorer, the file is
> listed at revision 3430, but in the properties dialog (subversion section),
> it lists the revision as 3431... could this have anything to do with the
> problem?

It is just more of the same symptoms. The decorators get refreshed
when Eclipse asks for new values. It does that when it thinks
something has changed.

When you run Refresh, Eclipse only refreshes stuff that it thinks has
changed. So somehow, Eclipse thinks it has the latest of this file.
That is why I suggest you force a refresh by editing the file.

In terms of reporting the bug, the problem is that the bug is not in
the Refresh, it is in whatever the root cause that triggered this was.
 That will be hard to determine.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org