Our experience is that the not-central repos aren't reliable over the medium term. So, if we can't get it to go to central, we copy it into our own copy of Nexus. This is, of course, not a helpful strategy for anything that has to be maintained 'out in the open'.
On Wed, Oct 19, 2016 at 11:16 AM, KARR, DAVID <dk0...@att.com> wrote: >> -----Original Message----- >> From: Mark H. Wood [mailto:mw...@iupui.edu] >> Sent: Wednesday, October 19, 2016 5:55 AM >> To: users@maven.apache.org >> Subject: Re: Comparing specifying repositories in pom vs. settings.xml? >> >> OK, I'm going to learn a lot from this thread. >> >> On Tue, Oct 18, 2016 at 06:57:42AM -0700, Robert Patrick wrote: >> > 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? >> >> We have a local Nexus instance, and besides a mirror of Central and a >> couple of others, there are just two non-mirror repositories: >> local-snapshots and local-releases. Why would you have more than these? > > Our "Nexus instance" maintains artifacts for a very large number of projects, > most of which are managed by different teams that prefer, and often require > (by NDA, et cetera), to keep their artifacts separate from the artifacts from > other projects. It's not unusual for some people to work on different sets > of projects, requiring different sets of repositories. > > > --------------------------------------------------------------------- > 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
