[jira] (WAGON-356) java.lang.ClassNotFoundException: org.slf4j.impl.StaticLoggerBinder
[
https://jira.codehaus.org/browse/WAGON-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309431#comment-309431
]
Lorenzo Bigagli commented on WAGON-356:
---
I had the same problem with Maven 3.0.3, maven-site-plugin 3.1,
wagon-webdav-jackrabbit 2.2.
I confirm that setting jackrabbit as an extension solves the problem.
However, I would avoid extensions and keep jackrabbit as a maven-site-plugin
dependency, so I worked around the issue forcing slf4j 1.6.1 (the policy of
binding changed with 1.6, see
http://www.slf4j.org/codes.html#StaticLoggerBinder).
I suggest future versions of jackrabbit update their dependency on slf4j, to
avoid all this.
org.apache.maven.plugins
maven-site-plugin
3.1
org.apache.maven.wagon
wagon-webdav-jackrabbit
2.2
org.slf4j
slf4j-api
1.6.1
> java.lang.ClassNotFoundException: org.slf4j.impl.StaticLoggerBinder
> ---
>
> Key: WAGON-356
> URL: https://jira.codehaus.org/browse/WAGON-356
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-webdav
>Affects Versions: 2.0
> Environment: Maven 3.0.3, maven-site-plugin 3.0,
> wagon-webdav-jackrabbit 2.0
>Reporter: Daniel Spilker
>Assignee: Olivier Lamy
>
> When performing a release the site deployment fails due to a
> ClassNotFoundException.
> {noformat}
> [INFO] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> [INFO] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
> further details.
> [INFO] Nov 8, 2011 10:28:56 AM org.sonatype.guice.bean.reflect.NamedClass
> [INFO] WARNING: Error injecting:
> org.apache.maven.wagon.providers.webdav.WebDavWagon
> [INFO] com.google.inject.ProvisionException: Guice provision errors:
> [INFO]
> [INFO] 1) Error injecting constructor, java.lang.NoClassDefFoundError:
> org/slf4j/impl/StaticLoggerBinder
> [INFO] at
> org.apache.maven.wagon.providers.webdav.WebDavWagon.(Unknown Source)
> [INFO] while locating org.apache.maven.wagon.providers.webdav.WebDavWagon
> [INFO]
> [INFO] [INFO] [ERROR]
> 1 error
> [INFO] Unsupported protocol: 'dav' for site deployment to
> distributionManagement.site.url=dav:https://repository.coremedia.com/...
> [INFO] at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:977)
> [INFO] at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1003)
> [INFO] at
> org.sonatype.guice.bean.reflect.AbstractDeferredClass.get(AbstractDeferredClass.java:47)
> [INFO] at
> com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
> [INFO] at
> com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:968)
> [INFO] at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1014)
> [INFO] at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:964)
> [INFO] at com.google.inject.Scopes$1$1.get(Scopes.java:59)
> [INFO] at
> org.sonatype.guice.bean.locators.LazyBeanEntry.getValue(LazyBeanEntry.java:79)
> [INFO] at
> org.sonatype.guice.plexus.locators.LazyPlexusBean.getValue(LazyPlexusBean.java:53)
> [INFO] at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:243)
> [INFO] at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:235)
> [INFO] at
> org.apache.maven.repository.legacy.DefaultWagonManager.getWagon(DefaultWagonManager.java:764)
> [INFO] at
> org.apache.maven.repository.legacy.DefaultWagonManager.getWagon(DefaultWagonManager.java:747)
> [INFO] at
> org.apache.maven.plugins.site.AbstractDeployMojo.getWagon(AbstractDeployMojo.java:354)
> [INFO] at
> org.apache.maven.plugins.site.AbstractDeployMojo.deploy(AbstractDeployMojo.java:264)
> at
> org.apache.maven.plugins.site.AbstractDeployMojo.deployTo(AbstractDeployMojo.java:257)
> [INFO] at
> org.apache.maven.plugins.site.AbstractDeployMojo.execute(AbstractDeployMojo.java:165)
> [INFO] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> [INFO] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> [INFO] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> [INFO] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> [INFO] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> [INFO] at
> org.apache.maven.lifecycl
[jira] Created: (MSITE-459) Fatal Error on site:deploy
Fatal Error on site:deploy
--
Key: MSITE-459
URL: http://jira.codehaus.org/browse/MSITE-459
Project: Maven 2.x Site Plugin
Issue Type: Bug
Components: site:deploy
Affects Versions: 2.1
Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_17
OS name: "mac os x" version: "10.6.2" arch: "x86_64" Family: "mac"
Reporter: Lorenzo Bigagli
Priority: Blocker
Attachments: lablib-checkboxtree.zip
site:deploy fails as follows (related to wagon-webdav dependencies?
Commons-logging?).
Reverting to maven-site-plugin:2.0.x works around the issue.
I attach the project zip (appropriate server/dav configuration needed to
reproduce the problem).
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'site'.
[INFO] org.apache.maven.plugins: checking for updates from
maven2-repo-dev-java-net
[INFO] org.apache.maven.plugins: checking for updates from
maven-repository.dev.java.net
[INFO] org.apache.maven.plugins: checking for updates from hosted.repos
[INFO] org.codehaus.mojo: checking for updates from maven2-repo-dev-java-net
[INFO] org.codehaus.mojo: checking for updates from
maven-repository.dev.java.net
[INFO] org.codehaus.mojo: checking for updates from hosted.repos
[INFO]
[INFO] Building CheckboxTree
[INFO]task-segment: [site:deploy]
[INFO]
[INFO] [site:deploy {execution: default-cli}]
WAGON_VERSION: 1.0-beta-2
http://zeus.pin.unifi.it/projectsSites/lablib-checkboxtree_snap - Session:
Disconnecting
http://zeus.pin.unifi.it/projectsSites/lablib-checkboxtree_snap - Session:
Disconnected
[FATAL ERROR] org.apache.maven.plugins.site.SiteDeployMojo#execute() caused a
linkage error (java.lang.ExceptionInInitializerError) and may be out-of-date.
Check the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1]
urls[0] =
file:/Users/bigagli/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1/maven-site-plugin-2.1.jar
urls[1] =
file:/Users/bigagli/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
urls[2] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.2/doxia-module-xhtml-1.1.2.jar
urls[3] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.2/doxia-core-1.1.2.jar
urls[4] =
file:/Users/bigagli/.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
urls[5] =
file:/Users/bigagli/.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar
urls[6] =
file:/Users/bigagli/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar
urls[7] =
file:/Users/bigagli/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar
urls[8] =
file:/Users/bigagli/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
urls[9] =
file:/Users/bigagli/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
urls[10] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.2/doxia-module-apt-1.1.2.jar
urls[11] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.2/doxia-module-xdoc-1.1.2.jar
urls[12] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.2/doxia-module-fml-1.1.2.jar
urls[13] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.2/doxia-decoration-model-1.1.2.jar
urls[14] =
file:/Users/bigagli/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.1.2/doxia-site-renderer-1.1.2.jar
urls[15] =
file:/Users/bigagli/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
urls[16] =
file:/Users/bigagli/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.8/plexus-velocity-1.1.8.jar
urls[17] =
file:/Users/bigagli/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar
urls[18] =
file:/Users/bigagli/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
urls[19] = file:/Users/bigagli/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar
urls[20] =
file:/Users/bigagli/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.2/maven-doxia-tools-1.2.jar
urls[21] =
file:/Users/bigagli/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
urls[22] =
file:/Users/bigagli/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
urls[23] =
file:/Users/bigagli/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar
urls[24] =
file:/Users/bigagli/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar
urls[25] =
file:/Users/bigagli/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.5/servlet-api-2.5-6.1.5.jar
[FATAL ERROR] Cont
[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.(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.
[jira] Commented: (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 commented on WAGON-60: -- 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.(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.(WebdavResource.java:290) > at > org.apache.maven.wagon.providers.webdav.CorrectedWebdavResource.(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(SiteDeplo
[jira] Commented: (MNG-3122) MAVENPROJECT: getActiveProfiles() returning duplicate activeByDefault profile defined in LOCAL_HOME/.m2/settings.xml
[ http://jira.codehaus.org/browse/MNG-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142166#action_142166 ] Lorenzo Bigagli commented on MNG-3122: -- This is the console output I get: pan:prova bigagli$ mvn help:active-profiles [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'help'. WAGON_VERSION: 1.0-beta-2 [INFO] [INFO] Building Unnamed - it.cnr.imaa.essi:lablib-prova:jar:1.0 [INFO]task-segment: [help:active-profiles] (aggregator-style) [INFO] [INFO] [help:active-profiles] [INFO] Active Profiles for Project 'it.cnr.imaa.essi:lablib-prova:jar:1.0': The following profiles are active: - property-injection (source: settings.xml) - property-injection (source: settings.xml) > MAVENPROJECT: getActiveProfiles() returning duplicate activeByDefault profile > defined in LOCAL_HOME/.m2/settings.xml > > > Key: MNG-3122 > URL: http://jira.codehaus.org/browse/MNG-3122 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 2.0.7 >Reporter: Ian Berry > Fix For: 2.0.x > > Attachments: duplicateActiveProfiles.JPG, > duplicateActiveProfiles.zip, settings.xml > > > MavenProject:getActiveProfiles() is returning duplicate activeByDefault > profiles defined in LOCAL_HOME/.m2/settings.xml. > Attached settings.xml resides in LOCAL_HOME/.m2. > Below is part of the output of a buildInformation plugin i am writing, which > shows profile WLS8 twice. > > >default-repositories >settings.xml > > > WLS8 > settings.xml > > > WLS8 > settings.xml > > -- 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
