Xavier Hanin wrote:
[...]
IvyFileInCache, ArchiveFileInCache, CachedDataFile
For the moment ArchiveFileInCache already supports a mechanism to
avoid copying it to the cache, called use origin. This mechanism
relies on the original location of the artifact which is stored in the
CachedDataFile. But this mechanism is not flexible enough, and not as
clean as what is suggested in IVY-399. Therefore I think we have to
review this mechanism as part of IVY-399.
+1 too much duplication in this artifact origin.
All this information should be maintained in every artifact (source,
lastmodified) metadata when 'resolved'.
[...]Hence I see another
solution: make BasicResolver delegate all its cache related operation
to a class implementing an interface we will have to define, but which
could be called ResolverCacheManager. Then we would have an
implementation called ResolverNoCacheManager, which would simply do no
cache management at all.
What operations are in a ResolverCacheManager ? can you elaborate ?
I have a hard time seeing the difference with a cache and nullcache.
[...]
With such a change, one thing that wouldn't make sense any more is the
saved resolver and artifact resolver, so the only information we would
have in CachedDataFile would be artifact origin (for resolvers using a
cache)
mmm ? Well the artifact data and artifact information are intended to
cached.
The source (ie origin) should be part of the metadata (ie attributes) of
the artifact and follow it all the time.
-- stephane.
