[ http://jira.codehaus.org/browse/MNG-2421?page=comments#action_69256 ]
Dennis Lundberg commented on MNG-2421: -------------------------------------- This is because docck uses commons-httpclient which in turn uses commons-logging. When commons-logging tries to configure itself it does not find any configuration at all. But it does find log4j in the classpath so it tries to use it. There is no configuration for log4j so it (log4j) opts to shut down completely. I added a dependency in docck on commons-logging 1.1 which has some nice diagnostics to use in cases like this. Then I ran Maven on the webstart-plugin again like this: mvn docck:plugin -Dorg.apache.commons.logging.diagnostics.dest=STDOUT This tells commons-logging to output its diagnostics to STDOUT. The diagnostics shoes the classloading and configuration chain. This might be good in other cases as well. Doing this actually showed the results for docck, so it can be used as a workaround for the time being. I will try to see if I can tweak docck to work better. > [plugins/docck] fail to run > "org.apache.commons.logging.LogConfigurationException: Class > org.apache.commons.logging.impl.Jdk14Logger does not implement Log" > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: MNG-2421 > URL: http://jira.codehaus.org/browse/MNG-2421 > Project: Maven 2 > Type: Bug > Components: Sandbox > Environment: maven 2.0.4 > Reporter: Jerome Lacoste > Attachments: mvn.log > > > This happens when I try running it on the under the > mojo/webstart-maven-plugin/plugin directory -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
