Laird, any environment with multiple developers and multiple repositories is Exhibit 1 for using a repository manager like Nexus.
Once you have that running, one proxies remote repositories from central administration, not rely on users having the latest information or some combination of the latest information. Developers do need to have a reference to the repository you set up, how that's configured (either as a replacement for central or as an additional repository) IMHO depends a lot on who you have working on the project. If everyone is using machines that are owned by the company (meaning they are not a bunch of contractors that may have other projects going on), setting up their machines to treat your repository as central makes a lot the most sense. If you do have such contractors, it's presumed you only have them because they are A-team players that can manage their own settings.xml with aplomb. Brian On Oct 22, 2012, at 5:37 PM, Laird Nelson <ljnel...@gmail.com> wrote: > I know that it is a Bad Thing to add a repository to your pom.xml. > > Is it regarded by the Great Maven Hivemind :-) to be a Bad Thing if you put > a repository in your pom.xml as an (unactivated by default) profile? > > I'm sick and tired of having to tell users to put repository X or > repository Y in their .m2/settings.xml file; the whole point of the pom.xml > is: download the stuff, tell Maven to build it. :-) > > Best, > Laird > > -- > http://about.me/lairdnelson --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
