Hi folks, in regards to deleting snapshots; how can you really delete snapshots? If you release an artifact with a resolved snapshot dependency (changed from SNAPSHOT to a timestamp - I do this when I release an artifact with a SNAPSHOT dependency to make the release reproducable at a later point in time), you will break backwards repoducability. This is a problem where I work; you can never be sure what timestamped snapshots one can delete, because its hard to determine which ones are actually used in a previous release. How do you other folks handle this situation?
Best regards, Bent On Wed, 8 Dec 2004 15:07:59 -0500, STRAYER, JON (SBCSI) <[EMAIL PROTECTED]> wrote: > About once a month I go in and delete all the timestamped snapshots from > the previous month. > > > > > -----Original Message----- > > From: Bert Lamb [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, December 08, 2004 3:04 PM > > To: STRAYER, JON (SBCSI) > > Cc: Maven Users List > > Subject: Re: Snapshot etiquette > > > > > > With this approach when do you clean up the timestamped snapshots? > > > > -Bert > > > > > > On Wed, 8 Dec 2004 14:40:04 -0500, STRAYER, JON (SBCSI) > > <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Ok, so I'm trying to get a handle on the "right" way to > > do snapshot > > > > dependencies during development and the perform a "release." In > > > > reading around the Internet it looks like there are two different > > > > approaches to snapshots.. > > > > > > > > Approach 1: > > > > > > > > In your POM define your version as "SNAPSHOT", and use > > jar:deploy to > > > > put your artifact myproj-SNAPSHOT.jar out on the repository. > > > > > > > > When it comes time to release then you change your > > version to your > > > > "real" version and then run that one build as your > > release build and > > > > put myproj-1.0.jar out on the repository. > > > > > > > > Approach 2: > > > > > > > > In your POM define your version as the real version that is > > > > currently in development but use jar:deploy-snapshot to put the > > > > artifact in the repository (it also puts a timestamped > > version there > > > > as well). > > > > > > > > When it comes time to release then you use jar:deploy for that > > > > "release build". > > > > > > > > Do I have these two approaches right? Which one is the > > "right" one? > > > > Is there a best practice documented somewhere? > > > > > > I use #2, but I don't have the status to claim it's the > > right method. > > > > > > > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
