Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Date: Sun, 25 Oct 2009 10:16:10 +0530
From: Sahoo <Sahoo@Sun.COM>
Subject: Re: Why are repositories usually separated into releases
 and	snapshots?
In-reply-to: <e18234670910241836ma63e934ydbc11acfbe8f3cc4@mail.gmail.com>
Sender: Sanjeeb.Sahoo@Sun.COM
To: Maven Users List <users@maven.apache.org>
Message-id: <4AE3D812.6090603@Sun.COM>
References: <26006147.post@talk.nabble.com>
 <e18234670910241836ma63e934ydbc11acfbe8f3cc4@mail.gmail.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)

Sometime back I had the exact question in my mind and QoS (what you 
mentioned as administration) and security were the only ones I could 
think of.

Thanks,
Sahoo

David Weintraub wrote:
> No one has answered the basic question: Why two repositories?
>
> I know the differences between a release and snapshot. but that doesn't
> explain why the releases and snapshots are in two separate repositories. Why
> not keep both snapshots and releases in the same repository. We know
> something is a snapshot simply because it has the word "SNAPSHOT" appended
> to it.
>
> Because of the dual repository structure, I have to configure everything
> with two separate repository names, two separate repository URLs, and two
> sets of accounts and passwords. So, why not simply have a single repository
> which can store both snapshots and releases?
>
> These are the only reasons I can think of:
>
> * Administration: Backing up a release repository is extremely important.
> Backing up snapshots -- not so much. But, is this actually true?
>
> * Who can see what. I might want my snapshot repository available to my
> developers, but not to the world. However, this would be more of something
> my repository management software should be able to do.
>
> * Releases should only be added to the release repository by a release
> manager, and not by any developer. However, snapshots would be added by
> developers. Again, this seems better handled via my repository management
> software.
>
> So, what is the reason to have two separate and distinct repositories for
> snapshots and for releases?
>
> On Thu, Oct 22, 2009 at 4:43 AM, Costin Caraivan <ccaraivan@axway.com>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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>     
>
>
>   

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org