The Eclipse File System (EFS) is an abstract file system API. It is used in the Eclipse platform to abstract away implementation details about what file system is used to store data in the workspace. This page is a repository of information for plug-in developers who are writing their own EFS implementations.
Are you working on an EFS implementation that you would like the community to know about? If so, add it to the list below. If possible, include CVS connection and contact information. You may find others in the community who are working on an implementation for the same kind of file system and may be able to pool resources.
Local file system
Plug-in id: org.eclipse.core.filesystem CVS: dev.eclipse.org:/cvsroot/eclipse/org.eclipse.core.filesystem Bugs: Eclipse Platform Resources Contact: The platform-core-dev mailing list] Description: This EFS implementation is backed by the local fileystem through a combination of java.io API, and some optional native fragments. The implementation is product quality, and is available in Eclipse Platform 3.2 release or greater.
Plug-in id: org.eclipse.core.filesystem.ftp CVS: dev.eclipse.org:/cvsroot/eclipse/platform-core-home/plugins/org.eclipse.core.filesystem.ftp Bugs: Eclipse Platform Resources Contact: The platform-core-dev mailing list] Description: This is a partial EFS implementation backed by the File Transfer Protocol (FTP). This implementation is not currently functional. You will need to create a KeyRing class with your FTP connection information. This plugin depends on the "team extras" FTP plug-in, found in the same repository at the path /platform-vcm-home/plugins/target/org.eclipse.ftp.
UI Examples: Zip and Memory file systems
Plug-in id: org.eclipse.ui.examples.filesystem CVS: dev.eclipse.org:/cvsroot/org.eclipse/www/eclipse/platform-ui/plugins/org.eclipse.ui.examples.filesystem Bugs: Eclipse Platform Resources Contact: The platform-core-dev mailing list] Description: This plug-in contains two sample EFS implementations. The first is an EFS implementation that treats a single zip file as the backing file system. The second is an entirely in-memory file system that is useful in automated tests.