Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 44221 invoked from network); 7 Apr 2008 14:07:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Apr 2008 14:07:43 -0000 Received: (qmail 32064 invoked by uid 500); 7 Apr 2008 14:07:43 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 32043 invoked by uid 500); 7 Apr 2008 14:07:43 -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 32034 invoked by uid 99); 7 Apr 2008 14:07:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Apr 2008 07:07:43 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xavier.hanin@gmail.com designates 209.85.200.173 as permitted sender) Received: from [209.85.200.173] (HELO wf-out-1314.google.com) (209.85.200.173) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Apr 2008 14:07:00 +0000 Received: by wf-out-1314.google.com with SMTP id 27so1495429wfd.10 for ; Mon, 07 Apr 2008 07:07:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=FCsCEIx69orN4kQesv/F06Sxaj8lAy/2R3PolHHOn9c=; b=bKmE9i3lJn+6NDyWAnwS9ageSNM14hDchE0deUBy4d5FVWb17KBI6HUcOPswo9WxMihTTno16dsUmBUboiL4vuwgFEeqa2KCdjMtJBzXwUQpqWOnFyRvbPjZot++VZdvkSKtZUf/rDs16dA81aLnK28vMkLuKQST8+dwXZgcJh0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=jev41QC2koBbhrh8Tgn5bKbZ3xr1CLiRw2QEMG7liufAiSW5F/38m1A3nBEphzQ5zTbu6gjV8Grh48KlDIvSWwJX8URhv4XWWEM2WwPYisxBN10xBCdPWcV6zFN/Q+t3MinO7wTl3S8aMq5qQhIWdr/Z1wWf7h+4EGkEMcCttB0= Received: by 10.142.126.17 with SMTP id y17mr2430981wfc.170.1207577232202; Mon, 07 Apr 2008 07:07:12 -0700 (PDT) Received: by 10.142.255.15 with HTTP; Mon, 7 Apr 2008 07:07:12 -0700 (PDT) Message-ID: <635a05060804070707teb782b3nd66a8349d02d6861@mail.gmail.com> Date: Mon, 7 Apr 2008 16:07:12 +0200 From: "Xavier Hanin" To: ivy-user@ant.apache.org Subject: Re: reusability of ivy cache In-Reply-To: <15412A37E8C9574393B24ADD991FAA7608CD605878@MERCMBX14.na.sas.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_23652_6451743.1207577232183" References: <15412A37E8C9574393B24ADD991FAA7608CD605878@MERCMBX14.na.sas.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_23652_6451743.1207577232183 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Mon, Apr 7, 2008 at 2:43 PM, Ernest Pasour wrote: > Hi, I am trying to attain maximum reusability of the artifacts in my Ivy > cache. I have multiple groups of projects, each group having its own ivy > repository chain. What I would like to do is point the repository cache at > a global location (i.e. ivy.cache.repository). Each group would point the > resolution cache (ivy.cache.resolution) at a group-specific location. So I > have something like this: > > Group A > ivy.cache.repository="global_cache" > ivy.cache.resolution="A" > > Group B > ivy.cache.repository="global_cache" > ivy.cache.resolution="B" > > Is this safe? This is safe if - you use the artifact-lock lock strategy for your repository cache: http://ant.apache.org/ivy/history/latest-milestone/configuration/lock-strategies.html - you don't have two processes using the same resolution cache concurrently Xavier > > > Thanks for any insight. > > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/ ------=_Part_23652_6451743.1207577232183--