Eclipse Development Environment¶
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.
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:
- First, add the .settings folder to your plugin folder. (Right-click → New → Folder)
- Next, add the .settings folder to subversion control. (Right-click → Team → Add to Version Control)
- 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) :
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.
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.
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
JAR Class Finder
Helps to find jar file corresponding to a specific class. Installation instructions
Useful Information Sources¶
Eclipse CVS Pathes
|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|
Book containing all the information to start with plug-in development.
http://www.informit.com/store/product.aspx?isbn=032142672X The book is available in the fortiss library.
Eclipse Modeling Framework (EMF)
Site containing the most useful information for Eclipse Modeling Framework (EMF).
http://www.informit.com/store/product.aspx?isbn=9780321331885 The book is available in the fortiss library.
Eclipse Modeling Project
Book containing information about GEF and GMF. http://www.informit.com/store/product.aspx?isbn=0321635175 The book is available in the fortiss library.
A short tutorial slide. http://tomsondev.files.wordpress.com/2011/05/emf-databinding.pdf
A useful blog about databinding. http://tomsondev.bestsolution.at/category/databinding/
A quick receipt for databinding usage. http://wiki.eclipse.org/EMF/Recipes#Recipe:_JFace_Viewers_and_1:n_associations
http://eclipse.org/swt/ The Standard Widget Toolkit
Rich Client Platform (RCP)
Book containing all the information to start with Rich Client Platform (RCP) application development. http://www.informit.com/store/product.aspx?isbn=0321334612 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). http://www.vogella.de/articles/EclipseJDT/article.html
Continuous Integration Server¶
Jenkins is used as a continuous integration server for AF3.
http://jenkins-ci.org/ Information on Jenkins
CONQAT is used to perform software quality analysis, integrated in the automatic builds performed with Jenkins.