Windows 下的 Maven&JDK 安装与配置
Maven是一个项目管理和综合工具。Maven提供了开发人员构建一个完整的生命周期框架。开发团队可以自动完成项目的基础工具建设，Maven使用标准的目录结构和默认构建生命周期。
在多个开发团队环境时，Maven可以设置按标准在非常短的时间里完成配置工作。由于大部分项目的设置都很简单，并且可重复使用，Maven让开发人员的工作更轻松，同时创建报表，检查，构建和测试自动化设置。
一、下载Maven
1、下载
官网下载地址：http://maven.apache.org/download.cgi
我们下载Binary zip archive （二进制压缩归档文件）
2、解压
我们下载的是压缩归档文件，不用安装，解压即可。
我这里将其解压到了F盘：D:\devenv\java\maven\apache-maven-3.9.11
3、环境变量配置
Win10可以直接搜索“环境变量”打开配置界面：
其他用户请：计算机右键→属性→高级系统设置→环境变量
我们需要在系统变量新建两个变量 M2_HOME 和 MAVEN_HOME，值为安装路径；
M2_HOME=D:\devenv\java\maven\apache-maven-3.9.11
MAVEN_HOME=D:\devenv\java\maven\apache-maven-3.9.11
然后再编辑系统变量PATH，添加 %M2_HOME%\bin
C. 验证
Win+R 运行 输入cmd打开命令行，在命令行里面输入 mvn -version
C:\Users\NB0382>mvn -version
Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b)
Maven home: D:\devenv\java\maven\apache-maven-3.9.11
Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: D:\devenv\java\jdk18\jdk1.8.0_202\jre
Default locale: zh_CN, platform encoding: GBK
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"二、JDK安装与配置
1、jdk下载
（1）百度网盘（1.8 版本）
链接：https://pan.baidu.com/s/1YJwDMltvczK8FZAwF2dHug?pwd=36m0
提取码：36m0（2）百度网盘（17 版本）
链接：https://pan.baidu.com/s/1_jslZYt_8A2440gbnhOaXQ?pwd=fs40
提取码：fs402、安装
点击暗转软件，一路安装即可，安装到如下路径：D:\devenv\java\jdk18\jdk1.8.0_202;D:\devenv\java\jre18
3、配置
点击 我的电脑 → 右键 → 选择 属性 ，点击 高级系统设置，或者 控制面板 → 系统和安全 → 系统 也可以找到 高级系统设置，或者快捷键 Win + S ，在输入框中输入 env，回车即可。
点击环境变量后，跳出如下图所示对话框，第一步点击 “新建”，随后跳出 “新建系统变量” 对话框，一般来说系统变量中是没有 “JAVA_HOME” 的，在弹出的 新建系统变量 对话框中的 变量名 填入 JAVA_HOME，变量值填入 ：D:\devenv\java\jdk18\jdk1.8.0_202（安装 Java 时 JDK 所在的文件夹， 默认安装都是在 C 盘的）。如果已经存在 JAVA_HOME 的，那么就在它的变量值的最后面加上英文分号（;），然后再将 JDK 的路径添加在这个分号的后面，点击 确定。
新建变量名 CLASSPATH，变量值：.;%JAVA_HOME%\lib\dt.jar;%JAVA_HOME%\lib\tools.jar（注意前面的 .;也要放进去，此变量名主要适用于 JDK8 不加目测也没什么问题），点击 确定。
双击打开 Path，点击新建按钮，添加变量值：%JAVA_HOME%\bin %JAVA_HOME%\jre\bin（注意：分开作为两行，如果只有一行，则用 ; 分开即可），点击 确定。
点击三次 确定 返回，即可
查看命令：
java -version
C:\Users\NB0382>java -version
java version "1.8.0_202"
Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)查看 Maven命令：
C:\Users\NB0382>mvn -version
Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b)
Maven home: D:\devenv\java\maven\apache-maven-3.9.11
Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: D:\devenv\java\jdk18\jdk1.8.0_202\jre
Default locale: zh_CN, platform encoding: GBK
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"三、配置IDEA
Maven 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.
-->
<!--
| 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.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.
|
| Default: ${user.home}/.m2/repository
<localRepository>/path/to/local/repo</localRepository>
-->
<localRepository>D:\devenv\java\maven\apache-maven-3.9.11\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>
<!-- 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.
|-->
<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>
<id>nexus-aliyun</id>
<mirrorOf>central</mirrorOf>
<name>Nexus aliyun</name>
<url>http://maven.aliyun.com/nexus/content/groups/public</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 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 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 仓库地址：
<localRepository>D:\devenv\java\maven\apache-maven-3.9.11\repository</localRepository>修改镜像地址为阿里云地址：
<mirror>
<id>nexus-aliyun</id>
<mirrorOf>central</mirrorOf>
<name>Nexus aliyun</name>
<url>http://maven.aliyun.com/nexus/content/groups/public</url>
</mirror>四、bat脚本批量安装jar离线依赖包
install-artemis.bat
@echo off
REM ==========================================================
REM 批处理脚本：安装 artemis-http-client 到本地 Maven 仓库
REM 作者：ChatGPT
REM 使用方法：双击运行，或在命令行执行 install-artemis.bat
REM ==========================================================
:: 配置 JAR 文件所在路径（不要带最后的反斜杠）
set JAR_DIR=D:\jarlibs
:: Maven 坐标信息（与官方 pom.xml 一致）
set GROUP_ID=com.hikvision.ga
set ARTIFACT_ID=artemis-http-client
set VERSION=1.1.14.RELEASE
echo.
echo ================================================
echo 正在安装 %ARTIFACT_ID% 主 jar 到本地 Maven 仓库...
echo ================================================
mvn install:install-file ^
-Dfile=%JAR_DIR%\%ARTIFACT_ID%-%VERSION%.jar ^
-DgroupId=%GROUP_ID% ^
-DartifactId=%ARTIFACT_ID% ^
-Dversion=%VERSION% ^
-Dpackaging=jar
if %ERRORLEVEL% NEQ 0 (
echo.
echo [错误] 主 jar 安装失败，请检查文件路径和 Maven 环境！
pause
exit /b %ERRORLEVEL%
)
echo.
echo ================================================
echo 正在安装 %ARTIFACT_ID% javadoc jar 到本地 Maven 仓库...
echo （如果不存在此文件会提示找不到，但不影响运行）
echo ================================================
mvn install:install-file ^
-Dfile=%JAR_DIR%\%ARTIFACT_ID%-%VERSION%-javadoc.jar ^
-DgroupId=%GROUP_ID% ^
-DartifactId=%ARTIFACT_ID% ^
-Dversion=%VERSION% ^
-Dpackaging=jar ^
-Dclassifier=javadoc
echo.
echo ================================================
echo 所有操作完成！
echo 请在 pom.xml 中添加以下依赖：
echo.
echo ^<dependency^>
echo ^<groupId^>%GROUP_ID%^</groupId^>
echo ^<artifactId^>%ARTIFACT_ID%^</artifactId^>
echo ^<version^>%VERSION%^</version^>
echo ^</dependency^>
echo ================================================
pause相关文章：
Windows下的Maven安装与配置【附Idea设置默认】
JDK 安装及配置教程（Windows）
Java/JDK下载安装与环境配置（Windows 10 超详细的图文版教程 ）
为者常成，行者常至
自由转载-非商用-非衍生-保持署名（创意共享3.0许可证）
