Checkstyle uses commons-logging, which has classloader problems when
initialized within a Maven plugin's container. This results in the
above message - if you run with '-e', you'll see something like the
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.impl.Jdk14Logger does not implement Log
buried deep in the stacktrace.
The only workaround we currently have for this problem is to include
another commons-logging Log implementation in the plugin itself. So,
you can solve the problem by adding the following to your plugin
declaration in your POM:
While this may seem a counter-intuitive way
of configuring a report, it's important to remember that Maven plugins
can have a mix of reports and normal mojos. When a POM has to configure
extra dependencies for a plugin, it should do so in the normal plugins
We will probably try to fix this problem before the next release of the checkstyle plugin.
UPDATE: This problem has been fixed in the SVN trunk version of the checkstyle plugin, which should be released very soon.
Plugins and Lifecycle, Sites & Reporting, Errors