它们分别归属于不同的组织或公司。下面是对这些镜像服务器归属的说明：
阿里云仓库 (alimaven)
公司: 阿里巴巴集团
描述: 阿里云提供的公共Maven仓库镜像服务。
Tencent (腾讯)
公司: 腾讯公司
描述: 腾讯提供的公共Maven仓库镜像服务。
网易 (163)
公司: 网易公司
描述: 网易提供的公共Maven仓库镜像服务。
华为 (huaweicloud)
公司: 华为技术有限公司
描述: 华为云提供的公共Maven仓库镜像服务。
中央仓库1 (repo1) 和 中央仓库2 (repo2)
公司: Maven Central Repository
描述: 这两个镜像是指向官方Maven Central Repository的两个不同的URL。
Apache Snapshots
公司: Apache Software Foundation
描述: Apache软件基金会提供的快照版本仓库。
SpringSource Repository (springsource-repos)
公司: Pivotal Software, Inc. (现在是VMware的一部分)
描述: Spring框架相关的发布仓库。
Activiti Repository (activiti-repos)
公司: Alfresco Software, Inc.
描述: Activiti工作流引擎相关组件的仓库。
JCenter (jcenter)
公司: Bintray (曾经属于JFrog)
描述: 一个非常流行的第三方开源组件仓库，现已宣布退役计划。
ThinkGem Repository 2 (thinkgem-repos2)
公司: ThinkGem (个人或小团队维护)
描述: 个人或小型团队维护的仓库，位于GitHub上。
Java Repository (java-repos)
公司: Oracle Corporation
描述: Oracle提供的Java相关项目的仓库。
ThinkGem Repository (thinkgem-repos)
公司: ThinkGem (个人或小团队维护)
描述: 与上述ThinkGem Repository 2类似，也是由个人或小型团队维护的仓库，位于OSChina上。
Oschina Releases (oschina-repos)
公司: OSChina (开源中国)
描述: 开源中国提供的公共Maven仓库镜像服务。
这些镜像服务器通常用于加速Maven项目的构建过程，尤其是在中国大陆地区，由于网络原因，使用国内镜像可以显著提高构建速度。需要注意的是，某些镜像服务器可能需要通过代理才能访问。
<?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 at
http://www.apache.org/licenses/LICENSE-2.0
Unless 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>C:/Users/Tiger/.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>
-->
<!-- 阿里云仓库 -->
<mirror>
<mirrorOf>central</mirrorOf>
<id>alimaven</id>
<name>aliyun maven</name>
<url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
</mirror>
<!-- Tencent(腾讯) -->
<mirror>
<mirrorOf>central</mirrorOf>
<id>tencent</id>
<name>tencent</name>
<url>http://mirrors.cloud.tencent.com/nexus/repository/maven-public/</url>
</mirror>
<!-- 网易 -->
<mirror>
<mirrorOf>central</mirrorOf>
<id>163</id>
<name>163</name>
<url>http://mirrors.163.com/maven/repository/maven-public/</url>
</mirror>
<!-- 华为 -->
<mirror>
<mirrorOf>central</mirrorOf>
<id>huaweicloud</id>
<name>huaweicloud</name>
<url>https://mirrors.huaweicloud.com/repository/maven/</url>
</mirror>
<!-- 清华大学 1 -->
<mirror>
<mirrorOf>central</mirrorOf>
<id>nju-maven</id>
<name>Nanjing University Maven Repository</name>
<url>http://maven.nju.edu.cn/repository/</url>
</mirror>
<!-- 清华大学 2 -->
<mirror>
<mirrorOf>central</mirrorOf>
<id>tuna-maven</id>
<name>Tsinghua University Maven Repository</name>
<url>https://mirrors.tuna.tsinghua.edu.cn/maven/</url>
</mirror>
<!-- OSChina (开源中国) -->
<mirror>
<mirrorOf>central</mirrorOf>
<id>oschina-repos</id>
<name>Oschina Releases</name>
<url>http://maven.oschina.net/content/groups/public</url>
</mirror>
<!-- Maven Central Repository 中央仓库1 -->
<mirror>
<mirrorOf>central</mirrorOf>
<id>repo1</id>
<name>Human Readable Name for this Mirror.</name>
<url>http://repo1.maven.org/maven2/</url>
</mirror>
<!-- Maven Central Repository 中央仓库2 -->
<mirror>
<mirrorOf>central</mirrorOf>
<id>repo2</id>
<name>Human Readable Name for this Mirror.</name>
<url>http://repo2.maven.org/maven2/</url>
</mirror>
<!-- Apache软件基金会 Apache Apache 仓库-->
<mirror>
<mirrorOf>central</mirrorOf>
<id>apache-snapshots</id>
<name>Apache Snapshots</name>
<url>https://repository.apache.org/snapshots/</url>
</mirror>
<!-- Spring框架相关 spring.io 中央仓库-->
<mirror>
<mirrorOf>central</mirrorOf>
<id>springsource-repos</id>
<name>SpringSource Repository</name>
<url>http://repo.spring.io/release/</url>
</mirror>
<!-- Oracle提供的Java相关项目 java.net 中央仓库（需要 x 墙哟）-->
<mirror>
<mirrorOf>central</mirrorOf>
<id>java-repos</id>
<name>Java Repository</name>
<url>http://download.java.net/maven/2/</url>
</mirror>
<!-- Alfresco Software, Inc. Activiti工作流引擎alfresco.com -->
<mirror>
<mirrorOf>central</mirrorOf>
<id>activiti-repos</id>
<name>Activiti Repository</name>
<url>https://maven.alfresco.com/nexus/content/groups/public</url>
</mirror>
<!-- Bintray (曾经属于JFrog) 一个非常流行的第三方开源组件仓库，现已宣布退役计划 JCenter Repository 仓库-->
<mirror>
<mirrorOf>central</mirrorOf>
<id>jcenter</id>
<name>JCenter</name>
<url>https://jcenter.bintray.com/</url>
</mirror>
<!-- ThinkGem 个人或小型团队维护的仓库github.com （需要 x 墙哟）-->
<mirror>
<mirrorOf>central</mirrorOf>
<id>thinkgem-repos2</id>
<name>ThinkGem Repository 2</name>
<url>https://raw.github.com/thinkgem/repository/master</url>
</mirror>
<!-- ThinkGem2 个人或小型团队维护的仓库github.com （需要 x 墙哟）-->
<mirror>
<mirrorOf>central</mirrorOf>
<id>thinkgem-repos</id>
<name>ThinkGem Repository</name>
<url>http://git.oschina.net/thinkgem/repos/raw/master</url>
</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>
-->
<!--
| 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>