Build Notes for TM @buildId@
@dateLong@

New and Noteworthy
  • TM 2.0M5 requires Eclipse 3.3M5. Platform Runtime is the minimum requirement for dstore and ftp. Terminal-ssh and RSE-ssh also require the CVS Client Runtime (The dependency on CVS Client Runtime should go away again with M6 by resolving bug 175686).
  • Added a milestone update site for TM 2.0 milestone builds at http://download.eclipse.org/dsdp/tm/updates/milestones. "Check for updates" will automatically reference this milestone update site, so you can get milestone patches from there [175241].
  • Qualifiers of feature names are currently missing the last digit due to Platform bug 176010.
  • Apache Commons.Net and ORO are now distributed as single-jar bundles. The separate commons.net and ORO features have been removed. The bundles are now directly included in the RSE FTP feature only.
  • SystemRemoteResourceDialog.setPreSelection() now works correctly [174944].
  • Use this query to show the list of bugs fixed since the last milestone, TM 2.0M5 [build notes].
  • For details on checkins, see the RSE CVS changelog, and the TM Core CVS changelog.
  • For other questions, please check the TM and RSE FAQ as well as the TM 2.0 Known Issues and Workarounds.
Getting Started

The RSE User Documentation now has a Tutorial that guides you through installation, first steps, connection setup and important tasks.

If you want to know more about future directions of the Target Management Project, developer documents, architecture or how to get involved,
the online Getting Started page as well as the TM and RSE FAQ are the best places for you to get started.

API Status

An important part of the Target Management 2.0 Project Plan is to harden the APIs which were provisional by RSE 1.0. Naturally, this requires API changes, and especially moving lots of classes which we cannot guarantee to support in the future into internal packages.

We are committed to not introducing any incompatible API changes on the RSE 1.0 maintenance stream (1.0.x), but we need to change the API for TM 2.0 in a not backward compatible way.
All such API changes are voted on by committers on the dsdp-tm-dev developer mailing list, and documented in a migration guide for future releases.

Currently, we see the following areas for more potential API changes:

  • The IConnectorService interface may be slightly modified in order to allow for better UI / Non-UI separation.
  • Some more RSE Model classes may be moved from the UI plugin to the non-UI core plugin.
API Changes since RSE 1.0.1 - newest changest first
The following lists those API changes that are not backward compatible and require user attention. A short hint on what needs to change is given directly in the list. More information can be found in the associated bugzilla items.
  • TM 2.0M6 API Changes
    • Cleaned up ISystemRegistry - removed or changed signature of several methods [175680].
    • Renamed getAdapter(Object) -> getViewAdapter(Object) on several classes [175150].
    • Refactored IConnectorService and moved to Core [168977].
    • [Just additions?] Support Menu Configuration in RSESystemTypeAdapter [161195].
  • TM 2.0M5 API Changes
    • Modified Extension Point subsystemConfigurations to reference system types by ID rather than by name. Client code needs to use the systemTypeIds tag now rather than systemTypes [162081].
    • Removed Extension Points for Popup Menus and Property Pages: The RSE-specific extension points org.eclipse.rse.ui.propertyPages and org.eclipse.rse.ui.popupMenus were removed because newer Eclipse versions have all required functionality in the base extension points already. Example code, tutorials and ISV docs were updated and have the required information for how to migrate to the new extension points. [172651].
    • Moved extension point org.eclipse.rse.ui.archiveHandlers to org.eclipse.rse.services.archiveHandlers [173871].
    • newConnectionWizards: The old newConnectionWizardDelegates extension point has been replaced by a new newConnectionWizards extension point for more flexibility [173772].
    • Deep Filtering: The SystemView now supports Context Information for queries of multiple filters to the same remote elements. That is, the SystemViewElementAdapter.getChildren() method can know the filer context in which a query is made. This is necessary in order to properly support "deep filtering" by file types. An API change was required to get this implemented: Existing code needs to change two method signatures in classes deriving from AbstractSystemViewAdapter. For details, see [170627].
    • Making classes internal: Many classes have been made internal, and PDE support for generating warnings of discourage access has been enabled. Client code should not have used the classes which are now internal anyways; but if you do, just running "organize imports" should make your code compile again. For details, see [170922].
Use this query to show the full list of API changes since RSE 1.0.1.
Known Problems and Workarounds

No major or critical bugs are known at the time of release. Use this query for an up-to-date list of major or critical bugs.

The TM 2.0 Known Issues and Workarounds Wiki page gives an up-to-date list of the most frequent and obvious problems, and describes workarounds for them.
If you have other questions regarding TM or RSE, please check the TM and RSE FAQ

Click here for a complete up-to-date bugzilla status report, or here for a report on bugs fixed so far.