You can have multiple groups (but I have never seen hundreds or thousands in 
use). In our case we have virtual repos only based on the product status and a 
separate virtual one for build time (plugin) dependencies.

Btw one more reason for using different settings if you work on projects with 
different repositories is also the local repository cache. While it does 
remeber where an artifact has come from, it does not cleanly isolate repos

So when you build something which should not use a specific repo it might still 
discover the artifacts. So when you set up different settings (one for company, 
one for open source) do not only specify different repos and mirrors, but also 
a different local path.


Von: Robert Patrick
Gesendet: Dienstag, 18. Oktober 2016 15:57
An: Maven Users List
Betreff: RE: Comparing specifying repositories in pom vs. settings.xml?

But in a large corporate environment, the centralized repository manager can 
house hundreds/thousands of repositories so unless you want to virtualize the 
entire set of repositories (which tends to make the repository manager slower), 
you still need to specify the repositories to search, right? 

-----Original Message-----
From: Curtis Rueden [mailto:ctrue...@wisc.edu] 
Sent: Tuesday, October 18, 2016 8:14 AM
To: Maven Users List
Subject: Re: Comparing specifying repositories in pom vs. settings.xml?

> I'm trying, without success, to imagine why you do not simply 
> accumulate <server> elements as required.

Wouldn't that cause Maven to ping every server sequentially for every needed 

Better to set up a Maven repository manager (Nexus, Artifactory, etc.) and 
proxy all the needed sources, no? Then your settings.xml is always constant, 
pointing at your master Nexus, which groups all your needed repositories. Your 
build is reproducible and remains resilient to otherwise disruptive remote 
repository changes -- as long as your master Nexus does not change.

On Tue, Oct 18, 2016 at 8:03 AM, Mark H. Wood <mw...@iupui.edu> wrote:

> On Mon, Oct 17, 2016 at 08:03:03PM +0000, KARR, DAVID wrote:
> > One thing I run into when jumping between different projects is
> different expectations for what maven repos I need to be using.  In 
> the past, I had to have multiple copies of "~/.m2/settings.xml" lying 
> around, and I would hack the specified repos when I needed to.
> I'm trying, without success, to imagine why you do not simply 
> accumulate <server> elements as required.  Before long you should 
> reach a state in which new additions are extremely rare.
> --
> Mark H. Wood
> Lead Technology Analyst
> University Library
> Indiana University - Purdue University Indianapolis
> 755 W. Michigan Street
> Indianapolis, IN 46202
> 317-274-0749
> www.ulib.iupui.edu

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

Reply via email to