It's essentially because of what you wrote below. You may want to be very diligent about backing up your release repo, but not so rigorous for snapshots. Snapshots tend to take up a lot more disk than releases because there are many copies of it when you use timestamps. This requires cleanup and metadata update at times. The less often you touch your release repo to start removing and changing things, the safer the data there is.
On Thu, Oct 22, 2009 at 4:43 AM, Costin Caraivan <[email protected]> wrote: > > Hello, > > I saw that most repositories are separated into releases and snapshots. And > that most repository managers recommend using releases and snapshots. > > Now, I know what each of them is: > 1. release -> stable version, will be uploaded only once, when you want to > change something you make a new release. > 2. snapshots -> development version, usually overwritten (you can keep > multiple snapshots, but it's not usually done) > > What are the benefits of having 2 separate repos? Cons & pros. Pros & cons > :) > -- > View this message in context: > http://www.nabble.com/Why-are-repositories-usually-separated-into-releases-and-snapshots--tp26006147p26006147.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
