Community
Participate
Working Groups
EFS currently has no API for file system implementations to communicate back changes that have occurred in the underlying file system. Win32 provides API like this, and inotify provides similar support on Linux. A common callback API in EFS could hook into these native capabilities where possible, and implement a polling based default implementation for other file systems.
There has been a little bit of discussion on listeners for EFS already, on bug 106176 comment 21. That discussion includes references to Apache Commons VFS which does have listener support. See also bug 106176 comment 27 which references a Java API for inotify, called http://l3x.net/imwiki/Wiki.jsp?page=JFileWatch Bug 108697 explicitly requests inotify support in Eclipse, see also bug 106176 comment 28. IResourceChangeListener seems related to this on a higher (resource) level: http://help.eclipse.org/help33/topic/org.eclipse.platform.doc.isv/guide/resAdv_events.htm inotify was also mentioned in the context of discussing symbolic link support for EFS, see bug 44107 comment 13 and the replies to it. Eclipse MonitorManager class was mentioned in this thread as the class that's currently caring for automatic Workspace Referesh (by polling right now, but hopefully using some notification mechanism in the future).
Actually, refreshProviders is the extension point that currently supports registering file system notification monitors related to MonitorManager: http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/resAdv_refresh.htm
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
