S3 Wagon provider added as an extension causes exception when resolving 
dependencies
------------------------------------------------------------------------------------

                 Key: MDEP-207
                 URL: http://jira.codehaus.org/browse/MDEP-207
             Project: Maven 2.x Dependency Plugin
          Issue Type: Bug
          Components: copy, copy-dependencies
    Affects Versions: 2.1, 2.0
         Environment: OS/X, Maven 2.0.9, Java 1.5
            Reporter: Yuri de Wit
            Assignee: Brian Fox



This is the extension I am using:
{noformat}
<extensions>
                <extension>
                        <groupId>org.springframework.build.aws 
                        </groupId>
                        <artifactId>org.springframework.build.aws.maven 
                        </artifactId>
                        <version>2.0.0.RELEASE</version>
                </extension>
</extensions>
{noformat}

It is being taken from this repository: 
{noformat}
                <repository>
                        <id>spring-snapshot</id>
                        <name>Spring Portfolio Snapshot Repository</name>
                        
<url>http://s3.amazonaws.com/maven.springframework.org/snapshot</url>
                </repository>
{noformat}

And depends on httpclient-3.1, which in turn depends on commons-logging 1.0.4.

When I try to mvn dependency:copy and there is a dependency that needs to be 
resolved from s3 I get the following exception:

{noformat}
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
Invalid class loader hierarchy.  You have more than one version of 
'org.apache.commons.logging.Log' visible, which is not allowed.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.ExceptionInInitializerError
        at 
org.springframework.aws.maven.SimpleStorageServiceWagon.connectToRepository(SimpleStorageServiceWagon.java:66)
        at 
org.springframework.aws.maven.AbstractWagon.connect(AbstractWagon.java:121)
        at 
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:435)
        at 
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:370)
        at 
org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:97)
        at 
org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:65)
        at 
org.apache.maven.artifact.transform.SnapshotTransformation.transformForResolve(SnapshotTransformation.java:63)
        at 
org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForResolve(DefaultArtifactTransformationManager.java:57)
        at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:129)
        at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74)
        at 
org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.getArtifact(AbstractFromConfigurationMojo.java:242)
        at 
org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.getProcessedArtifactItems(AbstractFromConfigurationMojo.java:143)
        at 
org.apache.maven.plugin.dependency.fromConfiguration.CopyMojo.execute(CopyMojo.java:69)
        at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
        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: 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.jets3t.service.S3Service.<clinit>(S3Service.java:70)
        ... 31 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)
        ... 35 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)
        ... 36 more
[INFO] ------------------------------------------------------------------------
{noformat}

-- 
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

        

Reply via email to