Nexus has a Purge Snapshots job you can schedule. It is pretty flexible. You can decide how many snapshots you wish to keep around. Ideally, you should normally only need the latest, but on the rare occasion you may want to point to an older one. In our environment, the job runs every night and only leaves the last 2 snapshots. Although we are now considering only keeping the latest since I don't think anyone has ever wanted to point to the second latest.
--- Todd Thiessen > -----Original Message----- > From: Neil Chaudhuri [mailto:nchaudh...@potomacfusion.com] > Sent: Friday, November 13, 2009 12:21 PM > To: users@maven.apache.org > Subject: Snapshot Deployment Best Practices > > I have figured out how to deploy all my artifacts to my local > Nexus repository, and I have even set up my CI tool (TeamCity > in my case) to deploy the snapshot artifacts every night. > > Because I am not at the release stage yet, I have just been > deploying snapshot after snapshot. This means that my > snapshot page on Nexus for this artifact is getting loaded > with entries down the page. > > My questions relate to the "best practices" associated with > this sort of practice: > > *Is it OK and desirable to "build up" artifacts between releases? > *If not, is there a way to replace the previous snapshot > artifacts with the latest ones? > *Are there any steps I am missing? > > Thanks for your insight. > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
