Refresh resources action has been behaving strange for me for a long time:
usually on repository (working tree, index, objects) external changes,
especially in situation like branch reset, change (checkout).
Now, we've got new indexing API and resources update machinery (am I
right?) and it seems to work even worse for me...
When I refresh whole project after some external action (or after action
that occurred when Eclipse wasn't running), sometimes I have to refresh
each opened file in editor manually (message recommending pressing F5
appears instead of file content).
Also, resources are often marked as having changes (prefix ">"), while
they actually aren't changed.
What's ugly, pressing refresh few times often doesn't help.
Am I the only one that experience that behavior regularly? If so, I can try
to provide some concrete steps to let you try to reproduce that.
I don't know internals behind jgit/egit index, refresh implementation, but
IMHO it behaves unnaturally for an end-user (at least in my instance).
Original issue reported on code.google.com by Marek.Za...@gmail.com on 27 Aug 2008 at 7:35
Original issue reported on code.google.com by
Marek.Za...@gmail.com
on 27 Aug 2008 at 7:35