Build Notes for TM @buildId@
@dateLong@

New and Noteworthy
  • TM 2.0M6 was respun as TM 2.0M6a in order to include the following critical fixes for EFS.
    If you do not want to use the Eclipse Filesystem (EFS) for accessing remote resources through your workspace, there is no need to update and you can also use 2.0M6:
    • [181917] Fix EFS running out of file descriptors, fix EFS early startup problems, improve EFS performance
    • [176603][api] ISubSystem.connect(IProgressMonitor, boolean forcePrompt) required for EFS
    • [sync] Add proper group markers to the toolbar groups. Re-used the context menu group markers for easier orientation
    Only the following 3 plug-ins from the rse-runtime-core feature were changed:
    • org.eclipse.rse.ui
    • org.eclipse.rse.core
    • org.eclipse.rse.eclipse.filesystem
  • TM 2.0M6 requires Eclipse 3.3M6. Platform Runtime is the minimum requirement for core RSE and Terminal. The Team CVS feature is no longer needed for SSH [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].
  • The experimental EFS Feature has been made official, and functionality moved into RSE Core. Thus EFS support is no separate download any more but comes with RSE. EFS works best with SSH connections. FTP and dstore should work as well, but have not yet received the same amount of testing. For more details, see the EFS Plan Item [170916]. We recommend the following procedure to bring remote resources into your workspace:
    • In a normal workspace project, choose "New Folder", "Advanced", "Link to folder in file system", then select the RSE file system and browse to a remote folder. This is the preferred and most stable method of working with remote resources for now. One big advantage of this approach is that it works for any kind of project nature, including CDT, JDT etc. and can thus be used very well to test other kinds of EFS integration issues to be done (along the lines of Eclipse Platform Plan Item [154126]).
    Creating whole projects based on RSE EFS is possible as well, but there are two Platform Bugs related to early reading of the remote .project file, which make this approach not adviseable for now.
  • Copy&Paste, Drag&Drop to Project Explorer are finally fixed [153652]. Same support for Windows Explorer is still on the list [181458].
  • Lots of Improved API and Flexibility especially for system types, action contributions, dynamic system types and the New Connection Wizard. See below for details on breaking API changes. As part of the improved New Connection Wizard, the Default System Type Preference has been removed [164413].
  • 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.
  • At least 94 bugs were fixed: 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.

As of TM 2.0 M6, most of this work has been completed, and the list of breaking API changes is found below with migration info. But although we had planned for API freeze with M6, there are still few more cleanup changes that we would like to take the opportunity and bring into TM 2.0. Most of these will be made shortly after M6, or they will be introduced in a backward compatible manner. At any rate, we will avoid breaking API changes after M7, or the earlierst possible integration build up to M7. But please be prepared for future changes, and especially take care of API marked as @deprecated in the Javadoc. Such API is prime candidate to be removed for TM 2.0.

Use this query to show the list of API changes planned or done after M6. All such API changes are voted by committers on the dsdp-tm-dev developer mailing list, and documented in a migration guide for future releases. Early migration information can also be found right in the bug reports. Look for those that are tagged [api][breaking].

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 Breaking API Changes
    • Making more classes "internal": Lots of more packages and classes were tagged as discouraged access (moved to "internal"). For migration, just "Organize Imports" and search for alternative ways of doing things in case you end up with imports from "internal" packages. For details, see [170922].
    • Refactored IConnectorService and moved to Core for beter UI / Non-UI separation. Most notably, the concept of a CredentialsProvider was added. That work is not quite complete yet, but the bulk of the work has been done. For detailed migration info, see [168977].
    • Renamed getAdapter(Object) -> getViewAdapter(Object) on several classes. For migration, same renaming may need to be done in client code. [175150].
    • Dont implement constant interfaces just to bring constants into namespace. As an effect of this, some classes that clients can derive from do not "see" some constants any more. For migration, these constants will need to be qualified with the interface that they come from. For details, see [180562].
    • Streams are now part of IFileService and IRemoteFileSubSystem. Supporting Streams was important for the EFS integration and is a more modern and flexible way to download and upload. Thus Streams are now mandatory, and extenders must ensure that they implement getInputStream() and getOutputStrem() properly in their own file services and subsystems. [162954] and [179850].
    • IHost.getSystemType() now returns an IRSESystemType instead of a String. More similar changes will follow, in order to move from system type Strings to IDs and translatable / externalizable labels. For migration, client code can replace getSystemType() by getSystemType().getName(). [175262].
    • Support Menu Configuration in RSESystemTypeAdapter [161195].
    • The RSE Communications Daemon has been removed since it was never quite properly supported in Open Source [180602].
    • The org.eclipse.rse.logging plugin has been removed, functionality is now in the core and UI plugins, respectively [170920].
  • TM 2.0M5 Breaking 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
The following critical or major bugs are currently known. We'll strive to fix these as soon as possible.
  • bug 180994 - maj - Expand of filter hangs with dstore
  • bug 179939 - maj - BIDI locale: Remote text files written in Hebrow look incorrect
  • bug 179937 - maj - BIDI locale: Path and file names shown incorrectly with hebrew UTF 8 encoding
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.