[TRINIDAD-2042] Trinidad TagDoc report plugin does not allow mvn site:site target to run

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0-core
• Component/s: Plugins
• Assignee: Scott O'Bryan
• Reporter: Scott O'Bryan
• Due: 20/Feb/11
• Created: 20/Feb/11 18:14
• Updated: 09/Sep/11 17:26
• Resolved: 01/Mar/11 17:21

Description

When running 'mvn site:site' on main, the following error is thrown:

org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.) (Caused by org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.))
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370)
at org.apache.commons.digester.Digester.<init>(Digester.java:304)
at org.apache.myfaces.trinidadbuild.plugin.tagdoc.TagdocReport.readIndex(TagdocReport.java:1673)
at org.apache.myfaces.trinidadbuild.plugin.tagdoc.TagdocReport.processIndex(TagdocReport.java:1592)
at org.apache.myfaces.trinidadbuild.plugin.tagdoc.TagdocReport.executeReport(TagdocReport.java:105)

....

It looks like there is an incompatible logger version or the logger has been declared multiple times in the environment. This must be fixed before the maven site can be generated.