Return-Path: 
 <ivy-user-return-50-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org
Received: (qmail 91532 invoked from network); 21 Nov 2006 10:22:38 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 21 Nov 2006 10:22:38 -0000
Received: (qmail 9796 invoked by uid 500); 21 Nov 2006 10:22:48 -0000
Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org
Received: (qmail 9767 invoked by uid 500); 21 Nov 2006 10:22:48 -0000
Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@incubator.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@incubator.apache.org>
List-Post: <mailto:ivy-user@incubator.apache.org>
List-Id: <ivy-user.incubator.apache.org>
Reply-To: ivy-user@incubator.apache.org
Delivered-To: mailing list ivy-user@incubator.apache.org
Received: (qmail 9757 invoked by uid 99); 21 Nov 2006 10:22:48 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Nov 2006 02:22:48 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Received: from [192.6.10.60] (HELO tobor.hpl.hp.com) (192.6.10.60)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Nov 2006 02:22:34 -0800
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tobor.hpl.hp.com (Postfix) with ESMTP id EC4524C07C
	for <ivy-user@incubator.apache.org>; Tue, 21 Nov 2006 10:22:11 +0000 (GMT)
X-Virus-Scanned: amavisd-new at hplb.hpl.hp.com
Received: from tobor.hpl.hp.com ([127.0.0.1])
	by localhost (tobor.hpl.hp.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id YjzGD0yLlEAt for <ivy-user@incubator.apache.org>;
	Tue, 21 Nov 2006 10:22:10 +0000 (GMT)
Received: from ha-node-br1.hpl.hp.com (ha-node-br1.hpl.hp.com [16.25.144.56])
	by tobor.hpl.hp.com (Postfix) with ESMTP id 87D394C068
	for <ivy-user@incubator.apache.org>; Tue, 21 Nov 2006 10:22:10 +0000 (GMT)
Received: from [16.25.171.182] (chamonix.hpl.hp.com [16.25.171.182])
	by ha-node-br1.hpl.hp.com (8.13.4/8.13.4) with ESMTP id kALALnCE013909
	for <ivy-user@incubator.apache.org>; Tue, 21 Nov 2006 10:21:50 GMT
Message-ID: <4562D214.2060703@apache.org>
Date: Tue, 21 Nov 2006 10:16:52 +0000
From: Steve Loughran <stevel@apache.org>
User-Agent: Thunderbird 1.5.0.8 (X11/20061025)
MIME-Version: 1.0
To: ivy-user@incubator.apache.org
Subject: Re: ivy:configure from url
References: <ed0c429e0611201052gf17851cg8e5651562be712a4@mail.gmail.com>
In-Reply-To: <ed0c429e0611201052gf17851cg8e5651562be712a4@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-HPL-MailScanner-Information: Please contact the ISP for more information
X-HPL-MailScanner: Found to be clean
X-HPL-MailScanner-From: stevel@apache.org
X-Virus-Checked: Checked by ClamAV on apache.org

Eric Crahen wrote:
> JIRA isn't available yet, so I'll mention this here.
> 
> ivy:configure from a url is very handy, especially when you have a
> non-trivial configuration you want many projects to share. One disadvantage
> to configuring from a url is that development is halted when the url is
> unavailable. That can happen for a number of reasons. I wonder if it would
> be possible to cache the configuration much the same as artifacts are 
> cached
> to allow local development to proceed while a remote service is 
> unavailable?
> 

Have you thought of using an Ant <get> to store the thing locally, then 
running Ivy:configure against that? <get> can check update times so only 
download files if they are newer