What I do for my projects (or group of projects) is to place the cache
in the project directory structure. I found it to be the best way to
avoid caching issues.
That said, my preference would be to not bother for the 2.0 release,
and come in a 2.1 with a wonderfull cache managment.
Gilles
2007/6/21, Xavier Hanin <[EMAIL PROTECTED]>:
On 6/21/07, Maarten Coene <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I'm using Ivy 1.4 and Ivy 2.0 on the same machine. The caches of 1.4 and
> 2.0 are not compatible with each other, so I have to change the cache
> location for all my projects using Ivy 2.0 manually. Maybe we should
> change the default cache location of Ivy 2.0 to ${user.home}/.ivy2 ? This
> would allow the usage of both Ivy 1.4 and Ivy 2.0 on the same machine with
> the default settings...
Why not. But if we don't review our cache mangement before 2.0 (an donly in
2.1 for instance), this will mean that we may have similar problems between
2.0 and 2.1. And I wouldn't like to have yet another default directory name
for 2.1. So maybe we should re consider cache mangement review for 2.0? Or
forget about such distinction? Or simply consider using .ivy2.1 for
2.1version (if necessary due to cache structure change). Or maybe we
could find
a way to preserve compatibility of cache (by using different file names)?
WDYT?
Xavier
--
> Maarten
>
>
>
>
>
>
>
____________________________________________________________________________________
> Never miss an email again!
> Yahoo! Toolbar alerts you the instant new Mail arrives.
> http://tools.search.yahoo.com/toolbar/features/mail/
>
--
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
--
Gilles SCOKART
