[
https://jira.codehaus.org/browse/MSITE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298421#comment-298421
]
Dennis Lundberg commented on MSITE-642:
---------------------------------------
Hi David,
Because of the bad decision by JBoss to include their own (slightly modified)
copy of commons-logging in JBoss 4, adding newer versions of commons-logging in
an application deployed to a JBoss 4 instance can lead to problems like this.
The reason is that you end up with two incompatible versions of commons-logging
(1.0.x and 1.1.x) in your applications classpath.
There are two possible workarounds:
1. Use a newer version of JBoss that doesn't bundle commons-logging in a
classloader that is shared with the installed applications. Sorry, but I don't
know which version.
2. Try to replace the version of commons-logging that is included in JBoss. I
haven't tried this but it might work. Use version 1.1.1 if possible.
> 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
