Description Nick Boldt 2010-03-09 09:35:47 EST

Scenario:

I have a workspace with over 500,000 files occupying nearly 3G of space. It is not practical to have "refresh workspace automatically" turned on; nor would it work worth a damn due to the time required to scan all those files and the continual disk access / CPU grinding required.

As such I am forever forced to manually refresh individual projects, folders, and files when Eclipse complains that the resource is not up to date w.r.t. the filesystem. This is particularly annoying when I'm running a build or have more than one workspace sharing a project (one to compile it w/ PDE UI, another to build it with PDE Build / Athena).

Should I forget to do so, I get errors to the tune of:

  org.eclipse.core.internal.resources.ResourceException: 
  Resource is out of sync with the file system

... and have to both refresh the workspace resources AND restart the build.

This is a serious pain in the ass and hit to productivity. What would be better? 

Proposed Solution:

How about an option under Preferences that says "if you see that a resource is not fresh, and you do not have a conflict between the dirty editor of that file and the actual filesystem copy, simply refresh the workspace file using the actual file, and not bother to notify me about it!"

Or, simpler:

  Automatically refresh non-conflicting workspace files if 
  changed outside workspace?
  [ ] Ask [x] Always [ ] Never