On 02/11/2010 1:20 PM, Haszlakiewicz, Eric wrote:
-----Original Message-----
From: Martin Gainty [mailto:[email protected]]
Sent: Friday, October 29, 2010 1:14 PM
To: [email protected]
Subject: RE: Request to re-open MNG-3472
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
What in the world are you talking about? How can you claim that everyone's has
the capability and the money to buy terabytes of disk space, especially for
everyone's local repositories?
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.
This is even more of a problem when you have dozens of people performing builds on a variety of
shared machines. It seems like many people don't realize that not everyone limits their use of
maven to personal PCs with huge disks. When you have several people working on the same system
"oh, it's just a few GB" quickly ends up turning into "out of disk space".
The guys with small disk can just delete their entire local repo and let
maven rebuild it by itself from your central server which should have
lots of space.
One or two builds usually gets us back to a fast build from localhost.
If your central server is short of space spend $100 and add a terabyte or 2.
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
I definitely agree with this. It's hard enough to get people to clean up the
files that the explicitly create.
eric
---------------------------------------------------------------------
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]
