[
https://issues.apache.org/jira/browse/WAGON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed WAGON-576.
--------------------------------
Resolution: Fixed
Fixed with
[067f7e615ee081bf5106d1b9321844ad90352e6e|https://gitbox.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=067f7e615ee081bf5106d1b9321844ad90352e6e].
> 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
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
