> 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 artifact? 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 >