diff --git a/releng/org.eclipse.rse.build/template/buildNotes.php b/releng/org.eclipse.rse.build/template/buildNotes.php index 0dfb55ee3a5..8b3ea31627d 100755 --- a/releng/org.eclipse.rse.build/template/buildNotes.php +++ b/releng/org.eclipse.rse.build/template/buildNotes.php @@ -23,21 +23,33 @@
    -
  • RSE ssh feature now supports connections via Proxy. -
      -
    • Re-uses ssh Preferences from Team > CVS > SSH2 Connection Method, and Team > CVS > Proxy Settings.
    • -
    • Ssh private key authentication is supported, but RSE requires entering a dummy password - (bug 142471). - As an alternative, passwords can also be maintained by RSE.
    • -
    -
  • -
  • Documentation is now available. Note that this documentation partially still - refers to the older IBM RSE product and thus contains lots of outdated - references.
  • -
  • The New Connection Wizard is now completely replaceable for contributed - system types. As a side effect of this, the ordering of subsystems for a - connection may change (bug 149280). -
  • Use +
  • APIs and String Constants have been cleaned up from old artifacts. + RSE Documentation has been adjusted to latest refactorings. You'll get the + documentation as part of the installation, or you can browse it online at + http://dsdp.eclipse.org/help/latest/. + Note that the online version is updated every night to hold the latest updates.
  • +
  • The ssh command shell now supports RSE pattern matching in the output. + Output parsers are installed for make, ls, pwd, cd, ps and many popular compilers. + If you run such a command, it's output will be parsed by the RSE shell + and annotations will be added. Double clicking these partially works (Bugs + 153270, + 153272).
  • +
  • The ssh command shell also supports content assist for directory names + and file names in the input box. To use it, press Ctrl+Space. After selecting + a completion, the command will be sent immediately (Bug + 153271).
  • +
  • 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.
  • +
  • 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).
  • +
  • See also the + + last milestone's New and Noteworthy.
  • +
  • Use this query to show the list of bugs fixed for this build.
  • Look here for the CVS changelog.
  • @@ -51,7 +63,12 @@
-

Download RSE SDK, and either +

The simplest way to get RSE is via the Update Manager: From your running instance +of Eclipse 3.2, choose Help > Software Updates > Find and Install.... +Choose "Search for New Features to Install", and add a new Remote Site named +"RSE" and pointing to http://download.eclipse.org/dsdp/tm/updates/. +Select the RSE SDK feature, and perform the update process as usual.

+

If you prefer manual installation, you can download RSE SDK and either

  • Extract it into your installation of Eclipse 3.2, or
  • Extract it into an empty directory and link it as product extension via Help > Install/Update, or
  • (If you want to write code for RSE) extract it into an empty directory, and from an Eclipse PDE Workspace @@ -65,7 +82,10 @@ local host, which is shown by default:
    • Browse the Filesystem, choose contextmenu > show in Table, and observe the Properties view
    • Create a new Filter to show specific resources in the file system only -
    • Launch an RSE Shell (Shells node > Launch)
    • +
    • Launch an RSE Shell (Shells node > Launch) +
      • In the Shell, perform commands such as ls, dir, ps, gcc, make and see the output interpreted
      • +
      • Use Ctrl+Space Content Assist on the shell command entry field
      • +
    For operations on an actual remote system, you can either
      @@ -84,7 +104,7 @@ For operations on an actual remote system, you can either

      RSE is a framework that supports plugging in many different communication protocols. By default, the dstore, FTP and ssh protocol plug-ins are provided, with dstore being -the most richest in features.

      +the richest in features.

      Dstore requirs a server to run on the remote system. There are several methods to get a server launched for a particular user, the most easy one to set up is the @@ -155,9 +175,6 @@ users can start a dstore server for themselves only, instead of a daemon:

    • On dstore, you can browse into remote archives (*.zip, *.tar) without having to transfer the entire contents. This works thanks to "miners" on the remote side. Custom miners can be plugged into the dstore server.
      Note: Some tar formats currently fail to work. See bug 139207.
    • -
    • On dstore, when you list directories in a remote shell, the shell output is parsed to identify - files, folders and even line numbers from compiler error messages. These items can also be - dragged and dropped, or double clicked to position an editor on them.
  • On dstore, you can choose Search > Remote....
    • The dstore miners support searching a remote file system without having to transfer any data.
  • @@ -183,25 +200,29 @@ users can start a dstore server for themselves only, instead of a daemon:
-The following M3 original plan deliverables did +The following M4 original plan deliverables did not make it into this build:
    -
  • User Actions, and Import/Export were deferred. - A new plan will be published.
  • -
  • JUnit tests did not make it into the build due to pending IP review. +
  • User Actions, and Import/Export were deferred with M3 already. + A new plan + has been published.
  • +
  • JUnit tests did not make it into the build due to pending IP legal review. They are available from Bugzilla - bug 149080 instead.
  • -
  • Examples are not yet available as downloadable package. A CDT Launch Integration Example - and a sample custom subsystem called Daytime Example are available from the - RSE CVS Repository instead.
  • + bug 149080 + instead. Due to the missing Unit Test Framework, automated tests could also + not yet be added to this build. +
  • Examples are not yet available as downloadable package. A CDT Launch Integration Example, + a sample custom subsystem called Daytime Example, + as well as the Tutorial Examples from the ISV Docs are 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.
-The following critical or major bugs are currently known. Since -the goal of this milestone was "functional complete" for soliciting -user and API feedback, we still gave a go for this milestone. +The following critical or major bugs are currently known. We'll strive to fix these as soon as possible.
    -
  • bug 149186 - maj - downloading in background can truncate the remote file
    - -- In order to avoid this bug, do not put any data transfer into background.
  • +
  • bug 150949 - maj - RSE gets unusable when full logging is enabled
  • bug 143462 - maj - [updating] Dirty remote editors do not get notified
  • bug 143292 - maj - [mac] Move Resource dialog causes hang/crash
  • bug 139207 - maj - Browsing into some remote tar archives fails, and may crash the dstore server
    @@ -214,10 +235,6 @@ for an up-to-date list of major or critical bugs, or for a complete up-to-date bugzilla status report, or here for a report on bugs fixed so far. -
diff --git a/releng/org.eclipse.rse.build/template/index.php b/releng/org.eclipse.rse.build/template/index.php index 68dc76e8968..90b0a2180d7 100755 --- a/releng/org.eclipse.rse.build/template/index.php +++ b/releng/org.eclipse.rse.build/template/index.php @@ -16,7 +16,13 @@

These downloads are provided under the Eclipse.org Software User Agreement.

-

To get started, see the build notes.
+ +

+ New and Noteworthy / Build Notes +

+ + To view the map file entries for this build, click here.
To view the compile logs for this build, click @@ -41,11 +47,11 @@ - + - - - +
RSE requires Eclipse-3.2. (download page)
RSE requires Eclipse-3.2. (download page)
Eclipse 3.2RC2, 3.1 or lower will not work!
We've been testing with Eclipse-3.2 RC7, built 2-Jun-2006 (download page)
@@ -115,7 +121,10 @@ Client Runtime Binaries - RSE-runtime-core is required, and includes the user documentation.
+ The runtime binaries do not include source and developer documentation, + and they are available in a more fine-grained packaging for re-use in + other products.
+ RSE-runtime-core is required, and includes the user documentation. All other runtime packages are optional.