My experiences with Dentaku's use of maven multiproject build might help others using Eclipse to develop plugin's for Dentaku. The simple rule is run "maven eclipse:generate-classpath" target in each of the child project directories and for the parent directory too, as it has a list of common jar dependencies in it's project.xml.
Then concatinate the produced .classpath files from each child project and delete duplicates.
Then create an Eclipse parent project that includes the source paths for the child projects you are interested in. Include your new 'super' .classpath file in the parent project directory along with the Eclipse produced .project file.
Now I have done this for the selected number of child projects I want to debug in my environment. The others I did not want to debug I left their jars listed in my Java Build Path/Libraries list (which is created from the .classpath file).
One thing still prevented my running my plugins, there was a jar not listed in the any of the project.xml files in all the Dentaku projects. It is a dom class, I found it in XercesParserImpl.jar from the Apache project, beware of this. Seems some have this or another jar with these xml parsing classes in their JDK install.
Now I am happily including other projects I depend on, like generama, with the Eclipse capability to include other Eclipse projects in any other Eclipse project.