diff --git a/releng/org.eclipse.rse.build/template/buildNotes.php b/releng/org.eclipse.rse.build/template/buildNotes.php index 93af6059ab7..3bb13eae947 100755 --- a/releng/org.eclipse.rse.build/template/buildNotes.php +++ b/releng/org.eclipse.rse.build/template/buildNotes.php @@ -24,19 +24,52 @@
  • TM 2.0M6 requires Eclipse 3.3M6. Platform Runtime is the minimum - requirement for core RSE and Terminal. Remotecdt requires CDT, and Discovery requires EMF. + 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. Thusu EFS support is no separate download any more but comes with RSE.
    • +
  • 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]. + To bring remote resources into your workspace, there are several options:
      +
    1. 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]).
      2. +
    2. Create a new project, on the location page disable "workspace", choose "rse" as file + system and browse to a remote folder. Works only if a .project file does not yet exist + at the chosen remote location. One disadvantage of this approach is that when + quitting and re-starting workbench, the project will be shown closed. You need to switch + to the RSE perspective, then open the project on each re-start of Eclipse. This will + be fixed by bug [181460].
      3. +
    3. In RSE, browse to any remote folder and choose "right-click" > "Create Remote Project". + This will create an EFS based "plain" project with the name of the remote folder in + your workspace. It will have no specific nature assigned, and creation may fail (e.g + when a .project file is already there; or a project of the requested name already exists). + This 3rd approach of creating an EFS project exists for convenience for now, and may be removed + in the future.
      4. +
    • +
  • 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.
    • -
  • SystemRemoteResourceDialog.setPreSelection() now works correctly [174944]. -
  • Use - - +
  • At least 94 bugs were fixed: use + + this query to show the list of bugs fixed since the last milestone, TM 2.0M5 @@ -87,20 +120,22 @@ are the best places for you to get started. 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.

    -

    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 TM 2.0 in a not backward compatible way.
    -All such API changes are voted on -by committers on the +

    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.

    -

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

      -
    • 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.
      • -
    +for future releases. Early migration information can also be found right +in the bug reports. Look for those that are tagged [api][breaking].

@@ -113,12 +148,50 @@ for future releases.

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. -
- + Use this query for an up-to-date list of major or critical bugs.