Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
  b=jUvXsgccLd3mCmIdGvcZit4pkku2Tn7UEfp8F9Z4CW6uKdDf2msyi6zWOHosxKzEgNRjwhKU0PU20a/UfK83HqUMZMCEiQmtzR0jz7omuJatubyctmGyyktq6HXPWYcuPkUvCUjdT0aKkyqGVPHffXGJCtM1oSd2OGGvPM8PjrE=;
Date: Wed, 10 Oct 2007 14:56:22 -0700 (PDT)
From: Maarten Coene <maarten_coene@yahoo.com>
Subject: Re: problem with work files created in cache by ivy:resolve (ivy 1.4)
To: ivy-user@incubator.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-ID: <302313.46052.qm@web30802.mail.mud.yahoo.com>

Another solution which will be probably easier to implement than IVY-399 is=
 to split the cache in 2: 1 cache for the downloaded data and 1 cache for t=
he resolution results. If we make the location of both caches configurable =
by properties (e.g. ivy.cache and ivy.metadata.cache) you can easily config=
ure ivy for instance to put the metadata.cache in a subdirectory of your pr=
oject so you don't have conflicts when resolving multiple projects at the s=
ame time.=0A=0A--=0AMaarten=0A=0A----- Original Message ----=0AFrom: Xavier=
 Hanin <xavier.hanin@gmail.com>=0ATo: ivy-user@incubator.apache.org=0ASent:=
 Tuesday, October 9, 2007 7:19:57 AM=0ASubject: Re: problem with work files=
 created in cache by ivy:resolve (ivy 1.4)=0A=0A=0AIndeed, using a lock fil=
e can defeat the whole purpose of using a=0A single=0Acache. The main probl=
em is that we handle two different things in the=0A cache:=0Acache of downl=
oaded data (ivy files and artifacts), and cache of a=0A module=0Aresolution=
 results. The former is what is interesting to share and less=0A a=0Aproble=
m to lock, the latter is not really interesting to share and more=0A a=0Apr=
oblem to lock. Once again we see that the cache management in Ivy=0A needs=
=0Aimprovement, it's one other vote for IVY-399. But this could even=0A des=
erve a=0Anew issue: make Ivy able to use a repository cache shared by multi=
ple=0Aprocesses. Could you create such an issue?=0A=0AXavier=0A=0A=0A=0A=0A=
=0A       =0A______________________________________________________________=
______________________=0AYahoo! oneSearch: Finally, mobile search =0Athat g=
ives answers, not web links. =0Ahttp://mobile.yahoo.com/mobileweb/onesearch=
?refer=3D1ONXIC