配置Maven镜像仓库，国内Maven镜像仓库，Maven中央仓库，国内Maven仓库大全的配置笔记记录

前言

在以前博主每次遇到环境变更时，博主就要大费周折的去整理以下Maven项目的 settings.xml 配置文件，什么镜像地址啦，仓库地址啦等等，很是浪费时间，在这儿记录哈，以便下次直接复制粘贴即可，为什么非要花时间整理能，在以前博主还是一个新手的时候， settings.xml 中配置的镜像地址总是只有一个，现在博主的配置文件里是，能有多少个就有多少个，比如在某天的社区里，看到一个新的即稳定，又快速的地址，我会立刻的毫不犹豫的加入进去（当然这只是博主个人的经验总结和建议）。

Maven镜像仓库地址配置

1、到一个新的项目中环境中，首先需要配置Maven的本地地址（这儿主要说Maven）在 settings.xml 配置文件中找到 localRepository 节点，内容如下：

<localRepository>D:\Install_Applications\apache-maven-3.5.3\.m2\repository</localRepository>

2、配置 Maven 镜像地址，在 settings.xml 配置文件中找到 mirrors 配置节点，示例内容如下：

<mirrors>--><!-- 阿里云Maven镜像仓库 该仓库目前存在于北京市大兴区 --><mirror><id>alimaven</id><name>aliyun maven</name><url>http://maven.aliyun.com/nexus/content/groups/public/</url><mirrorOf>central</mirrorOf></mirror>
</mirrors>

3、配置 Maven 中央仓库地址，在 settings.xml 配置文件中找到配置节点，示例内容如下：

<profile><id>jdk‐1.8</id><activation><activeByDefault>true</activeByDefault> <jdk>1.8</jdk></activation><properties><maven.compiler.source>1.8</maven.compiler.source><maven.compiler.target>1.8</maven.compiler.target><maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion></properties><!-- dubbo 官方的解决方案 --><repositories><repository><id>sonatype-nexus-snapshots</id><url>https://oss.sonatype.org/content/repositories/snapshots</url><releases><enabled>false</enabled></releases><snapshots><enabled>true</enabled></snapshots></repository></repositories>
</profile>

4、settings.xml 配置文件示例内容如下（注：是基于apache-maven-3.5.3 版本的）：

