Build Notes for RSE @buildId@
@dateLong@

• The systemTypes extension point now allows specifying the "icon", "iconLive" and "enableOffline" properties either as a Property, or as an attribute. This change allows for better integration with PDE. It is backward compatible with the format used in RSE 1.0M4.
• RSE now provides an update site at http://download.eclipse.org/dsdp/tm/updates/. We encourage users to update frequently, since we expect RSE quality to improve more and more as we are approaching our 1.0 release.
• Persistent storage of connection and filter data has been streamlined to use fewer files and directories, resulting in simplification of team support and improved perfomance.
• Windows dstore daemon can now be started by simply double clicking on daemon.bat (Bug 142952)
• Numerous bugs have been fixed, and we consider RSE safe now for all kinds of data transfer, even if it's done in multiple background sessions (except FTP, which will be enhanced as soon as the Jakarta Commons Net library passes EMO legal review).
• Use this query to show the list of bugs fixed since the last milestone, RSE 1.0M4.
• Look here for the CVS changelog.

• Renamed the org.eclipse.rse.ui.subsystemConfiguration extension point to subsystemConfigurations in order to better match the standard naming scheme used by the Platform.
• Renamed the org.eclipse.rse.ui.newConnectionWizardDelegate extension point to newConnectionWizardDelegates in order to better match the standard naming scheme used by the Platform.
• Removed the org.eclipse.rse.ui.rseConfigDefaults extension point. Use Java Properties instead, as described in the runtime-options documentation.
• Removed the org.eclipse.rse.ui.passwordPersistence extension point. The same functionality is achieved by using the data known from the IConnectorService implementations of a systemType (supportsUserId(), supportsPassword()). As long as a subsystem supports user id and password, the password can also be persisted. Persistence is always done case sensitive; Persistence cannot be disabled for system types.
• Moved several RSE Model Objects and Interfaces from org.eclipse.rse.ui to core:
  • (UI) org.eclipse.rse.model --> org.eclipse.rse.core.model
  • (UI) org.eclipse.rse.filters --> org.eclipse.rse.core.filters
  • (UI) org.eclipse.rse.subsystems.servicesubsystem --> org.eclipse.rse.core.subsystems
  Client code can be adapted to the new locations easily by invoking "Organize Imports" except for the following additional changes that need to be made:
  • Event handling methods for ISystemResourceChangeEvent, ISystemPreferenceChangeEvent, ISystemModelChangeEvent, ISystemRemoteChangeEvent have been removed from ISystemRegistry, such that they are available only in the SystemRegistry implementation. This applies to the fireEvent(), postEvent() and corresponding add...Listener() methods. The simplest fix in user code is to get the SystemRegistry from RSEUIPlugin instead of SystemRegistry as described below.
  • Use RSEUIPlugin.getTheSystemRegistry() instead of SystemRegistry.getSystemRegistry()
  Note that wherever possible, client code should only refer to the model object interfaces in org.eclipse.rse.core.* and not use the actual implementations which still reside in the UI plugin (these will be moved to core eventually, too).

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

As per the Target Management plan, we reached API Freeze for RSE M4.

In fact we have reviewed and documented all relevant APIs, but just like most Eclipse projects, we'll still reserve the right to make API improvements when committers vote on them. Votes will be held publicly, such that everyone will be informed in case the APIs should change.

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

• Classes and Interfaces that are not meant for public use will be moved to packages tagged as internal. This will apply particularly to the "implementation" plugins for the ssh, ftp and local subsystems (these do not define any new APIs anyways).
• 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.

• User Actions, and Import/Export were deferred with M3 already. A new plan has been published with M3 already.
• JUnit tests did not make it into the build due to pending IP legal review. They are available from Bugzilla bug 149080 instead. Due to the missing Unit Test Framework, automated tests could also not yet be added to this build.
• The CDT Launch Integration Example is not yet available as a download. It is available from the RSE CVS Repository instead.
• Jakarta Commons Net is not yet available for FTP and Telnet due to pending legal review. We are confident to get these completed in August though.
  • As a consequence, FTP connections are still not quite reliable.

• bug 143462 - maj - [updating] Dirty remote editors do not get notified