Community
Participate
Working Groups
Having the RSE EFS provider in a separate plugin is problematic in terms of plugin dependencies. There may be clients who want to use the EFS provider without some of the UI associated - see bug #182363 for instance. Given that RSE Core depends on the Platform anyways, and the EFS APIs are even below Resources, I think that the EFS Provider should not be a separate plugin any more but moved into org.eclipse.rse.subsystems.files.core org.eclipse.rse.files.ui In order to allow for applications to use RSE bug not the EFS provider, the EFS extension should honor Capabilities.
Done, commit comment: [186320][188360][api] Split and rename org.eclipse.rse.eclipse.filesystem into org.eclipse.rse.efs and org.eclipse.rse.efs.ui respectively Migration docs: --------------- Instead of the old plugin org.eclipse.rse.eclipse.filesystem there are now two new plugins: org.eclipse.rse.efs org.eclipse.rse.efs.ui Since no package was API the change should be trivial.
In order to pick up the new plugin into your RSE CVS Workspace, please 1.) Synchronize the www-tm-development project to HEAD 2.) Import the team project set of your choice 3.) Delete the old obsolete org.eclipse.rse.eclipse.filesystem project --> You should get two shiny new plugins: org.eclipse.rse.efs org.eclipse.rse.efs.ui
[target cleanup] 2.0 RC1 was the original target milestone for this bug