This is actually a maven wagon issue:

http://jira.codehaus.org/browse/MNG-4301


Try using the extension specified in that issue, it seems to solve it for me:

            <extension>
                <groupId>org.apache.maven.wagon</groupId>
                <artifactId>wagon-webdav</artifactId>
                <version>1.0-beta-2</version>
            </extension>

Rich

On Dec 7, 2011, at 3:59 AM, Julien HENRY wrote:

> Hi,
> 
> I was bitten by bug OutOfMemory when deploying big files 
> (http://jira.codehaus.org/browse/WAGON-272) so I decided to switch to dav 
> protocol. In my pom I have added "dav:" in front of URL in 
> distributionManagement section, and also added webdav wagon this way:
> <build>
>   <pluginManagement>
>     <plugin>
>       <groupId>org.apache.maven.plugins</groupId>
>       <artifactId>maven-deploy-plugin</artifactId>
>       <version>2.7</version>
>         <dependencies>
>              <dependency>
>                    <groupId>org.apache.maven.wagon</groupId>
>                    <artifactId>wagon-webdav-jackrabbit</artifactId>
>                    <version>2.1</version>
>              </dependency>
>         </dependencies>
>     </plugin>
> ...
> 
> 
> Then I tried to deploy on our Nexus repo using Maven 2.2.1, and the result 
> was corrupted md5 checksum for all files (pom, metadata.xml, ...). My feeling 
> was that it was not the correct wagon that was used (I suppose the one 
> included in Maven 2.2.1 takes priority over the one declared as dependency of 
> m-deploy-p). So I tried to switch to an extension:
>         <extensions>
>             <extension>
>                 <groupId>org.apache.maven.wagon</groupId>
>                 <artifactId>wagon-webdav-jackrabbit</artifactId>
>                 <version>2.1</version>
>             </extension>
>         </extensions>
> 
> But then my build failed with the following error:
> [INFO] [deploy:deploy {execution: default-deploy}]
> [INFO] Retrieving previous build number from macif-snapshots-repo
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> ...
> [ERROR] BUILD ERROR
> ...
> Caused by: java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder
>       at org.slf4j.LoggerFactory.getSingleton(LoggerFactory.java:230)
>       at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
>       at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:112)
>       at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:275)
>       at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:248)
>       at 
> org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:155)
>       at 
> org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:131)
>       at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:685)
>       at 
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.<clinit>(MultiThreadedHttpConnectionManager.java:70)
>       at 
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.<init>(AbstractHttpClientWagon.java:181)
>       at 
> org.apache.maven.wagon.providers.webdav.WebDavWagon.<init>(WebDavWagon.java:64)
> ...
> 
> 
> Any suggestion?
> 
> My need is to be able to deploy big files with Maven 2.2.1 and/or Maven 
> 3.0.3. I can do any modification in our corporate pom but I don't want to 
> rely on anything in settings.xml as I can't be sure users will do the 
> modification and I don't want to corrupt my repository.
> 
> Thanks
> 
> Julien

Reply via email to