Bug 186320

Summary: [api][efs] RSE EFS provider should be split into core and UI plugins respectively
Product: [Tools] Target Management Reporter: Martin Oberhuber <mober.at+eclipse>
Component: RSEAssignee: Martin Oberhuber <mober.at+eclipse>
Status: RESOLVED FIXED QA Contact: Martin Oberhuber <mober.at+eclipse>
Severity: enhancement    
Priority: P3 Keywords: api
Version: 2.0Flags: mober.at+eclipse: pmc_approved+
Target Milestone: 2.0   
Hardware: All   
OS: All   
Whiteboard:

Description Martin Oberhuber CLA 2007-05-10 05:09:51 EDT
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.
Comment 1 Martin Oberhuber CLA 2007-05-25 13:37:20 EDT
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.
Comment 2 Martin Oberhuber CLA 2007-05-25 14:02:09 EDT
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
Comment 3 Martin Oberhuber CLA 2008-08-13 13:19:22 EDT
[target cleanup] 2.0 RC1 was the original target milestone for this bug