ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Buck, Robert" <>
Subject RE: problem with work files created in cache by ivy:resolve (ivy 1.4)
Date Wed, 10 Oct 2007 22:40:59 GMT
Hi Maarten,

The one additional reason for IVY-399 is the publication of build
artifacts should not pollute the resolution results for third party
artifacts. Put another way, one ought to be able to have a local cache
of artifacts resolved from an IVREP, and have a workspace local
repository that is for resolved build artifacts only. So a simple split
would only partly solve the problem -- at least for those of us at

But I do agree with the concept of splitting out the meta-data. Having
it in a cache is a bad idea.


-----Original Message-----
From: Maarten Coene [] 
Sent: Wednesday, October 10, 2007 5:56 PM
Subject: Re: problem with work files created in cache by ivy:resolve
(ivy 1.4)

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 the resolution results. If we make the location of both caches
configurable by properties (e.g. ivy.cache and ivy.metadata.cache) you
can easily configure ivy for instance to put the metadata.cache in a
subdirectory of your project so you don't have conflicts when resolving
multiple projects at the same time.


----- Original Message ----
From: Xavier Hanin <>
Sent: Tuesday, October 9, 2007 7:19:57 AM
Subject: Re: problem with work files created in cache by ivy:resolve
(ivy 1.4)

Indeed, using a lock file can defeat the whole purpose of using a
single cache. The main problem is that we handle two different things in
cache of downloaded data (ivy files and artifacts), and cache of a
module resolution results. The former is what is interesting to share
and less  a problem to lock, the latter is not really interesting to
share and more  a problem to lock. Once again we see that the cache
management in Ivy  needs improvement, it's one other vote for IVY-399.
But this could even  deserve a new issue: make Ivy able to use a
repository cache shared by multiple processes. Could you create such an


Yahoo! oneSearch: Finally, mobile search that gives answers, not web

View raw message