Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id DBF0D200CDD for ; Mon, 24 Jul 2017 06:03:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DA594163BF7; Mon, 24 Jul 2017 04:03:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2D175163BF3 for ; Mon, 24 Jul 2017 06:03:09 +0200 (CEST) Received: (qmail 51259 invoked by uid 500); 24 Jul 2017 04:03:08 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 51250 invoked by uid 99); 24 Jul 2017 04:03:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jul 2017 04:03:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id D857718041D for ; Mon, 24 Jul 2017 04:03:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id EGiFs-5lyOoi for ; Mon, 24 Jul 2017 04:03:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 177A55F341 for ; Mon, 24 Jul 2017 04:03:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DB17FE00A9 for ; Mon, 24 Jul 2017 04:03:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id D467221ED9 for ; Mon, 24 Jul 2017 04:03:01 +0000 (UTC) Date: Mon, 24 Jul 2017 04:03:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: notifications@ant.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IVY-735) Timeout should be able to be specified MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 24 Jul 2017 04:03:10 -0000 [ https://issues.apache.org/jira/browse/IVY-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097918#comment-16097918 ] ASF GitHub Bot commented on IVY-735: ------------------------------------ Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/54 I'd rather have dropping support for 2.x up for vote a.s.a.p. because 3.x is [EOL](http://hc.apache.org/httpclient-3.x/) already. > 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)