<?xml version="1.0" encoding="UTF-8"?><!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License athttp://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
--><!--| This is the configuration file for Maven. It can be specified at two levels:||  1. User Level. This settings.xml file provides configuration for a single user,|                 and is normally provided in ${user.home}/.m2/settings.xml.||                 NOTE: This location can be overridden with the CLI option:||                 -s /path/to/user/settings.xml||  2. Global Level. This settings.xml file provides configuration for all Maven|                 users on a machine (assuming they're all using the same Maven|                 installation). It's normally provided in|                 ${maven.conf}/settings.xml.||                 NOTE: This location can be overridden with the CLI option:||                 -gs /path/to/global/settings.xml|| The sections in this sample file are intended to give you a running start at| getting the most out of your Maven installation. Where appropriate, the default| values (values used when the setting is not specified) are provided.||-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"><!-- localRepository| The path to the local repository maven will use to store artifacts.|| Default: ${user.home}/.m2/repository<localRepository>/path/to/local/repo</localRepository>--><localRepository>D:\Install_Applications\apache-maven-3.5.3\.m2\repository</localRepository><!-- interactiveMode| This will determine whether maven prompts you when it needs input. If set to false,| maven will use a sensible default value, perhaps based on some other setting, for| the parameter in question.|| Default: true<interactiveMode>true</interactiveMode>--><!-- offline| Determines whether maven should attempt to connect to the network when executing a build.| This will have an effect on artifact downloads, artifact deployment, and others.|| Default: false<offline>false</offline>--><!-- pluginGroups| This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.| when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers| "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.|--><pluginGroups><!-- pluginGroup| Specifies a further group identifier to use for plugin lookup.<pluginGroup>com.your.plugins</pluginGroup>--></pluginGroups><!-- proxies| This is a list of proxies which can be used on this machine to connect to the network.| Unless otherwise specified (by system property or command-line switch), the first proxy| specification in this list marked as active will be used.|--><proxies><!-- proxy| Specification for one proxy, to be used in connecting to the network.|<proxy><id>optional</id><active>true</active><protocol>http</protocol><username>proxyuser</username><password>proxypass</password><host>proxy.host.net</host><port>80</port><nonProxyHosts>local.net|some.host.com</nonProxyHosts></proxy>--></proxies><!-- servers| This is a list of authentication profiles, keyed by the server-id used within the system.| Authentication profiles can be used whenever maven must make a connection to a remote server.|--><servers><!-- server| Specifies the authentication information to use when connecting to a particular server, identified by| a unique name within the system (referred to by the 'id' attribute below).|| NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are|       used together.|<server><id>deploymentRepo</id><username>repouser</username><password>repopwd</password></server>--><!-- Another sample, using keys to authenticate.<server><id>siteServer</id><privateKey>/path/to/private/key</privateKey><passphrase>optional; leave empty if not used.</passphrase></server>--></servers><!-- mirrors| This is a list of mirrors to be used in downloading artifacts from remote repositories.|| It works like this: a POM may declare a repository to use in resolving certain artifacts.| However, this repository may have problems with heavy traffic at times, so people have mirrored| it to several places.|| That repository definition will have a unique id, so we can create a mirror reference for that| repository, to be used as an alternate download site. The mirror site will be the preferred| server for that repository.|--><mirrors><!-- mirror| Specifies a repository mirror site to use instead of a given repository. The repository that| this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used| for inheritance and direct lookup purposes, and must be unique across the set of mirrors.|<mirror><id>mirrorId</id><mirrorOf>repositoryId</mirrorOf><name>Human Readable Name for this Mirror.</name><url>http://my.repository.com/repo/path</url></mirror>--><!-- 阿里云Maven镜像仓库 该仓库目前存在于北京市大兴区 --><mirror><id>alimaven</id><name>aliyun maven</name><url>http://maven.aliyun.com/nexus/content/groups/public/</url><mirrorOf>central</mirrorOf></mirror><mirror><id>nexus-aliyun</id><mirrorOf>*</mirrorOf><name>Nexus aliyun</name><url>http://maven.aliyun.com/nexus/content/groups/public</url></mirror><!-- CN国内Maven镜像仓库 该仓库目前存在于浙江省杭州市 --><mirror><id>net-cn</id><mirrorOf>central</mirrorOf><name>Human Readable Name for this Mirror.</name><url>http://maven.net.cn/content/groups/public/</url></mirror><!-- 网易163Maven镜像仓库 该仓库目前存在于广东省广州市 --><mirror><id>nexus-163</id><mirrorOf>*</mirrorOf><name>Nexus 163</name><url>http://mirrors.163.com/maven/repository/maven-public/</url></mirror><!-- ibiblio地址是美国的，但是博主用起来感觉还是比较快的，而且还不用X墙的，非常nice --><mirror><id>ibiblio</id><name>Mirror from Maven ibiblio</name><url>http://mirrors.ibiblio.org/pub/mirrors/maven2/</url><mirrorOf>central</mirrorOf></mirror></mirrors><!-- profiles| This is a list of profiles which can be activated in a variety of ways, and which can modify| the build process. Profiles provided in the settings.xml are intended to provide local machine-| specific paths and repository locations which allow the build to work in the local environment.|| For example, if you have an integration testing plugin - like cactus - that needs to know where| your Tomcat instance is installed, you can provide a variable here such that the variable is| dereferenced during the build process to configure the cactus plugin.|| As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles| section of this document (settings.xml) - will be discussed later. Another way essentially| relies on the detection of a system property, either matching a particular value for the property,| or merely testing its existence. Profiles can also be activated by JDK version prefix, where a| value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.| Finally, the list of active profiles can be specified directly from the command line.|| NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact|       repositories, plugin repositories, and free-form properties to be used as configuration|       variables for plugins in the POM.||--><profiles><!-- profile| Specifies a set of introductions to the build process, to be activated using one or more of the| mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>| or the command line, profiles have to have an ID that is unique.|| An encouraged best practice for profile identification is to use a consistent naming convention| for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.| This will make it more intuitive to understand what the set of introduced profiles is attempting| to accomplish, particularly when you only have a list of profile id's for debug.|| This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.<profile><id>jdk-1.4</id><activation><jdk>1.4</jdk></activation><repositories><repository><id>jdk14</id><name>Repository for JDK 1.4 builds</name><url>http://www.myhost.com/maven/jdk14</url><layout>default</layout><snapshotPolicy>always</snapshotPolicy></repository></repositories></profile>--><profile><id>jdk‐1.8</id><activation><activeByDefault>true</activeByDefault> <jdk>1.8</jdk></activation><properties><maven.compiler.source>1.8</maven.compiler.source><maven.compiler.target>1.8</maven.compiler.target><maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion></properties><!-- dubbo 官方的解决方案 --><repositories><repository><id>sonatype-nexus-snapshots</id><url>https://oss.sonatype.org/content/repositories/snapshots</url><releases><enabled>false</enabled></releases><snapshots><enabled>true</enabled></snapshots></repository></repositories></profile><!--| Here is another profile, activated by the system property 'target-env' with a value of 'dev',| which provides a specific path to the Tomcat instance. To use this, your plugin configuration| might hypothetically look like:|| ...| <plugin>|   <groupId>org.myco.myplugins</groupId>|   <artifactId>myplugin</artifactId>||   <configuration>|     <tomcatLocation>${tomcatPath}</tomcatLocation>|   </configuration>| </plugin>| ...|| NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to|       anything, you could just leave off the <value/> inside the activation-property.|<profile><id>env-dev</id><activation><property><name>target-env</name><value>dev</value></property></activation><properties><tomcatPath>/path/to/tomcat/instance</tomcatPath></properties></profile>--></profiles><!-- activeProfiles| List of profiles that are active for all builds.|<activeProfiles><activeProfile>alwaysActiveProfile</activeProfile><activeProfile>anotherAlwaysActiveProfile</activeProfile></activeProfiles>-->
</settings>

好了，关于配置Maven镜像仓库，国内Maven镜像仓库，Maven中央仓库，国内Maven仓库大全的配置笔记记录就写到这儿了，如果还有什么疑问或遇到什么问题欢迎扫码提问，也可以给我留言哦，我会一一详细的解答的。
歇后语：“ 共同学习，共同进步 ”，也希望大家多多关注CSND的IT社区。

作者：	华仔
联系作者：	who.seek.me@java98k.vip
来源：	CSDN (Chinese Software Developer Network)
原文：	https://blog.csdn.net/Hello_World_QWP/article/details/85046483
版权声明：	本文为博主原创文章，请在转载时务必注明博文出处！

配置Maven镜像仓库，国内Maven镜像仓库，Maven中央仓库，国内Maven仓库大全的配置笔记记录相关推荐

配置Maven项目本地仓库和远程镜像
1.下载Maven资源登录官网下载,网址:https://maven.apache.org/download.cgi 2.解压压缩包注意:请单击右键解压,不要直接双击解压,且最好把解压文件夹放到除 ...
国内阿里Maven仓库镜像及自己收集镜像库
国内阿里Maven仓库镜像Maven配置文件Maven仓库速度快收集的仓库如下: <?xml version="1.0" encoding="UTF-8" ...
idea通过maven使用docker插件生成镜像并推送到harbor仓库
windows有2种方式获取docker环境,使用VM构建linux环境并安装docker,另一种是安装dockertoolbox,再通过bash的方式创建虚拟的docker环境(本文使用后者) 1. ...
开发常用镜像资源替换为国内开源镜像(yum,compose,maven,docker,android sdk,npm,国内开源镜像汇总)...
一.国内开源镜像站点汇总阿里云开源镜像站 (http://mirrors.aliyun.com/) 网易开源镜像站 (http://mirrors.163.com/) 中国科学技术大学开源镜像站 ( ...
超级详细：公网环境下登录 Docker 仓库： Docker Hub 或国内阿里镜像仓库！超级解惑！（推送镜像到docker hub 或国内阿里云镜像仓库）
文章目录前言: 1.登录 Docker Hub : ①.注册或登录 Docker Hub: ②.创建储存库: ③.开始上传镜像: ④.下载镜像: 2.使用国内阿里云镜像仓库: ①.开通容器 ...
Maven国内阿里镜像（Maven下载慢的解决方法）
Maven国内阿里镜像(Maven下载慢的解决方法) 参考文章: (1)Maven国内阿里镜像(Maven下载慢的解决方法) (2)https://www.cnblogs.com/xiongxx/p/ ...
Maven 的相关配置【源码下载、镜像源修改】
PS:网上相关配置很多,这里仅做自己的一个配置在线备份,所以比较简略. 1. Maven 配置下载源码和 JavaDoc 开发中,经常需要查看某个不太熟悉的类的源码,甚至是该类的 DOC 文档,在 ...
测试配置yum仓库的http镜像
测试配置yum仓库的http镜像一.基础环境 1.在tvm-base的基础上,复制一个镜像为tvm-yum来测试. 2.网络: eth0:host-only(用于虚拟内网,手动固定IP,这样从宿主机 ...
配置私有仓库(使用registry镜像搭建一个私有仓库)
在使用Docker一段时间后,往往会发现手头积累了大量的自定义镜像文件,这些文件通过公有仓库进行管理并不方便:另外有时候只是希望在内部用户之间进行分享,不希望暴露出去.这种情况下,就有必要搭建一个本地 ...

配置Maven镜像仓库，国内Maven镜像仓库，Maven中央仓库，国内Maven仓库大全的配置笔记记录

前言

Maven镜像仓库地址配置

配置Maven镜像仓库，国内Maven镜像仓库，Maven中央仓库，国内Maven仓库大全的配置笔记记录相关推荐

最新文章

热门文章