[
https://issues.apache.org/jira/browse/IVY-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097516#comment-16097516
]
ASF GitHub Bot commented on IVY-735:
------------------------------------
Github user jaikiran commented on the issue:
https://github.com/apache/ant-ivy/pull/54
Gintas, thanks for pointing me to that code. I now understand what you
meant.
So essentially, Ivy internally tries to support both 2.x and 3.x version of
HTTP client library at runtime. But at compile time we depend on 3.x version
now. So it's not going to work out supporting 2.x version since we will end up
using 3.x APIs at compile time. But that's a different topic altogether and
something that I will raise a dev list mailing thread.
In the context of this feature/change, what I have now done is - updated
the commit to use the HTTP client 2.x APIs to set these timeouts. These APIs
have been deprecated in 3.x but should work in both 2.x and 3.x (at least 3.1,
the version we are currently using). Once/if we come to a consensus of just
supporting 3.x, I will update the code in separate commits to use the newer
APIs that are available in 3.x
> Timeout should be able to be specified
> --------------------------------------
>
> Key: IVY-735
> URL: https://issues.apache.org/jira/browse/IVY-735
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0.0-beta-1
> Reporter: Testo Nakada
> Assignee: jaikiran pai
> Attachments: 0001-Add-timeout-support-for-HTTP-requests.patch
>
>
> It's currently not possible to provide timeout for resolver. For example,
> yesterday ibiblio is really slow. I waited almost forever just to know that
> there is something wrong with ibiblio. It would be nice if I can specify
> timeout so that i can fail over to some other resolvers in my chain resolver.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
