Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 363240

Summary: Better handling of out of sync files
Product: [Eclipse Project] Platform Reporter: Miles Parker <milesparker>
Component: SearchAssignee: Platform-Search-Inbox <platform-search-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3 CC: daniel_megert, deepakazad
Version: 3.7   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Miles Parker CLA 2011-11-08 18:41:52 EST 
Currently, when the user does a search and a file is out of sync, the user gets an error: 

"Resource is out of sync with the file system: '/project/somefile.txt'.

This seems way overboard, at least for a typical workflow. When searching within a complex workspace, I often get this error, typically for resources I care nothing about. Of course, it is (currently, anyway!) impossible for the IDE to intuit what resources I might or might not be interested in, but it would really improve workflow and quality perception to handle this in a less obtrusive way. Some possibilities:

1. Can't we just synch the actual file? If we can find out that it is out of synch, what's wrong with simply fixing that?
2. Provide "don't show this again" message.
3. Log as warning, not error.
4. Don't show.
Comment 1 Deepak Azad CLA 2011-11-08 19:39:20 EST 
Please enable "Preferences > General > Workspace > Refresh on access". This was introduced in 3.7.
Comment 2 Miles Parker CLA 2011-11-08 19:41:27 EST 
Oh, neat. Now I think I remember seeing a mention of that in milestones, but had forgotten. Out of curiosity, why isn't this default?
Comment 3 Deepak Azad CLA 2011-11-08 20:07:22 EST 
(In reply to comment #2)
> Oh, neat. Now I think I remember seeing a mention of that in milestones, but
> had forgotten. Out of curiosity, why isn't this default?
That I don't know. But you can add your views to bug 340977.
Comment 4 Dani Megert CLA 2011-11-09 05:03:31 EST 
.

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