Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 83860 invoked from network); 14 Mar 2008 09:47:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Mar 2008 09:47:26 -0000 Received: (qmail 58752 invoked by uid 500); 14 Mar 2008 09:47:23 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 58734 invoked by uid 500); 14 Mar 2008 09:47:23 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 58725 invoked by uid 99); 14 Mar 2008 09:47:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Mar 2008 02:47:23 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [84.14.163.131] (HELO trinity.anyware-tech.com) (84.14.163.131) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Mar 2008 09:46:46 +0000 Received: from localhost (localhost [127.0.0.1]) by trinity.anyware-tech.com (Postfix) with ESMTP id 99878400BEF for ; Fri, 14 Mar 2008 10:46:54 +0100 (CET) Received: from trinity.anyware-tech.com ([127.0.0.1]) by localhost (trinity.anyware-tech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11866-01 for ; Fri, 14 Mar 2008 10:46:44 +0100 (CET) Received: from almeda.anyware (almeda.anyware [10.0.3.16]) by trinity.anyware-tech.com (Postfix) with ESMTP id 0FB83400BCD for ; Fri, 14 Mar 2008 10:46:44 +0100 (CET) From: Nicolas =?iso-8859-1?q?Lalev=E9e?= Organization: Anyware Technologies To: ivy-user@ant.apache.org Subject: Re: Confusion/Questions Regarding Settings File in Beta 2 Date: Fri, 14 Mar 2008 10:46:55 +0100 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200803141046.55863.nicolas.lalevee@anyware-tech.com> X-Virus-Scanned: Debian amavisd-new at anyware-tech.com X-Virus-Checked: Checked by ClamAV on apache.org Le mercredi 12 mars 2008, Buck, Robert a =E9crit=A0: > Hi, > > I probably need my head realigned, but could you help me understand > something? > > I have the settings file below. And what I am doing is the following (or > so I think I am doing this): > > 1. Cache all HTTP downloads into the "download-cache". This is > accomplished by specifying "download-cache" on the "url" based resolver. > When I run the build, I confirm this indeed does work as I anticipated. > Good. > > 2. Define a "Local IVYREP" or sorts in the "ivy/ivyrep" directory. What > I anticipate using this for is for read-only retrievals in case I want > to test an upgrade of some library to a newer version, without impacting > anyone. (Problem, see below) > > 3. Specify to IVY where to put its resolution cache and repository > cache. > > Concerns/Problems: > > 1. The ivy publish commands seem to put the jars from my build in both > the "ivy/cache/repository" directory and the "ivy/ivyrep" directory. > Shuffling around copies of build artifacts is expensive. If I remember coreectly your cache will be populated as soon as there is a= =20 resolve. So the publish will populate your ivy/ivyrep. But on the next=20 resolve that will ask for artifacts in your ivyrep repo, the cache will be= =20 populated with them. Nicolas