How can I configure logging in the editor?

To get log4j to read your own configuration when developing the editor or anything that has to do with cdmLibrary eclipse plugin you have to tell log4j explicitly what configuration it should use. Otherwise it will scan the classpath and use the first log4j.xml/ file it finds (which is mostly the in cdmlib-commons as it will be the first one it encounters).

Passing the following argument to the Virtual Machine however does the trick:

-Dlog4j.configuration=file:///<path to your personal>/

If you run into trouble , you can debug log4j's startup sequence by passing another argument to the VM.



Some of the taxeditor projects have errors

And the errors do look like the cdmlib dependecies can not be resolved, there are two possible solutions for this problem.

  1. cdmlib-plugin does not contain the cdmlib dependencies

    Please follow the instructions on how to initialize the cdmlib-plugin

  2. Your classpath is outdated

    Update your classpath by right-clicking any of the taxeditor-* projects and choose PDE Tools -> Update Classpath.... Click <Select All> in the dialog and confirm.


Launching the editor from eclipse is simply not working for me.

This could be due to many reasons. Please have a look at the Troubleshooting Editor Launches document on the developers wiki.


I get a "RuntimeException: No application id has been found." preceded by lots of "Missing required bundle" errors when launching my run/debug configuration

Whenever you change something in the plguin dependency hirarchy, i.e. adding, (re)moving, or renaming a dependant plugin your run configuration does not know about that automatically. To solve this:

  • In eclipse, open the Run Configurations wizard
  • Choose the run configuration in question
  • Select the Plug-ins tab
  • Click Deselect All from the buttons on the right
  • Click Add Required Plug-ins
  • Apply your changes

The editor should launch again.


The Taxonomic Editor crashes or freezes in recent Ubuntu versions

In recent Ubuntu versions (13.04, 13.10) the Taxomomic Editor crashes frequently (KDE) or freezes for some time (GNOME). The crashes in KDE are due to a bug which affects all Eclipse indigo (3.7) RCP based applications. Even this bug is currently discussed in the affected developer communities: launchpad bug 1241101, eclipse bug 419729 the cause of this bug is still unclear.

In KDE the crash occurs when the oxygene_gtk is being used. Therefore switching to another GTK2 theme is known as a temporary solution. The GTK2 theme Raleigh has been sucessfully used as a replacement to the oxygen_gtk2. You can either configure it globally or set the environmanet variable GTK2_RC_FILES for the application to run.

GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc "/path/to/EDIT Taxonomic Editor/TaxonomicEditor"

The font size is usually too big in the default configration of this theme. In order to have a nicer font, you can create a file named .gtkrc-eclipse in your user home folder with the following content:

style "eclipse" {
        font_name = "Ubuntu 9"
class "GtkWidget" style "eclipse"

Finally, to launch the Editor, use following command line:

GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc:~/.gtkrc-eclipse "/path/to/EDIT Taxonomic Editor/TaxonomicEditor"


Note for using the EDITor in a Windows Domain/Active directory

Using the EDITor from a user account in an active directory is possible but in the case user profile folders are located on network folders, one of the following problems may occurr, when working with CDM databases:

1) Problems are known, if the user profile path is an UNC path (e.g. "\\server\share"). 2) CDM Information may be written to the local machine's profile copy (if the %USERPROFILE% evironment variable is set respectively) and get lost during synchronization.

If one of the described problems occurs, the following workaround can solve the problem:

- Connect a network drive with the UNC path of your network profile root folder (if that is not already done within your group policies). (Make sure to check the option to reconnect the drive on the next login.) - Start the EDITor with the additional command line option "-Duser.home=I:\", where "I" should be replaced by the letter used for the network drive.

Now all CDM Information will directly be accessed on the network resource. (Note that with such a configuration, it is not recommended to run multiple instances of the EDITor in different machines of the domain using the same user profile in parallel.)


The taxon navigator is greyed out even when I am connected to a data source

If you are using Linux and the non-jre version of the Taxonomic Editor this might happen because of the java version you are using. There might be a problem with OpenJDK9. If possible try switching to OpenJDK8 or u else use the JRE version of the Taxonomic Editor.