There are issues with the policy/drools-applications maven hierarchy and management of dependencies.   It is specially important in drools-application to have a tidy structure so control loops at runtime do not load unnecessary libraries, or use different versions of libraries in different projects loaded by the same drools-application.   There are some other issues to be cleaned up as well as junit dependencies in non test code, poms artifact ids not matching their directory name, .. that will also need to pay attention at.