Hi Brian if diskspace was a concern i would concur but as each repository and their mirrors support terabyte capacity i would hold off on the purge i was bitten by a wizbang version maven plugin that wasnt tested with wizbank injector and failed when the maven-plugin's were injected using incorrect role and roleHint falling back one full version of this plugin saved my configuration and saved my local repository
WDYT? Martin ______________________________________________ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > From: [email protected] > To: [email protected] > Date: Fri, 29 Oct 2010 15:28:27 +0200 > Subject: RE: Request to re-open MNG-3472 > > 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. > > 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. > > -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] >
