ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin" <xavier.ha...@gmail.com>
Subject Re: Preventing remote repository access if artifact is already cached
Date Fri, 12 Jan 2007 17:03:46 GMT
On 1/12/07, Johan Stuyts <j.stuyts@javathinker.com> wrote:
>
> > Ok, so maybe it's related to IVY-207. I'm now wondering if IVY-207
> should
> > have been fixed or not. The problem was most specifically related to a
> > module for which an artifact was found with no module descriptor, then
> if
> > you add a module descriptor in your chain, it won't be found because Ivy
> > use
> > the cached version. But maybe this should be considered as normal, as
> > soon
> > as you don't use checkModified="true".
>
> Okay, I understand why this behavior is needed now.
>
> > What do you think?
>
> IMHO Ivy should not attempt to look for artifacts if they are already in
> the cache when 'checkModified' is set to 'false'.


It makes sense. Could you post an issue in JIRA?

- Xavier

Johan
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message