Build Notes for TM 3.0.2
Dec 5, 2008

New and Noteworthy
  • TM 3.0.2 requires Eclipse 3.3 or later for the SSH component. Other components may work with earlier Eclipse versions, but these have not been tested. Platform Runtime is the minimum requirement for core RSE and Terminal. Discovery needs EMF, and the RemoteCDT integration needs CDT.
    Building the RSE SSH service requires Eclipse 3.4 or later for the fix of bug 224799; the fix also requires 3.4 at runtime, but the code contains a backward compatibility fallback to also run on Eclipse 3.3 if that particular fix is not required.
  • Highlights of Bugs fixed since TM 3.0.1:
    • Performance of the RSE Save Job was drastically improved for certain situations involving property sets - before the fix, the context menu could be frozen for up to 30 seconds in user actions [254842]
    • Symbolic Link Handling for dstore was fixed, especially for remote search [250458] [251713] [251744]
    • The Editor received an important fix where saving would lead to an invalid save conflict dialog [250140]
    • Offline Mode is now better supported [query]
    • RSE Useractions received some important fixes [query]
  • At least 30 bugs were fixed in total: Use this query to show the list of bugs fixed since TM 3.0.1 [build notes].
  • Following plug-ins were changed compared to TM 3.0.1:
    • org.eclipse.dstore.core
    • org.eclipse.rse.core
    • org.eclipse.rse.files.ui
    • org.eclipse.rse.services.dstore
    • org.eclipse.rse.subsystems.files.dstore
    • org.eclipse.rse.ui
    • org.eclipse.rse.useractions
    • org.eclipse.tm.terminal.ssh
  • For details on checkins, see TM SearchCVS, 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 3.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

No API changes are allowed in the TM 3.0.x maintenance stream. Therefore, TM 3.0.x is fully upward and backward compatible with TM 3.0, and can be fully exchanged for TM 3.0 in any product based on it. Take care of API specification updates though, where the TM 3.0.x API Docs have been updated to add clarifications or missing information compared to 3.0.

For the upcoming TM 3.1 release, only backward compatible API changes are planned, especially in order to support improved componentization and UI/Non-UI splitting. In the interest of improving the code base, though, please take care of API marked as @deprecated in the Javadoc. Such API is prime candidate to be removed in the future. Also, observe the API Tooling tags such as @noextend and @noimplement.

API Specification Updates since TM 3.0
The following lists amendments to API specifications that are worth noticing. More information can be found in the associated bugzilla items.
  • TM 3.0.2 API Specification Updates
    • None.
  • TM 3.0.1 API Specification Updates
    • IFileService#createFolder() now specifies that parent folders may be created by the implementation. Note that this clarification required additional code in FileServiceSubSystem in order to make IRemoteFileSubSystem.createFolder() and IRemoteFileSubSystem.createFolders() behave as expected for both parent folders created or not.
      Service implementations that need to be compatible with both TM 3.0 and TM 3.0.1 should create parent folders in the file service. Subsystem clients that need to be compatible with both TM 3.0 and TM 3.0.1 should not expect that parent folders are created [234026].
Use this query to show the full list of API related updates since TM 3.0 .
Known Problems and Workarounds
The following critical or major bugs are currently known. We'll strive to fix these as soon as possible.
  • bug 247059 - maj - [dstore] RSE AIX:SSL Connections work with EXPIRED certificate
  • bug 245260 - maj - Different user's connections on a single ftp host are mapped to the same temp files cache
  • bug 244070 - maj - [dstore] DStoreHostShell#exit() does not terminate child processes
  • bug 238156 - maj - Export/Import Connection doesn't create default filters for the specified connection
  • bug 236443 - maj - [releng] Using P2 to install "remotecdt" only from update site creates an unusable installation
  • bug 226564 - maj - [efs] Deadlock while starting dirty workspace
  • bug 222380 - maj - [persistence][migration][team] Subsystem association is lost when creating connection with an installation that does not have subsystem impl
  • bug 218387 - maj - [efs] Eclipse hangs on startup of a Workspace with a large efs-shared file system on a slow connection
  • bug 208185 - maj - [terminal][serial] terminal can hang the UI when text is entered while the backend side is not reading characters
  • bug 198395 - maj - [dstore] Can connect to DStore with expired password
Use this query for an up-to-date list of major or critical bugs.

The TM 3.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.