[
https://issues.apache.org/jira/browse/WAGON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024964#comment-17024964
]
Michael Osipov commented on WAGON-576:
--------------------------------------
OK, I see. The tests we have operate on the unmodified sources, thus are
useless in this special case. I am thinking whether we could use our own
interface which implement the problematic one. Though, this be a breaking
change, but this is still better then not usuable at all.
> 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)