Building the Overture Platform in Eclipse
From Wiki.overturetool.org
| Warning: These instructions are no longer entirely correct. The maven build process is presently being fixed. |
The Overture platform is separated into three parts (see Overture Platform Architecture) which all can be developed in the Eclipse development environment. See Development Environment for environment setup.
Preparation
Before any projects can be imported into Eclipse they need to be checked out Overture Sourceforge. When this is done there will be a setup script in the trunk which must be executed with the option install.
setup install
This script will:
- Generate all eclipse project and settings files needed for Eclipse importing
- Install all core projects in the users local repository
like this if we assume trunk is the current directory:
cd core mvn install cd .. cd tools mvn install cd .. cd ide mvn install -P nocompile cd .. mvn eclipse:eclipse cd ide mvn eclipse:eclipse
The repeated eclipse:eclipse is there to first build the projects and then sync the Manifest.MF with the .classpath file.
Importing
Start Eclipse with Maven support and create a workspace. Then:
- Select the following menu:
- Files
- Import
- (General) Maven Projects
- Select the projects of interest must be selected. We recommend to only import the leafs of the tree to minimize the number of imported projects. See
- We suggest to organize the projects in working sets in eclipse as follows:
- core - All projects imported from /core
- Tools - All projects imported from /tools
- IDE - All projects imported from /ide except the projects mentioned in the other working sets
- IDE_Plugins - All projects imported from /ide/plugins
- IDE_features - Feature projects. Not imported with Maven
What to do if there is errors after import
Errors after imports can either occur if:
- The Manifest.MF has jar files under runtime which does not exist.
- This is solved by running mvn eclipse:eclipse in the project folder and refreshing the project in Eclipse.
- The project configuration is out of sync.
- This is fixed by selecting the project and using the context menu: Maven->Update Project configuration.
- The Manifest.MF has jar files under runtime which does not exist.
