Bug 186523 - [api][breaking] subsystemConfigurations extension point should be in Core
Summary: [api][breaking] subsystemConfigurations extension point should be in Core
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 1.0.1   Edit
Hardware: All All
: P1 enhancement (vote)
Target Milestone: 2.0   Edit
Assignee: Martin Oberhuber CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks: 170923
  Show dependency tree
 
Reported: 2007-05-11 04:37 EDT by Martin Oberhuber CLA
Modified: 2008-08-13 13:18 EDT (History)
0 users

See Also:
mober.at+eclipse: pmc_approved+
uwe.st: review+
javier.montalvoorus: review+
ddykstal.eclipse: review+
kmunir: review+
dmcknigh: review+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-05-11 04:37:20 EDT 
The subsystemConfigurations extension point should be defined in org.eclipse.rse.core, and not the UI.

It is conceptually a non-UI extension point, and even though the actual SubsystemConfiguration implementations still require UI right now when they derive from the abstract base class, the corresponding interfaces are all non-UI already:
  ISubSystemConfiguration
  ISubSystemConfigurationProxy
  SubSystemConfigurationProxy

I consider it very important moving the extension point to Core for TM 2.0 because this will make the APIs non-UI and allow us to probably make more implementation non-UI without changing the APIs in the future.
Comment 1 Martin Oberhuber CLA 2007-05-11 21:40:33 EDT 
Work completed, checkin comment:
[186523][api] Move subsystemConfigurations extension point from UI to core

Migration notes:
In every subsystemConfigurations extension point, replace
   org.eclipse.rse.ui.subsystemConfigurations
by
   org.eclipse.rse.core.subsystemConfigurations
Comment 2 Martin Oberhuber CLA 2008-08-13 13:18:23 EDT 
[target cleanup] 2.0 M7 was the original target milestone for this bug