[
https://jira.codehaus.org/browse/MSITE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297885#comment-297885
]
Dennis Lundberg commented on MSITE-642:
---------------------------------------
I see from the log that this is built on Jenkins running on JBoss.
Do you get the same error when you run this build locally?
The reason I ask is because JBoss has has several problems relating to
commons-logging.
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-site-plugin:3.1:site:
> java.lang.ExceptionInInitializerError: null
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MSITE-642
> URL: https://jira.codehaus.org/browse/MSITE-642
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Affects Versions: 3.1
> Environment: Using Maven 3.0.4
> Reporter: David Pilato
> Attachments: mavensite3.log, pom.xml, pom.xml
>
>
> After updating maven site version from 3.0 to 3.1, I get the following error
> when running mvn clean site on my project.
> As far as I can see, the error come from :
> 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.getLogConstructor(LogFactoryImpl.java:385)
> ... 61 more
> Full log is attached.
> I added my parent pom.xml file and the pom.xml file for the first module
> (which fails).
> Hope this help.
> David.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
