On Fri, Oct 29, 2010 at 8:26 AM, <[email protected]> wrote: > Is it each > developer's responsibility to understand the details of how snapshot > artifacts are managed in the local repository and periodically clean up after > Maven? I don't think so. It seems like the best solution here is to allow > a retention policy to be defined in the settings.xml including a default > value which is fairly small.
(This would better be addressed to the dev list, unless you're just trying to gather support/votes for it from other users.) But how would you expect this to work? Maven is a command line tool, there is nothing sitting there able to run on a schedule to do this purge. First build of the day maybe? That's when it (by default) goes off checking for snapshot updates. Given that it's dead easy to just "rm -rf /path/to/local/repo" occasionally, (and re-download everything from you internal (or even localhost) repository manager) I don't see the devs putting much time into this one. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
