Hi barrie, After reading your post, I beg to differ on the need to lock down the repository.
Locking down your repository has nothing to do with _not_ trusting your developers. The reason you lock down your repository is to avoid any "unintentional" library conflicts that may arise when you have multiple projects using the same repository. A single developer will not be preview to all the dependency matrix (especially the new graduates) and avoids any accidental library conflicts that may arise due to a new core library being installed. Thanks Lakshman > -----Original Message----- > From: Barrie Treloar [mailto:[EMAIL PROTECTED] > Sent: Monday, 18 September 2006 11:02 AM > To: Maven Users List > Subject: Re: [M2] Managing Repositories > > On 9/17/06, Andreas Guther <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I am struggling with the question on how to maintain a controlled > > internal repository with Maven 2. > > > > We want to have full control over the downloaded dependencies and > > configured Maven to use as central repository our internal repository > > server. With this configuration no external repository is used. > > I will link to my response to a similar query. > http://www.nabble.com/forum/ViewPost.jtp?post=6087922&framed=y > > Essentially I question the need for a locked down repository. > About the only time I can see a need for this is because of security > restrictions on network connections (i.e. defence with a secure and > insecure network, as the secure network can not connect to ibiblio). > Any other reason is just making busy work and adds no value. > > --------------------------------------------------------------------- > 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]
