Very interesting discussion. We have been having some of the exact same
discussions.

A lot of it comes down to what one defines as a team. Is a team a
collection of 3 developers working on a very specific part of a larger
system? Or, on the complete other side of the spectrum, is it 100
developers working on the entire system?

I don't think there is a cut and dry answer.  We have made our public
group contain all our internal snapshot and released artifact and give
the teams the choice whether or not they should point to another teams
snapshots or released artifacts. Using snapshot can really foster a more
agile environment and really help improve feature and bug fix turnaround
time. Particularly on larger projects. There are cons of course too but
I feel the pros tends to win out.

Of course we still have some teams who don't use snapshots at all. The
concept of a maven snapshot is very new to many and can be a bit
difficult to get ones head around.

---
Todd Thiessen
 

> -----Original Message-----
> From: Brian Fox [mailto:bri...@infinity.nu] 
> Sent: Thursday, October 22, 2009 1:18 PM
> To: Maven Users List
> Subject: Re: Why are repositories usually separated into 
> releases and snapshots?
> 
> On Thu, Oct 22, 2009 at 9:45 AM, Martin Gainty 
> <mgai...@hotmail.com> wrote:
> >
> > a snapshot usually has no guarantee of passing any sort of 
> test....its 
> > a way for a programmer/developer to prove that the 
> developer assigned 
> > has done *something*..but the snapshot carries no guarantee 
> has passed 
> > completely thru the SDLC validation lifecycle
> >
> > a release carries much more weight..basically
> >
> 
> Right, I tend to forget that aspect, it's just natural to me. 
> It's also recommended that you use snapshot for intra-team 
> dependencies, but use releases for inter-team dependences. 
> Take an OSS model for example, we try to avoid picking up 
> snapshot dependencies of other oss projects we depend upon in 
> Maven. We typically wait for a release before updating. If 
> you aren't careful and you've mixed releases and snapshots 
> together in the same repo, then it's difficult to give people 
> access to one without the other.
> 
> ---------------------------------------------------------------------
> 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

Reply via email to