You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lorenzo Bigagli (JIRA)" <ji...@codehaus.org> on 2010/01/20 19:29:55 UTC
[jira] Issue Comment Edited: (WAGON-60) wagon-webdav fails with
commons-logging classloader issues
[ http://jira.codehaus.org/browse/WAGON-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207645#action_207645 ]
Lorenzo Bigagli edited comment on WAGON-60 at 1/20/10 12:28 PM:
----------------------------------------------------------------
We are having this problem with maven 2.2.1, wagon-webdav 1.0-beta-2, maven-site-plugin:2.1 on mvn site:deploy.
Reverting to maven-site-plugin:2.0 worked around the issue.
I have tried to force using commons-logging:1.1.1, but this is not possible in extensions/reporting plugins.
Don't know if this would fix it, though.
Anybody has an idea what is the exact offending component?
There are quite many others reporting apparently similar problems: maybe this should be reopened and investigated further.
was (Author: bigagli):
We are having this problem with maven 2.2.1, maven-site-plugin:2.1 on mvn site:deploy.
Reverting to maven-site-plugin:2.0 worked around the issue.
I have tried to force using commons-logging:1.1.1, but this is not possible in extensions/reporting plugins.
Don't know if this would fix it, though.
Anybody has an idea what is the exact offending component?
> wagon-webdav fails with commons-logging classloader issues
> ----------------------------------------------------------
>
> Key: WAGON-60
> URL: http://jira.codehaus.org/browse/WAGON-60
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-webdav
> Affects Versions: 1.0-beta-1
> Environment: maven 2.0.4
> Reporter: Yuri Schimke
> Assignee: Carlos Sanchez
> Priority: Critical
>
> I tried it with a build extension and also putting jars in $M2_HOME/lib, but both ways I get classloader issues with commons-logging.
> My project uses commons logging and I've seen at least one other report that it can be a problem.
> with things in lib:
> Caused by: 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.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
> at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
> at org.apache.commons.httpclient.HttpClient.<clinit>(HttpClient.java:69)
> ... 30 more
> 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.getLogConstructor(LogFactoryImpl.java:397)
> at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
> ... 34 more
> 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)
> using build extension:
> java.lang.ExceptionInInitializerError
> at org.apache.webdav.lib.WebdavSession.getSessionInstance(WebdavSession.java:145)
> at org.apache.webdav.lib.WebdavSession.getSessionInstance(WebdavSession.java:127)
> at org.apache.webdav.lib.WebdavResource.setClient(WebdavResource.java:1273)
> at org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1298)
> at org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1320)
> at org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1408)
> at org.apache.webdav.lib.WebdavResource.<init>(WebdavResource.java:290)
> at org.apache.maven.wagon.providers.webdav.CorrectedWebdavResource.<init>(CorrectedWebdavResource.java:52)
> at org.apache.maven.wagon.providers.webdav.WebDavWagon.openConnection(WebDavWagon.java:139)
> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
> at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:132)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Jdk14Logger does not implement Log
> at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532)
> at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272)
> at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246)
> at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
> at org.apache.commons.httpclient.HttpClient.<clinit>(HttpClient.java:69)
> ... 30 more
> Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Jdk14Logger does not implement Log
> at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:416)
> at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525)
> ... 34 more
> Caused by: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Jdk14Logger does not implement Log
> at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:412)
> ... 35 more
--
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