[ 
https://issues.apache.org/jira/browse/WAGON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024974#comment-17024974
 ] 

Michael Medin commented on WAGON-576:
-------------------------------------

Well, it is not unusable...

If you implement the forked interface and set a dependency for the file it 
works, so one option would be to publish the jar and update the documentation 
to the forked interface.

But as I am not sure why there is a forked version of the http client I cant 
really say which is best route, in general I guess it would be better to not 
fork http client at all and use the published version. 

 

> Retry handler docs are possibly wrong
> -------------------------------------
>
>                 Key: WAGON-576
>                 URL: https://issues.apache.org/jira/browse/WAGON-576
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http
>    Affects Versions: 3.3.4
>            Reporter: Michael Medin
>            Priority: Minor
>
> The documentation for retry 
> [https://maven.apache.org/wagon/wagon-providers/wagon-http/] says that a 
> custom retry handler should implement org.apache.http.client.Interface 
> HttpRequestRetryHandler.
> This is may not be true as at least the wagon-http used by Maven has packaged 
> (forked) a custom version of common-httpclient inside so the interface which 
> should be implemented in the case of Maven is actually 
> org.apache.maven.wagon.providers.http.httpclient.client.HttpRequestRetryHandler.
>  
> The reason I dont submit a PR fixing this is that I am unsure whether this is 
> just an issue for how Maven uses wagon or if is an issue with wagon it self.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to