Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

You have two choices here: either work on our server, or install Eclipse on your own computer.

Working on Our Server

Using one of the thin clients found all over the place, you can use the reference installation of Eclipse on our server. Just log in and start Eclipse using the following command line:

   /home/java/eclipse/eclipse

This  will always point to the current reference installation. Feel free to setup a link on your desktop to avoid having to start the console every  time.

Installing Eclipse on Your Own Computer

If you want to install Eclipse on your own computer, just expand the installation guide below. Note that you need at least Java 1.5 to run and use Eclipse and KIELER. On Windows, double-click the eclipse.exe found in the installation directory. On Linux, execute the eclipse executable found in the installation directory.

The first step in getting your own Eclipse installation is to download Eclipse Kepler 4.3 from the Eclipse download page. The download page offers several different variants of Eclipse; you want the Eclipse Modeling Tools, as they come with many of the features required for KIELER development already installed. Once Eclipse is installed and started, you need to install the remaining features. For each of these steps, fire up the software installation dialog by clicking Install New Software... from the Help menu.

  1. From the Kepler update site (should already be in the Work with list), choose the following components:
    1. Xtext SDK
    2. Xtend SDK
    3. Xpand SDK (only for Semantics project)
    4. MWE 2 language SDK
    5. MWE 2 runtime SDK
    6. MWE SDK
  2. From the Itemis update site, install the following:
    1. Xtext Antlr SDK Feature
  3. From the Checkstyle update site, install the following:
    1. Eclipse Checkstyle Plug-in
  4. From the FindBugs update site, install the following:
    1. FindBugs Feature
  5. From the Google Guava update site, install the following:
    1. Guava: Google Core Libraries for Java 1.5 - SDK (be sure to install version 10.0.1, since EMF Compare currently doesn't like newer versions; you will need to uncheck the Show only the latest version of available software checkbox to see older versions. (error)Is this still valid for EMF Compare 2.0?)

The following dependencies are only required for few subprojects of KIELER:

  1. SVG export functionality is based on the Batik Swing feature  from the Orbit update site. Make sure to install version 1.6 of the plug-in, not version 1.7.
  2. If you want to work on the Graphiti integration of KIELER Layout, install the Graphiti SDK Plus from the Kepler update site.
  3. If you want to work on KlighDning, install the Jetty bundles from the Jetty update site. Currently we are using version 8.
  4. If you want to work on KWebS, install the JAX-WS Tools from the Kepler update site.
  5. If you're interested in e4 application development, install the following from the e4 update site: (If you don't know what e4 application development is, odds are you won't need these.)
    1. Eclipse e4 Tools (Incubation)
    2. We originally also installed E4 CSS Spy (Incubation), but it installed keyboard shortcuts that somehow conflicted with Eclipse's built-in ones. This lead to common shortcuts such as Ctrl+Z and Ctrl+Space not working properly, which is why we don't install the CSS Spy for the time being.
  6. If you use some code from Subversion repositories, install the Subversive SVN Team Provider from the Kepler update site. You will be prompted to install a Subversive Connector upon restarting Eclipse; select one that fits to your installed SVN version. KIELER does not use Subversion anymore.
  7. Some deprecated dependencies (we don't work with these frameworks anymore):
    1. Graphical Editing Framework Zest Visualization Toolkit SDK
    2. Graphical Modeling Framework (GMF) Notation SDK
    3. Graphical Modeling Framework (GMF) Tooling SDK

After everything is installed, restart Eclipse and configure your installation according to our configuration guidelines.

Esoteric Dependencies

Some projects require a bunch of more esoteric dependencies. For each one of them, make sure you actually work with a given project and then install the required dependencies only if necessary. Note: This list has not yet been updated for Eclipse 4.2.1. If this doesn't work, find an adult!

  1. Some plug-ins require Papyrus to be installed, which you should probably simply google for.

Memory Problems

Regardless of the two methods you've decided on following, Eclipse may well run into problems due to lack of memory. If so, navigate to your installation directory, open eclipse.ini, and edit it to contain the following lines:

Eclipse Configuration
--launcher.XXMaxPermSize 256M
--launcher.XXPermSize 64M
-Xmn128m
-Xmx768m

For more information about what these settings to, see this page.

  • No labels