diff --git a/releng/org.eclipse.rse.build/template/buildNotes.php b/releng/org.eclipse.rse.build/template/buildNotes.php
index 3a766842eb4..e31d361ff70 100755
--- a/releng/org.eclipse.rse.build/template/buildNotes.php
+++ b/releng/org.eclipse.rse.build/template/buildNotes.php
@@ -3,14 +3,14 @@
-Build Notes for RSE @buildId@
+Build Notes for TM @buildId@
-
Build Notes for RSE @buildId@
+
Build Notes for TM @buildId@
@dateLong@
@@ -23,11 +23,17 @@
-
Added a milestone update site for RSE 2.0 milestone builds at
+
Taking into account that TM is actually more than the core RSE framework,
+ and especially includes components like the Terminal that do not require RSE,
+ we changed all references to read TM 2.0 instead of RSE 2.0.
+
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.
- As per [175241], the RSE Core feature references
- this update site os when you install an RSE 2.0 milestone, you can "check for updates" to get the next
- one or add components from the site.
+ "Check for updates" will automatically reference this milestone update site, so you can get milestone
+ patches from there [175241].
Terminal: Use rxtx-2.1 (gnu.io) for serial line support instead of javax.comm. See the new
README for installing RXTX
[168893]
@@ -49,7 +55,7 @@
Using this new functionality, it is also possible to hook up new system types with existing
subsystemConfigurations [173265].
@@ -103,7 +109,7 @@ 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 RSE 2.0 in a not backward compatible way.
+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
@@ -130,27 +136,27 @@ More information can be found in the associated bugzilla items.
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].
+[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]
+to the new extension points. [172651].
newConnectionWizards: The old newConnectionWizardDelegates extension point
- has been replaced by a new newConnectionWizards extension point for more flexibility.
- See the bugzilla item for details [173772].
+ 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. See [170627] for details.
+ 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.
- See [170922] for details.
+ For details, see [170922].
Use
@@ -175,14 +181,14 @@ We'll strive to fix these as soon as possible.
-->
No major or critical bugs are known at the time of release.
Use
-this query
+this query
for an up-to-date list of major or critical bugs.
The
-
-RSE 2.0 Known Issues and Workarounds Wiki page gives an up-to-date list
+
+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 RSE, please check the
+If you have other questions regarding TM or RSE, please check the
TM and RSE FAQ
- Prerequisites for add-ons (like CDT, EMF) should be retrieved from the
+ We recommend installing
+ eclipse-SDK.
+ If you do not want JDT, PDE and the developer docs, please install
+ eclipse-platform together with
+ eclipse-CVS-Client.
+
+
+ Prerequisites for other add-ons (like CDT, EMF) should be retrieved from the
Europa Discovery Site.
- Earlier versions (e.g. Eclipse 3.2.x) will not work!
+ Earlier versions (e.g. Eclipse 3.2.x, Eclipse 3.3M4) will not work!
An experimental Eclipse Filesystem (EFS) provider, which
- uses RSE contributed file services. It currently works for accessing
- remote file systems, but cannot be used to hold Projects of an
- Eclipse Workspace due to resource locking issues. Includes Source.
+ uses RSE contributed file services. It currently works for ssh
+ connections with limitations. See
+ bug 170916 for details. Includes Source.
