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. |
To use the installation, simply start Eclipse with the following command line:
/home/java/eclipse/eclipse |
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.
When installing a new version, follow this to-do list:
eclipse_4.2.1
or eclipse_4.3_modeling
./home/java/eclipse
to point to the new installation.Copy the installation into a new directory and copy all plugins and features of the delta pack into its plugins
and features
folders.
Produce a P2 reference repository for the automatic Maven build to use. To do that, execute the following script with reasonable parameters
#!/bin/bash if [ $# -ne 3 ] then echo "Usage: $0 [ECLIPSE_INSTALLATION] [TARGET_DIR] [REPOSITORY_NAME]" else ECLIPSE_DIR=$1 # e.g. /home/java/eclipse-modeling-4.4.1/ TARGET_DIR=$2 # e.g. /home/java/public_html/repository/ REPO_NAME=$3 # e.g. luna441 CMD="java -jar $ECLIPSE_DIR/plugins/org.eclipse.equinox.launcher_*.jar \ -application org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher \ -metadataRepository file:$TARGET_DIR/$REPO_NAME \ -artifactRepository file:$TARGET_DIR/$REPO_NAME \ -source $ECLIPSE_DIR \ -configs any.any.any \ -compress \ -publishArtifacts" echo $CMD eval $CMD fi |
kieler
user's public_html/repository/
directory.config
repository.
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 |