maven下载安装配置
1.下载
进入maven官网，https://maven.apache.org/,
点击左侧Download，进入下载页面
点击Other Releases下的 Maven 3 archives或legacy archives，可以查看历史版本。
选择download页面最新版Files标签下的Binary zip archive行的Link列，即apache-maven-3.9.9-bin.zip，Windows环境下选择bin.zip,linux环境下选择bin.tar.gz.
点击下载，保存压缩包
2.安装
把下载的压缩包，拷贝到待安装目录，解压到当前文件夹，删除压缩包。
注意：
凡是解压缩前。先用软件看下压缩包内是否是所有内容都在一个目录下，符合预期再解压。若压缩包直接就是散乱的文件，那么很可能会导致文件夹层级混乱，想删除加压好的文件再新建目录然后解压也会很麻烦。
如果拿不准，那么久自行建一个单独目录，解压进去，如果多了一个层级，那么就全量拷贝内层内容到外层，然后删除建立的空文件夹即可。
拷贝到目录：E:\Program Files，
我通过7z打开压缩包，发现是所有内容都在一个目录下
直接解压到当前目录，
删除压缩包。
3.配置
maven需要有对应的Java环境，首先保证java环境已配好
若在idea中使用maven，idea中自带maven，调整设置和仓库即可。
配置maven环境变量后，才可以在命令行使用。一般单独安装配置下，不用idea自带的。
配置win10的maven环境
右键桌面的此电脑，点击属性，点击高级系统设置，点击环境变量，点击新建
变量名：MAVEN_HOME
变量值：E:\Program Files\apache-maven-3.9.9
再双击Path,点击新增
%MAVEN_HOME%\bin
点击确定或应用，直到退出所有页面，才会保存生效。
测试环境是否安装好：win+r，输入cmd,回车，输入mvn -v, 正常显示。
配置idea的maven环境
打开idea，
ctrl+alt+s打开设置，
打开构建、执行、部署，
点击构建工具，
点击Maven,
maven主路径设置已安装的maven路径
用户设置文件设置maven安装目录下conf/settings.xml，一般在项目中配置文件可能有多个，名称加上项目后缀即可，有一份能跑起来的配置，要一份过来就行。
本地仓库设置E:\maven-repository（不要放C盘，名称最好明确，比如maven-repository或者项目名-maven-repository，软件目录一般不要出现中文或空格，白给自己找麻烦）
配置maven的配置文件settings.xml
在conf目录下，给自己留一个原版的settings.xml文件，里面未修改过任何属性，命名settings-原版.xml
可以拷贝以下翻译后的一份配置文件，简单参考，命名settings-翻译.xml
留一份项目通用的配置文件，命名settings-通用.xml
其他单独或临时用于某个项目，命名settings-项目名.xml
仅供参考。
翻译的配置文件
<?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.
根据一个或多个贡献者许可协议授权给Apache软件基金会（ASF）。有关版权所有权的更多信息，请参阅随本作品分发的通知文件。ASF根据Apache许可证2.0版（
“许可证”）；除非遵守许可证，否则您不得使用此文件。您可以在以下网址获得许可证副本
http://www.apache.org/licenses/LICENSE-2.0
除非适用法律要求或书面同意，否则根据许可证分发的软件将在
“现状”基础，不作任何明示或暗示的保证或条件。有关许可证下管理权限和限制的具体语言，请参阅许可证。
-->
<!--
| 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.
|
| 这是Maven的配置文件。它可以在两个级别上指定：
|
1.用户级别。此settings.xml文件为单个用户提供配置，
|并且通常在${user.home}/.m2/settings.xml中提供。
|
|注意：此位置可以用CLI选项覆盖：
|
|-s/path/to/user/settings.xml
|
2.全局层面。此settings.xml文件为所有Maven提供配置
|机器上的用户（假设他们都使用相同的Maven
|安装）。它通常在
|${maven.conf}/settings.xml。
|
|注意：此位置可以用CLI选项覆盖：
|
|-gs/path/to/global/settings.xml
|
|此示例文件中的部分旨在为您提供一个运行起点
|充分利用Maven安装。在适当的情况下，默认
|提供值（未指定设置时使用的值）。
|-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 https://maven.apache.org/xsd/settings-1.2.0.xsd">
<!-- localRepository
| 本地存储库
| The path to the local repository maven will use to store artifacts.
| 本地存储库maven的路径将用于存储工件。
|
| Default: ${user.home}/.m2/repository
<localRepository>/path/to/local/repo</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.
| 这将决定maven在需要输入时是否提示您。如果设置为false，
|maven将使用一个合理的默认值，可能基于其他设置，用于
|有问题的参数。
|
| 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.
| 离线
|确定maven在执行构建时是否应尝试连接到网络。
|这将对工件下载、工件部署等产生影响。
| 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.
| 插件组
|这是在按前缀解析插件时将搜索的其他组标识符的列表，即。
|当调用“mvn前缀：目标”这样的命令行时。Maven将自动添加组标识符
|如果列表中尚未包含“org.apache.maven.plugins”和“org.codehaus.mojo”。
|-->
<pluginGroups>
<!-- pluginGroup
| Specifies a further group identifier to use for plugin lookup.
|plugin集团
|指定用于插件查找的另一个组标识符。
<pluginGroup>com.your.plugins</pluginGroup>
-->
</pluginGroups>
<!-- TODO Since when can proxies be selected as depicted? 从什么时候开始可以选择如图所示的代理？ -->
<!-- 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.
| 服务器
|这是一个身份验证配置文件列表，由系统中使用的服务器id标识。
|每当maven必须连接到远程服务器时，都可以使用身份验证配置文件。
|-->
<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.
|服务器
|指定连接到特定服务器时使用的身份验证信息，由以下内容标识
|系统内的唯一名称（由下面的“id”属性表示）。
|
|注意：您应该指定用户名/密码或私钥/密码，因为这些配对是
|一起使用。
|
<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.
|他的是一个镜像列表，用于从远程存储库下载工件。
|
|它的工作原理是这样的：POM可以声明一个存储库，用于解析某些工件。
|然而，这个存储库有时可能会遇到流量大的问题，因此人们已经镜像
|它去了几个地方。
|
|该存储库定义将具有唯一的id，因此我们可以为其创建镜像引用
|存储库，用作备用下载站点。镜像站点将是首选
|该存储库的服务器。
|-->
<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.
| 指定要使用的存储库镜像站点，而不是给定的存储库。存储库
|此镜像服务的ID与此镜像的mirrorOf元素匹配。使用ID
|用于继承和直接查找目的，并且必须在整个镜像集中是唯一的。
|
<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>
<id>maven-default-http-blocker</id>
<mirrorOf>external:http:*</mirrorOf>
<name>Pseudo repository to mirror external repositories initially using HTTP.</name>
<url>http://0.0.0.0/</url>
<blocked>true</blocked>
</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 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.
|
|这是一个配置文件列表，可以通过多种方式激活，也可以修改
|构建过程。settings.xml中提供的配置文件旨在提供本地计算机-
|允许构建在本地环境中工作的特定路径和存储库位置。
|
|例如，如果你有一个集成测试插件，比如仙人掌，你需要知道它在哪里
|您的Tomcat实例已安装，您可以在此处提供一个变量，使该变量为
|在构建过程中取消引用以配置仙人掌插件。
|
|如上所述，配置文件可以通过多种方式激活。一种方式-activeProfiles
|本文档的一节（settings.xml）-稍后将讨论。另一种基本方式
|依赖于对属性的检测，
|或者仅仅测试它的存在。配置文件也可以通过JDK版本前缀激活，其中
|在JDK版本“1.4.2_07”上执行构建时，值“1.4”可能会激活配置文件。
|最后，可以直接从命令行指定活动配置文件的列表。
|
|注意：对于settings.xml中定义的配置文件，您仅限于指定工件
|用作配置的存储库、插件存储库和自由格式属性
|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.
| 指定一组构建过程的介绍，使用一个或多个
|上述机制。出于继承目的，并通过<activatedProfiles/>激活配置文件
|配置文件必须具有唯一的ID。
|
|一个鼓励的配置文件识别最佳实践是使用一致的命名约定
|用于配置文件，如“env-dev”、“env-test”、“env生产”、“user-jdcasey”、“user brett”等。
|这将使理解引入的配置文件集所尝试的内容变得更加直观
|要实现这一点，特别是当您只有一个用于调试的配置文件id列表时。
|
|此配置文件示例使用JDK版本触发激活，并提供特定于JDK的仓库。
<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 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.
|
|这是另一个配置文件，由值为“dev”的属性“target env”激活
|提供指向Tomcat实例的特定路径。要使用此功能，您的插件配置可能
|假设看起来像：
|
| ...
|<插件>
|<groupId>org.myco.myplugins</groupId>
|<artifactId>我的插件</artifactId>
|
|<配置>
|<tomcatLocation>${tomcatPath}</tomcatLocation>
|</配置>
|</plugin>
| ...
|
|注意：如果你只是想在有人将“target env”设置为
|任何东西，你都可以省略激活属性中的<value/>。
<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>
通用的配置文件
<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 https://maven.apache.org/xsd/settings-1.2.0.xsd">
<!-- 本地仓库的位置 -->
<localRepository>/path/to/local/repo</localRepository>
<!-- 私服发布的用户名密码 -->
<servers>
<server>
<id>deploymentRepo</id>
<username>repouser</username>
<password>repopwd</password>
</server>
<server>
<id>siteServer</id>
<privateKey>/path/to/private/key</privateKey>
<passphrase>optional; leave empty if not used.</passphrase>
</server>
</servers>
<mirrors>
<!-- 阿里云镜像 -->
<mirror>
<id>alimaven</id>
<name>aliyun maven</name>
<!-- https://maven.aliyun.com/repository/public/ -->
<url>http://maven.aliyun.com/nexus/content/groups/public/</url>
<mirrorOf>central</mirrorOf>
</mirror>
</mirrors>
<!-- 配置: java8, 先从阿里云下载, 没有再去私服下载 -->
<!-- 不同版本可以自行测试：影响下载顺序的是profiles标签的配置顺序, 而不是activeProfiles的顺序 -->
<profiles>
<!-- 全局JDK1.8配置 -->
<profile>
<id>jdk1.8</id>
<activation>
<activeByDefault>true</activeByDefault>
<jdk>1.8</jdk>
</activation>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<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>
</profile>
<!-- Nexus私服配置: 第三方jar包下载, 比如oracle的jdbc驱动等 -->
<profile>
<id>dev</id>
<repositories>
<repository>
<id>nexus</id>
<url>url</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>public</id>
<name>Public Repositories</name>
<url>url</url>
</pluginRepository>
</pluginRepositories>
</profile>
<!-- 阿里云配置: 提高国内的jar包下载速度 -->
<profile>
<id>ali</id>
<repositories>
<repository>
<id>alimaven</id>
<name>aliyun maven</name>
<url>http://maven.aliyun.com/nexus/content/groups/public/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>alimaven</id>
<name>aliyun maven</name>
<url>http://maven.aliyun.com/nexus/content/groups/public/</url>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<!-- 激活配置 -->
<activeProfiles>
<activeProfile>jdk1.8</activeProfile>
<!-- <activeProfile>dev</activeProfile> -->
<activeProfile>ali</activeProfile>
</activeProfiles>
</settings>
参考文献
https://www.cnblogs.com/z2024/p/18276535
https://blog.csdn.net/m0_74363339/article/details/139768830
https://www.jb51.net/program/331587mod.htm