Rtsys Group Wiki
Page tree
Skip to end of metadata
  • Created by Unknown User (cds), last modified on Sep 04, 2013
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 5 Next »

Eclipse for the People

We maintain an Eclipse installation that is ready to use for developers working at our research group. The installation is usually quite up-to-date, consisting of the most recent Eclipse release with a then-current selection of features already installed. Ideally, this installation can be used to work on every part of KIELER without the need to install additional features.

More importantly, this installation serves as the basis for the target platform KIELER is developed against. We found that a centralized and clearly defined target platform is necessary to avoid any version issues.

This documentation is not valid for the new Eclipse installation central to the institute.

Using the Installation

To use the installation, simply start Eclipse with the following command line:

/home/java/eclipse/eclipse

Administering the Installation

The information in this section is only relevant for those of us that actually administer the shared Eclipse installation. If you're just using it, this is not for you.

To-Do List for Installing a New Version

When installing a new version, follow this to-do list:

  1. Install a basic Eclipse distribution in a properly named folder, e.g. eclipse_4.2.1 or eclipse_4.3_modeling.
  2. Install additional features as described in Getting Eclipse.
  3. Install the delta pack necessary to build products for other platforms.
  4. Update /home/java/eclipse to point to the new installation.
  5. Copy the installation into a new directory and copy all plugins and features of the delta pack into its plugins and features folders.

  6. Produce a P2 reference repository for the automatic Maven build to use. To do that, execute something similar to the following command in /home/java:

    java -jar <eclipse_directory>/plugins/org.eclipse.equinox.launcher_*.jar \
-application org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher \
-metadataRepository file:/home/java/<repository_name> \
-artifactRepository file:/home/java/<repository_name> \
-source /home/java/<eclipse_directory>/ \
-configs any.any.any
-compress
-publishArtifacts
  7. Move the repository to our kieler user's public_html/repository/ directory.
  8. Update the reference repository location in the parent POM files of the source code repositories. Also update the target platform definition files in the config repository.

Note on Windows

In case you want to setup the P2 repository on a Windows system, adapt the file paths as follows and take care to not append a file:\\ after the -source argument.

java [...] -metadataRepository file:\\E:\juno42rep -artifactRepository file:\\E:\juno42rep -source E:\juno42rep -publishArtifacts

 

 

  • No labels