rm -rf ~/.m2/repository No kidding, host a proxy like Nexus on your network and use that as a mirrored proxy. This has all kind of clean up tasks, like remove old snapshots, etc. And, because it is a local mirror, it has all the artifacts you need. And even in different repositories, like proxied central, hosted snapshots with cleanup policy, hosted releases with deploy once policy, hosted thirdparty repository. All cleanly seperated and easily backupped.
For staging builds you would need Nexus Professional, for all your other wishes the normal Nexus fits like a glove. Hth, Nick Stolwijk ~Senior Java Developer~ iPROFS Wagenweg 208 2012 NM Haarlem T +31 23 547 6369 F +31 23 547 6370 I www.iprofs.nl On Tue, Dec 28, 2010 at 6:47 PM, baz themail <bazthem...@gmail.com> wrote: > Hi, > > 1. What is the best and recommended way to limit the size of the local > maven repo? Currently, I am having a cron job to remove older > SNAPSHOT. > > 2. Is there any way to keep certain release builds but not others? > Meaning, is there any type of promotion mechanism in maven to mark > some releases in local repo? > > 3. Is there any way to stop the same version of pom file/build being > built more than once? > > Thanks. > > B. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
