Eclipse


The OSGi Service Platform and the Equinox OSGi implementation ship with Eclipse. You can start an OSGi container and use the console to manage a running OSGi platform, launch equinox and check running OSGi bundles and their (potential) dependencies.

Window> Preferences> Java> code Style> Formatter
2 space tabs
Line Wrapping> Maximum Line Width 100

Eclipse Shortcut Keys


Ctrl + Shift + T     : Open Type

Ctrl + Shift + F4     : Close all Opened Editors 

Ctrl + O                 : Open declarations
Ctrl + E                 : Open Editor

Alt + Shift + R        : Rename

Alt + Shift + L         : extract to Local Variable
Alt + Shift + M        : extract to Method

F3 : Open Declaration


Ctrl+.    go directly to the next warning or error in your current source file.

Alt+Left / Alt+Right      navigate back and forth to where you where before
Ctrl+Q     go to last edit location
Ctrl+T     type hierarchy

Ctrl+1

Ctrl+F11 (Run last launched) or F11 (debug last launched)?


Remote System Explorer

update site:

   http://download.eclipse.org/dsdp/tm/updates/3.0/








Update site: http://download.eclipse.org/tm/updates/3.3/
select "Remote system Explorer End User Runtime"
Window > Open P

erspective > Other > Remote System Explorer.

File > new > Remote System Explorer > connection > SSH Only

Install server : 

Prerequisites

To use the Remote System Explorer communications server daemon you need to install Perl. Using the daemon helps eliminate some of the manual steps when you connect to the server.

Installing the server code

  1. Find the package that contains the server. The server code is usually packaged with the containing product and you should refer to that product's documentation for finding and installing the server package. The server is also available, however, on the Eclipse Target Management download site as the package rseserver-<version>-<os>.tar. For example, rseserver-2.0-linux.tar contains the release 2.0 server for Linux. There are servers for Linux, AIX, a generic Unix version that can be tailored to your particular flavor of Unix, and an experimental Mac OS X version.
  2. Ensure that Perl is installed.
  3. Ensure that a Java Runtime Environment (JRE) version 1.4 or higher is installed. An IBM, Oracle or equivalent JRE is required; The gcj-based jvm shipped with most Linux distributions does not work. If in doubt, run the command
    java -version (see below) and check if there is a reference to gcj. You can download an Oracle JRE from http://www.oracle.com/technetwork/java/.
  4. Create a directory where you want to install the server code. The remainder of these instructions will assume the directory /opt/rseserver (suitable for team sharing), but you are free to use any directory.
  5. Upload the server package to this directory. You can use FTP.
  6. Switch to the /opt/rseserver directory by typing:
    cd /opt/rseserver
  7. Run the following command in the /opt/rseserver directory to extract the server code from the package appropriate to your operating system. For linux this command is:
    tar -xf rseserver-2.0-linux.tar

To start the server with the server daemon
Ensure that you are running using the root user ID. (If the daemon is not run under root, it will be unable to authenticate connecting users.) Run the following commands:
$ su -l root cd /opt/rseserver
$ perl ./daemon.pl [daemonPort] [serverPortRange]
Note that the server daemon runs on port 4075 by default. You can pass the optional daemonPort argument to force a different port if you want.
If your daemon runs behind a firewall, you may want to specify the optional serverPortRange argument to restrict selected server ports to the range given:
$ perl ./daemon.pl 4075 10000-10010

SSL Encryption and Firewalls 
By default the RSE DStore connection is unencrypted. You can, however, configure it to use SSL encryption. Because all dstore data transfer is done through a single TCP/IP connection, the connection can also be tunneled through an ssh channel. In fact, the same ssh channel can also be used to start the server, like in the following example: 
$ ssh -l root sm321-01.cise.ufl.edu -L27127:sm321-01.cise.ufl.edu:27127 "sh -c 'cd /opt/rseserver/; perl ./server.pl 27127'"

Here, the RSE Server is started on port 27127 through an ssh connection, and at the same time port 27127 is forwarded through ssh to the local host. You can now connect RSE to localhost:27127, and the connection will transparently be forwarded to the remote system.