On 4/11/07, Gilles Scokart <[EMAIL PROTECTED]> wrote:
Hi,
Hi, I read on the user mailing list that the caching mechanism will be reviewed
in 2.0. Did I read correctly?
Yes, you did. What is your idea for that? Nothing really more than what is already explained on the issue. At first I was thinking that it would be necessary to have such flexible cache management to implement a maven 2 resolver: i.e. a resolver using both the local and remote maven repositories, which could use the maven 2 local repository as a cache. I also like the idea behind flexible cache management: to be able to have separated caches per resolver, to use cache or not for some resolvers, ... There's quite a lot of work because for the moment cache management is spread across several classes, but code will be cleaner and Ivy more flexible after this review. And since it is the most voted issue, I thought it was a good idea to plan it for 2.0. NB: The concerned jira issues are still not 'planned' for 2.0. You're right, I thought I did it, but it seems we haven't really reached consensus on that yet. Maybe you have opinion or feedback to give about planning this feature for 2.0 or not? - Xavier Gilles
-- Learn Ivy at ApacheCon: http://www.eu.apachecon.com/ Manage your dependencies with Ivy! http://incubator.apache.org/ivy/
