Bug 196938 - [api][breaking] Get rid of obsolete SystemSelectConnection*
Summary: [api][breaking] Get rid of obsolete SystemSelectConnection*
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.0 M3   Edit
Assignee: David McKnight CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2007-07-18 07:23 EDT by Martin Oberhuber CLA
Modified: 2007-11-05 12:01 EST (History)
1 user (show)

See Also:
mober.at+eclipse: review+


Attachments
patch for removing obsolete classes (80.16 KB, patch)
2007-11-05 10:19 EST, David McKnight CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-07-18 07:23:09 EDT
Following classes are nowhere used and seem to be obsolete:
  SystemViewConnectionSelectionInputProvider
  SystemSelectConnectionAction
  SystemSelectConnectionDialog  (*)
  SystemSelectConnectionForm  (*)

  SystemUpdateConnectionDialog
  SystemUpdateConnectionAction

  SystemRemoteArchiveSelectAction
  SystemRemoteFileSelectAction
  SystemRemoteFolderSelectAction

  SystemRemoteConnectionCombo (*)
  SystemWidgetHelpers.createSystemTypeListBox (*)

(*) SystemSelectConnectionDialog and SystemRemoteConnectionCombo are in an API package so removing those is an API change and might require proposing an alternative. The others are in internal packages so removing them should not be an issue.
Comment 1 Martin Oberhuber CLA 2007-07-18 07:23:34 EDT
Assigning 2.0.1 for now since I'd like the non-api-changing removals to be done for 2.0.1
Comment 2 Martin Oberhuber CLA 2007-07-18 07:26:57 EDT
Note: Occurrences of the obsolete classes have been found by searching who's calling SystemWidgetHelpers.getValidSystemTypes() -- this check should be re-done once obsolete classes are removed.
Comment 3 Martin Oberhuber CLA 2007-10-01 07:57:24 EDT
Bulk update target milestone 2.0.1 -> 3.0
Comment 4 David McKnight CLA 2007-11-05 10:19:24 EST
Created attachment 82097 [details]
patch for removing obsolete classes
Comment 5 David McKnight CLA 2007-11-05 10:21:19 EST
I've added a patch for removing the obsolete classes.  For those that are in API packages, do you think we need to do anything?  Is so, how do we go about proposing alternatives? 
Comment 6 Martin Oberhuber CLA 2007-11-05 11:02:03 EST
Since you remove the API classes as well, I'm marking this bug as [api][breaking] in the subject.

I guess that in the final 3.0 release, we should have a "migration" section in the ISV docs, similar to http://help.eclipse.org/help33/nav/2_3

While it's not clear if and how we compile that migration section, I'd propose just adding your migration notes as a comment on this bug, in the form of "If you've been using SystemRemoteConnectionCombo, migrate to using XYZ instead".

When compiling the migration docs, all bugs which are marked as [api][breaking] should be considered for inclusion.
Comment 7 David McKnight CLA 2007-11-05 11:25:10 EST
In place of SystemSelectConnectionForm, users may use SystemHostCombo to choose an available connection.

In place of the SystemRemoteFileSelectAction and the SystemRemoteFolderSelectAction, users should use the SystemSelectRemoteFolderAction.  As an alternative, users can use SystemRemoteArchiveDialog, SystemRemoteFileDialog and SystemRemoteFolderDialog directly.

In place of the SystemRemoteConnectionCombo, users should use the SystemHostCombo directly or via SystemWidgetHelpers.createConnectionCombo().

In place of SystemWidgetHelpers.createSystemTypeListBox(), users can use SystemWidgetHelpers.createListBox() directly with the appropriate arguments.


Martin, do you think this description is sufficient?  I've committed the changes to cvs.
Comment 8 Martin Oberhuber CLA 2007-11-05 11:56:46 EST
Looks good to me.
Comment 9 David McKnight CLA 2007-11-05 12:01:26 EST
Okay, I'm marking this as fixed now.