some markup goes here
- - - -some markup goes here
-some markup goes here
-some markup goes here
-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:
+ +If you run into trouble , you can debug log4j's startup sequence by passing + another argument to the VM.
+ +And the errors do look like the cdmlib dependecies can not be resolved, there are two possible solutions for this problem.
+Please follow the instructions on how to initialize the cdmlib-plugin
+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.
+This could be due to many reasons. Please have a look at the Troubleshooting Editor Launches document on the developers wiki.
+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:
+The editor should launch again.
+