Setting up a Taxonomic Editor development environment This document describes all steps necessarry to create a development environment to develop the EDIT Taxonomic Editor. If you are looking for instructions on how to install the EDIT Taxonomic Editor please consult the {{{./manual.html} manual}}. %{toc|section=0|fromDepth=2|toDepth=3} * Requirements * CDM Library development environment set up on your machine (please follow the instructions on {{{http://wp5.e-taxonomy.eu/cdmlib/getting-started.html#Developing_the_CDM_Library}how to install a CDM Library development environment}}) * Eclipse PDE Version >= 3.6 * Checking out the sources Use subversion to check out the sources from the EDIT repository to a location on your development machine. --- $ svn co http://dev.e-taxonomy.eu/svn/trunk/taxeditor --- This will leave you with a directory <<>> containing everything that is needed. We will have a look at the contents later on. * Setting up eclipse The Taxonomic Editor uses maven for convenient configuration and automation of common tasks, such as setting up eclipse. --- $ cd taxeditor/ $ mvn eclipse:eclipse --- This will take some time, as maven will download the required dependencies and configure the projects. After maven has finished follow these steps: * Start up eclipse (make sure you have the required version installed) and open a workspace. * Open up the Import Wizard via Import...> from the menu * Choose Existing projects into Workspace > and click next. * Check and finish the wizard. The package exporer should show a bunch of projects. Although it will also show a bunch of errors, so please read on. * Initializing the cdmlib plugin The project contains all dependencies needed for the CDM Library to work except the <<>> artifacts itself. Therefore the <<>> project will show an error. In order to include these artifacts the project contains a shell (and bash) script to copy these from your local maven repository. Please make sure, that the <<>> artifacts exist in your repository. --- $ cd taxeditor/cdmlib-plugin/ $ ./_makeSources.sh --- Refresh the <<>> project; the errors should be gone. <> This will change in the very near future as these dependencies will also be managed by maven. After this you have to update the classpaths of all plugin projects as well. To do this right-click any of the projects and choose Update Classpath...>. Click