On Oct 29, 2010, at 9:28 AM, <[email protected]> <[email protected]> wrote:
> I'm not suggesting that Maven periodically run a task to purge the repo. I'm > suggesting that a settable policy be implemented such that a max number of > versions of a snapshot artifact be kept in the local repo. When that limit is > exceeded, the oldest version is deleted. > It's essentially the same logic implemented in repository managers. > Yes, it's easy enough to do an rm -rf on your local repo. But that assumes > that you understand why you need to do this or have been told by your dev > team to do this and that you remember to do it before you realize that a lot > of disk space is being used up by something. > > IMHO, a tool should never have unbounded access to resources such as disk > space. Further, I don't think stakeholders (not all of which are developers) > should need to understand the inner working of Maven or what they need to do > work around a limitation such as this. > Given all our other concerns and that the issue has one vote, it's honestly not likely something we'll implement. But if you want to and contribute it take a look at how artifacts are installed with Aether, which is what Maven 3.x is using. We would need an extension mechanism for the installation process, and way to define those extensions in settings.xml, and then how you would configure that extension. > -brian > > > -----Original Message----- > From: ext Wendy Smoak [mailto:[email protected]] > Sent: Friday, October 29, 2010 8:43 AM > To: Maven Users List > Subject: Re: Request to re-open MNG-3472 > > 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] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- To do two things at once is to do neither. -—Publilius Syrus, Roman slave, first century B.C.
