[
https://issues.apache.org/jira/browse/IVY-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549045
]
Xavier Hanin commented on IVY-321:
----------------------------------
I think this issue should be split into two separate issues:
- cache cleaning
- repository cleaning
Indeed the two are very different, for the cache removing stuff won't ever have
any other implication than impacting performance, while removing module
revisions from a repository is more complex if we want to help insure its
consistency (being sure we never remove a module revision on which other
modules depend).
So I'll create a new issue for repository cleaning, and rename this one in
cache cleaning.
> cache and repository cleaning
> -----------------------------
>
> Key: IVY-321
> URL: https://issues.apache.org/jira/browse/IVY-321
> Project: Ivy
> Issue Type: New Feature
> Reporter: Gilles Scokart
> Assignee: Xavier Hanin
>
> Ivy should provide some solution to manage the size of the cache (and of
> repositories). Ivy configuration should have some rules saying how long to
> keep versions of the jars in the cache. Theses rules could be parametrized
> in function of the module, of the type of revision, of the age of the files
> or depending of the last time it has been used, the existence of dependent
> modules, etc. (I let you choose the best solutions)
> The same kind of things should also exist for a reposiotry (mainly for
> continuous build repository).
> The cleaning might be performed automatically when a retrieve (for the cache)
> or a publish (for a repository) is performed, or might be invocable from a
> dedicated task.
> There is currently no easy way to perform similar cleaning.
> To illustrate this need, here is a mail I received from a developper who is
> using ivy since 1 day. He have wriiten an ant scripts launching some tests
> build by our continuous build.
> {quote}
> Gilles,
>
> The build file is working great, so thanks for that! It's a very easy way to
> distribute software to the testers (until now I had to send all the jars and
> update them manually etc)
>
> However, one minor issue: I've noticed that ivy keeps all version in its
> cache. After just a day of playing around with it I already got a cache of
> almost 100MB, so this will get out of control rather quickly. Is there a
> configuration option somewhere to limit the cache size? or to automatically
> delete older versions? Even if it just leaves the latest version I'm ok with
> that, although it might be neat to leave the last 3 or 5 or something.
>
> Peter
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
