- Target Management source code release, available as versions tagged "R3_2" in the project's
- Remote System Explorer (RSE):
- RSE SDK (includes runtime, user and programmer documentation, with sources) (downloadable).
- RSE client runtime binaries (split up by protocol, includes user documentation) (downloadable).
- RSE dstore server runtime (downloadable).
- RSE User Actions and Compile Commands (downloadable).
- RSE tutorial code and examples (downloadable).
- RSE unit test framework and tests (downloadable).
- Stand-alone components:
- TM Terminal SDK (includes runtime, user and programmer documentation, with sources) (downloadable).
- NEW: Redistribution of Apache Commons Net 2.2 (downloadable through the Orbit project).
- Incubating components:
- RSE WinCE Subsystems and RAPI wrappers (runtime and sources) (downloadable).
- TM Local Terminal Connector (runtime and sources) (downloadable).
Notes: All stand-alone components will have an integration part that makes them work inside the RSE framework. For that reason, there are no downloadable stand-alone component tests, but the RSE unit test component will also have tests for the stand-alone components.
Target Management 3.3 will be backward compatible with TM 3.2.
API Contract Compatibility: Target Management 3.3 will be compatible with TM 3.2 as per the constraints documented in the TM 3.2 API Docs.
Binary (plug-in) Compatibility: Target Management 3.3 will be binary compatible with TM 3.2.
Source Compatibility: Target Management 3.3 will likely not be source compatible with TM 3.2.
Workspace Compatibility: We intend to keep Target Management 3.3 upwards workspace-compatible with TM 3.2 unless noted. This means that workspaces and projects created with TM 3.2 can be successfully opened by Target Management 3.3 and upgraded to a 3.3 workspace. This includes especially TM 3.2 connection definitions, which may propagate between workspaces via file copying or team repositories. User interface session state may be discarded when a workspace is upgraded. Downward workspace compatibility is not supported. A workspace created (or opened) by a product based on TM 3.3 may be unusable with a product based on TM 3.2.
API Contract
APIs published for the Target Management 3.3 release will be carefully reviewed prior to release, making use of "internal" packages for unsupported and variable implementation classes. Client plug-ins that directly depend on anything other than what is specified in the published API are inherently unsupportable and receive no guarantees about future compatibility. Refer to How to Use the Eclipse API for information about how to write compliant plug-ins.
The Remote System Explorer is designed as the basis for internationalized products. The user interface elements provided by the RSE components, including dialogs and error messages, are externalized. The English strings are provided as the default resource bundles. The default bundles will be localized to a subset of those locales offered by the Platform. This plan will be updated to indicate which locales will be provided and the timeframe for availability.
In order to remain current, each Eclipse release is designed to run on reasonably current versions of the underlying operating environments.
The Target Management Project 3.3 depends upon on the Eclipse Platform 3.7. For this release, the RSE sources will mostly be written and compiled against version 1.4.2 of the Java Platform APIs (i.e., Java 2 Platform, Release 1.4.2 SE), and designed to run on version 1.4.2 of the Java Runtime Environment, Standard Edition except for the following components, which are compiled on and running against Java 5: FTP, Telnet and Import/Export.
The Target Management deliverables will be tested and validated against a subset of the reference platforms listed in the Eclipse Platform 3.7 Project Plan (this list is updated over the course of the release cycle).
Target Management Reference PlatformsOperating systemOS versionProcessor architectureWindow systemJava 2 PlatformMicrosoft WindowsXPx86-32Win32Sun Java 5 Update 22Microsoft WindowsXPx86-32Win32IBM Java 5 SR11Red Hat Enterprise LinuxWS 4 update 2x86-32GTKSun Java 5 Update 22
for Linux x86SUSE Linux Enterprise Server11x86-32GTKIBM Java 5 SR11Sun Solaris10SPARCGTKSun Java 5 Update 22
for Solaris SPARCApple Mac OS X (Secondary, see below)10.5UniversalCarbonApple Java 10.5 Update 2
Apple Mac OS X 10.5 is considered a "secondary" Reference Platform meaning that it does receive some amount of systematic testing but doesn't enjoy quite the same priority for bug fixes as the other Platforms.
Eclipse and Target Management undoubtedly run fine in many operating environments beyond the reference platforms we test. However, since we do not systematically test them we cannot vouch for them. Problems encountered when running Target Management on a non-reference platform that cannot be recreated on any reference platform will be given lower priority than problems with running Target Management on a reference platform.
Although untested, Target Management should work fine on other OSes that support the same window system. For more details, see the Eclipse Project Plan 3.7 Reference Platforms.
Datastore Agent Reference Platforms
The Datastore protocol is the default protocol shipped with RSE for accessing remote file systems, process info and shells. It requires a Datastore server (agent) running on the remote system. This Datastore agent is shipped as plain Java Source Code together with the RSE distribution. It should run fine on any Java Platform, with additional Data Miner Plug-ins that may be OS specific.
We will test and verify the Datastore agent on the following Reference Platforms, which are a subset of the Platforms we test the RSE UI on:
- Red Hat Enterprise Linx 4, Intel x86, Sun 1.5.0_14 VM
- SUSE Linux Enterprise Server 10, Intel x86, IBM 1.4.2 sr 7 VM
- Apple Mac OS X 10.5, Power, Apple J2SE 5 sr 4 VM
Improve Release Engineering
For the constantly growing TM code size and committer base, it is important to have a reliable but easy-to-use release engineering system. Required features include automatic signing and adoption of Orbit, easy promoting to the Eclipse Servers and Indigo, running automated unit tests with automatic reporting of test failures to the mailing lists, ability and description for running the releng build on any adopter's system. In bugzilla, these items are tagged with "[releng]" in the Summary (query: all [releng] open).
- Remove.
archive the discovery component [330337] (target milestone: 3.3 M4) - API Tooling reports incomplete build path on o.
e. rse. subsystem. shells. local [332506] (target milestone: 3.3 M5) - Legacy Builder should use Mapfiles from org.
eclipse. tm. releng [332513] (target milestone: 3.3 M4) - SCP fails to build on Eclipse 3.
7m5 [335912] (target milestone: 3.3 M5) - Retire or migrate the dsdp.
eclipse. org vserver [338635] (target milestone: 3.3 M7) - Update the SUA in the features to the latest version [339954]
(target milestone: 3.3 M6) - Move TM to tools [330336]
(target milestone: 3.3 M6)
Improve Unittest Coverage
As the TM Codebase is growing, it is important to secure its functionality with unit tests against regressions. Since large portions of RSE especially are UI code, there should be an automated UI test suite run every night. Tests should automatically run on all supported host platforms against all supported target platforms. Adopters should be able to run a TM test suite on their own systems easily, and configure it for sanity checking or compliance testing their own connector plug-ins. In bugzilla, these items are tagged with "[testing]" in the Summary (query: all [testing] open).
Other
Bug fixes for improved robustness, stability and usability are part of ongoing maintenance. Besides that, here are some larger features and bugs that we plan to address in the next release cycle until 3.3 M7, but are not categorized into one of the themes above.
In order not to overload the project plan with less important items, only those marked with a "plan" keyword will be added to the project plan. The pool of known items to add to the plan can be found from the associated queries (query: all open committed, proposed, deferred ).