Release Notes for RSE 1.0M1
April 27, 2006

Download RSE SDK, and either

• Extract it into your installation of Eclipse 3.2RC1a, 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 choose Import > Plug-in development > Plug-ins and Fragemtns. Select the RSE directory and import everything either as binary folders.

Even without an actual connection to a remote system, you can start experimenting with the RSE UI on the 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)

RSE is a framework that supports plugging in many different communication protocols. By default, the dstore and FTP protocol plug-ins are provided, with dstore being a lot richer 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 daemon method. To start a dstore launcher daemon,

• On Windows:
  • Extract the rseserver-*-win32.zip package and cd to it.
  • Run setup.bat, then run daemon.bat.
• On Linux or AIX or other Unix:
  • Extract the appropriate rseserver-*.tar.
  • Become root and cd to the package directory.
  • Make sure that a Sun or IBM JRE 1.4 or higher is in the PATH. The gcj-based java installation that comes with many Linux distributions will not do! You can download a Sun JRE from http://java.sun.com.
  • Run perl daemon.pl.

Note: In its default configuration for testing, the dstore daemon accepts unencrypted passwords from the RSE client. For production use, SSL can be enabled in order to encrypt connections, or the RSE server can be launched differently (e.g. through ssh).

• In the RSE Perspective, Remote Systems View, press the New Connection button.
  • Note: In the Preferences, you can enable displaying available new connection types in the RSE tree.
• Enter a name, system type and IP address for a remote system running a dstore server.
  • You can also run a dstore server on the local machine for testing. In this case, type "localhost" as address.
  • You can press Finish right away, the wizard defaults are fine for dstore connections.
• Browse remote files, or open remote shells.
  • You can drag and drop files between local and remote file systems, between editors and any view. Files are transferred as needed.
  • 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.
  • 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.
• Choose Search > Remote....
  • The dstore miners support searching a remote file system without having to transfer any data.
• When the remote system is Linux, AIX or Other Unix:
  • Browse remote Processes.
  • Select "My Processes" and choose context menu > Monitor.
  • Enable polling, choose a short wait time. See processes appear and vanish as you perform commands in a remote shell.

• Documentation is not yet part of the SDK.
• The Wizard is not yet completely replacable.
• The persistence framework is not yet pluggable.
• The secure shell (ssh) plugin is not yet part of the core distribution (it's available from bug 138337 instead).

• 138619 - Local Shell fails on Windows 2000
• 138367 - Filetype Pattern Matching fails in local shells
• 139207 - Browsing into some remote tar archives fails, and may crash the dstore server