General 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/log4j.properties file it finds (which is mostly the log4j.properties 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>/log4j.properties

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

-Dlog4j.debug 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"