Eclipse Development Environment

1. Java
2. Eclipse Settings
3. Subclipse Settings
4. Review Rating
5. Useful Plug-ins
6. Useful Information Sources
7. Eclipse Shortcuts
8. Eclipse Links
9. Continuous Integration Server


Eclipse settings for Java and Eclipse development can be viewed here: AF3 Repository Standard Environment Settings.
Note that these settings are subject to change by the fortiss quality assurance team only.

Eclipse Settings

The settings for Java Compiler and Code Style are contained in the files org.eclipse.jdt.core.prefs and org.eclipse.jdt.ui.prefs in the above settings. These two files are the master copies of the Eclipse settings, which can be included in all plug-ins by using the following method:

  1. First, add the .settings folder to your plugin folder. (Right-click → New → Folder)
  2. Next, add the .settings folder to subversion control. (Right-click → Team → Add to Version Control)
  3. Next, add a subversion property svn:externals to contain two file links (Right-click → Team → Show Properties, right-click on SVN Properties view → Add a Property) :

^/fortiss-std-env/settings/org.eclipse.jdt.core.prefs org.eclipse.jdt.core.prefs

^/fortiss-std-env/settings/org.eclipse.jdt.ui.prefs org.eclipse.jdt.ui.prefs

This links your plugin to the settings master, so changes to the master will be passed to your plugin upon the next Update of your plugin's .settings folder.

Code Templates

Code Styles

Subclipse Settings

The subclipse settings are contained in the file config in the above settings folder.

After you checked out the standard environment into your development workspace, you go to the Eclipse preferences (subsection Team → SVN) and change the configuration location to Use directory: and select the settings folder. Note that you have to select the path according to your operating system. It is not an Eclipse workspace path!

Note also that after you use this subclipse config instead of your default location and you commit something to a repository, Subclipse will write several files to the settings folder (a auth folder with some files, a servers file and a README.txt file). However, we configured the settings folder to svn:ignore those specific files, so you will not have a dirty workspace.

Review Rating

The review rating is a source code annotation that is used to track the state of the source code unit (e.g. a Java class) during the Review Process

Useful Plug-ins

JAR Class Finder

Helps to find jar file corresponding to a specific class. Installation instructions


Tool for code coverage. Installation instructions
Update site:

Tool to ensure common coding conventions.
Installation instructions Update site:

Useful Information Sources

General Information

Eclipse CVS Pathes

Eclipse Shortcuts

Function Description Shortcut
Plug-in Selection Spy Opens a windows showing the classes behind the GUI element under the cursor. <Alt> + <Shift> + F1
Plug-in Menu Spy Opens a windows showing the who is contributing to the menu under the cursor. <Alt> + <Shift> + F2

Eclipse Links

Plug-in Development
Book containing all the information to start with plug-in development. The book is available in the fortiss library.

Eclipse Modeling Framework (EMF)
Site containing the most useful information for Eclipse Modeling Framework (EMF). The book is available in the fortiss library.

Eclipse Modeling Project
Book containing information about GEF and GMF. The book is available in the fortiss library.

EMF Databinding
A short tutorial slide.
A useful blog about databinding.
A quick receipt for databinding usage.

SWT The Standard Widget Toolkit

Rich Client Platform (RCP)
Book containing all the information to start with Rich Client Platform (RCP) application development. The book is available in the fortiss library.

JUnit tests are integrated in the automatic builds performed with Jenkins.

SWT-Bot tests can be used to test the GUI.

introduction to the ANT build system (make for JAVA).

information about the component assembly project

Access of Eclipse JDT Parse Result
Describes access of Java file content via Java Model and Abstract Syntax Tree (AST).

Continuous Integration Server

Jenkins is used as a continuous integration server for AF3. Information on Jenkins

CONQAT is used to perform software quality analysis, integrated in the automatic builds performed with Jenkins.