This seems to be related to the merged PR from 
https://github.com/apache/maven-wagon/pull/51/files 
<https://github.com/apache/maven-wagon/pull/51/files>.
Not sure why the error happens though...

> On 8. Jan 2019, at 17:27, Enrico Olivelli <[email protected]> wrote:
> 
> Hi,
> I have this error with Maven 3.6.0 and maven-site-plugin 3.7.1 and
> wagon-webdav-jackrabbit 3.3.1
> 
> java.lang.NoSuchMethodError:
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
>    at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.access$000
> (AbstractHttpClientWagon.java:112)
>    at 
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon$RequestEntityImplementation.writeTo
> (AbstractHttpClientWagon.java:185)
>    at org.apache.http.impl.DefaultBHttpClientConnection.sendRequestEntity
> (DefaultBHttpClientConnection.java:156)
> 
> 
> Is there anyworkaround ?
> I am trying to force all of the dependencies in the site plugin
> 
> <plugin>
>    <groupId>org.apache.maven.plugins</groupId>
>    <artifactId>maven-site-plugin</artifactId>
>    <version>3.7.1</version>
>    <dependencies>
>    <dependency>
>      <groupId>org.apache.maven.wagon</groupId>
>      <artifactId>wagon-http</artifactId>
>      <version>3.3.1</version>
>    </dependency>
>    <dependency>
>      <groupId>org.apache.maven.wagon</groupId>
>      <artifactId>wagon</artifactId>
>      <version>3.3.1</version>
>      <type>pom</type>
>    </dependency>
>    <dependency>
>      <groupId>org.apache.maven.wagon</groupId>
>      <artifactId>wagon-http-shared</artifactId>
>      <version>3.3.1</version>
>    </dependency>
>    <dependency>
>      <groupId>org.apache.maven.wagon</groupId>
>      <artifactId>wagon-webdav-jackrabbit</artifactId>
>      <version>3.3.1</version>
>    </dependency>
>          </dependencies>
> 
> But no result...
> 
> Thanks
> 
> Enrico
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

Reply via email to