If a module class cannot be loaded, the POG throws an IllegalArgumentException and aborts module loading. This prevents other modules from loading appropriately and renders the full POG unusable.
Module loading should be more robust to configuration problems. A missing or malformed module should not invalidate the whole tool.
Add a mis-configured module to the tests to ensure proper operation of the POG in case of configuration error.
Also check whether the static checker is more resilient.
Fixed: exceptions are thrown inside a ModuleLoadingException that is caught in StateTypeManager, ConfigManager, ModuleManager or ModuleFactory.
Faulty modules are now ignored.