Bug 416199 - EGit auto-refresh should refresh related resource only
Summary: EGit auto-refresh should refresh related resource only
Status: CLOSED DUPLICATE of bug 551289
Alias: None
Product: EGit
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-29 22:21 EDT by Dennis CLA
Modified: 2019-12-04 11:45 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis CLA 2013-08-29 22:21:39 EDT
1. Enable "Refresh resource when index changes" in Preferences

2. git checkout (reset, stash, commit or anything) in ssh terminal

3. Eclipse do a slow refresh on your projects.


The "Refresh resource when index changes" feature, will trigger a "full project refresh" when it find the git index changes. However, it should be smarter and able to find the related files from git index and refresh them and only.

By refresh only the related file, the performance and response time of egit should boost.
Comment 1 Robin Stocker CLA 2013-11-19 13:25:55 EST
With which version of EGit are you having this problem?
Comment 2 Lorenzo Dalla Vecchia CLA 2019-12-04 05:04:19 EST
What is the exact purpose of the "Refresh resource when index changes" preference?

Regardless of it being checked, I see a full workspace refresh after every Git operation. I am using EGit 5.4.
Comment 3 Thomas Wolf CLA 2019-12-04 11:45:49 EST
This should be fixed in EGit 5.6.0.

(In reply to Lorenzo Dalla Vecchia from comment #2)
> What is the exact purpose of the "Refresh resource when index changes"
> preference?

It should refresh the Eclipe resource tree when JGit changes files on checkout. JGit doesn't know about the Eclipse resource APIs and uses java.io.File directly, and thus Eclipse might not pick up changes (files added/deleted).

*** This bug has been marked as a duplicate of bug 551289 ***