Taxonomic Editor development environment

The main source of information is Setting up a Taxonomic Editor development environment and #4227

Steps to set up development environment

as documented in #4227

  1. git checkout generated-resources
  2. run
  3. Install m2e feature (if not already installed) in eclipse
  4. Import projects as maven projects into the eclipse workspace
    • Note: A dialog may pop up saying that a mapping for antrun and maybe others are missing. Just install all connectors that are available (Note AM: what does this mean?). The problem with antrun will then be solved by importing cdmlib/lifecycle-mapping-metadata.xml in the preferences under Maven->Lifecycle Mappings->Change mapping file location
  5. Open /eu.etaxonomy.taxeditor/ and reload all locations
  6. Click "Set as target platform"

Updating a project after switching to an other branch for example:

  1. ./setup-project
  2. für alle taxeditor projekte: Maven > Update Project Alt+F5

Solving "cycles exist" problem

Sometimes not all errors (in problems view) disappear after executing the above steps.
In this case it may help to close the projects according to there dependency among each other.
In a first step one may close all projets except .taxeditor, .feature, .cdmlib.
Then repeat

  1. fix all remaining errors (if there are still some)
  2. open the next project and return to previous step
  3. run maven->update project on the currently opened project

Open the projects in the following order: workbench, store, bulkeditor, editor, navigation, {help, molucular.lib, test}, print, molecular, application, test

A detailed dependency graph can be found at TaxonomicEditorArchitecture

Note: often it is enough to seperate the projects between bulkeditor and editor as these tend to create cycles if updated at the same time.

About this page

This page only contains additional information not yet contained in the above linked page.

Download timeouts in the maven validate phase

Note AM (2022-06-15): The below does not seem be critical and also needs to be updated as eclipse-swtbot does not seem to be in use anymore and also indigo is not used anymore. During the build there usually come similar warnings but they do not seem to be critical. However, increasing the timeouts might be a good idea to avoid unwanted behaviour so we keep this instruction here.

This especially happens with the repository from where plugins have to be downloaded.

The according error message in the maven log is:

[ERROR] Internal error: java.lang.RuntimeException: Failed to load p2 repository with ID 'eclipse-swtbot' from location Unable to read repository at Unable to read repository at Read timed out -> [Help 1]

Running maven in the debug mode (-X) reveals that this is a socket timeout:

Caused by: Read timed out
    at Method)
    at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(

In the above download process two classes are involved which have different timeout settings:

  • org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer

setting timeout controls for JRE-http based transport

in org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer


In case of equinox transport timeouts, a message like the following should become visible in the log.

    Timeout while reading input stream.
    The following system properties can be used to adjust the readTimeout, retryAttempts, and closeTimeout

Setting the waggon timeouts in the setting.xml

This is the recommended solution!

see and

This setting is supposed to configure the timeouts which therefore is the correct one in order to fix the above problem.

Setting in the ~/.m2/settings.xml

  <!-- username and password are required otherwise the tycho P2PasswordUtil will fail with an NPE -->

The error which is thrown when the user credentials are missing:

[ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException
        at org.apache.maven.DefaultMaven.execute(
        at org.apache.maven.cli.MavenCli.execute(
        at org.apache.maven.cli.MavenCli.doMain(
        at org.apache.maven.cli.MavenCli.main(
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(
Caused by: java.lang.NullPointerException
        at org.eclipse.tycho.p2.remote.P2PasswordUtil.setCredentials(
        at org.eclipse.tycho.p2.remote.RemoteRepositoryLoadingHelper.setPasswordForLoading(
        at org.eclipse.tycho.p2.remote.RemoteRepositoryLoadingHelper.getEffectiveLocationAndPrepareLoad(
        at org.eclipse.tycho.p2.remote.RemoteMetadataRepositoryManager.translateAndPrepareLoad(
        at org.eclipse.tycho.p2.remote.RemoteMetadataRepositoryManager.loadRepository(
        at org.eclipse.tycho.p2.remote.RemoteMetadataRepositoryManager.loadRepository(
        at org.eclipse.tycho.p2.manager.ReactorRepositoryManagerImpl.computePreliminaryTargetPlatform(
        at org.eclipse.tycho.p2.resolver.P2DependencyResolver.computePreliminaryTargetPlatform(
        at org.eclipse.tycho.core.resolver.DefaultTychoResolver.resolveProject(
        at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(
        at org.apache.maven.DefaultMaven.doExecute(
        at org.apache.maven.DefaultMaven.doExecute(
        at org.apache.maven.DefaultMaven.execute(
        ... 11 more

Further informations especially for remoting you can find here Taxonomic Editor Developers Guide

Updated by Andreas Müller almost 2 years ago · 29 revisions