You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/02/22 14:03:00 UTC

[jira] [Comment Edited] (WAGON-576) Retry handler docs are possibly wrong

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

Michael Osipov edited comment on WAGON-576 at 2/22/20 2:02 PM:
---------------------------------------------------------------

To solve your problem, you should dump the original Wagon HTTP into {{lib/ext}} and see if it works. If it does not, remove the shaded one. This should really work.


was (Author: michael-o):
To solve your problem, you should dump the original Wagon HTTP into {{lib/ext)} and see if it works. If it does not, remove the shaded one. This should really work.

> 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: Major
>
> 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)