【8017】安装MAVEN配置从下载到idea运行

最新推荐文章于 2023-09-26 09:17:36 发布

快乐的数据库

最新推荐文章于 2023-09-26 09:17:36 发布

阅读量578

点赞数 2

分类专栏： MAVEN 文章标签： maven intellij-idea java

本文链接：https://blog.csdn.net/Caojian_0/article/details/127683240

版权

MAVEN 专栏收录该内容

1 篇文章 0 订阅

订阅专栏

【8017】安装MAVEN配置从下载到idea运行

问题背景：

今天心血来潮，本来用的好好的MAVEN默认系统的项目（C盘），看到Springboot视频后，别人搭配环境的时候放到了其他盘里，就想也搞搞（以前也搞过，不过当时觉得每次都需要重新配置嫌麻烦就用系统配置的了），当然那个时候有个步骤没搞好导致的，底下会提示的，于是花了十几分钟又重新配置的一下，写个博客记录记录。

安装步骤：（两大步）

1.下载Maven–>配置环境变量–>配置本地仓库–>配置镜像–>配置JDK
2.配置idea默认配置

第一步：下载Maven：

点击这里，是MAVEN的官网下载地址，我下载的是可执行版本：

https://maven.apache.org/download.cgi

Binary是可执行版本（已经编译好的）
Source是源代码版本（需要自己编译成可执行软件）
在这里插入图片描述
下载完成后进行解压到自己要安装的路径（记住自己下载的位置，最好不要放在C盘了）

第二步：maven环境配置(右击此电脑，点击属性，找到高级系统环境)：

先编辑系统变量：MAVEM_HOME：

D:\MAVEN\apache-maven-3.5.4-bin\apache-maven-3.5.4//实际配置环境变量时以自己安装的路径为准

再编写Path环境变量：

%MAVEM_HOME%\bin

在这里插入图片描述

在这里插入图片描述

然后win+R运行cmd，输入mvn -version，如图所示则配置成功

第三步：配置本地仓库：

1.在D盘的某个位置（推荐在MAVEN文件夹下，自己定义的）下建一个maven仓库（用来放下载的资源的）：repository文件夹（我的是D:\Software.m2\repository）
在这里插入图片描述
2.编辑conf下的settings.xml文件配置：
在路径D:\MAVEN\apache-maven-3.5.4-bin\apache-maven-3.5.4\conf(自己安装的路径)下找到settings.xml文件–>找到节点localRepository，在注释外添加自己仓库的地址:

   <localRepository>D:\Software\.m2\repository</localRepository>//实际配置环境变量时以自己安装的路径为准

在这里插入图片描述

第四步：配置配置镜像和JDK编译版本：

1在settings.xml配置文件中找到mirrors节点，找到并在和两个标签之间添加如下配置：

<!-- 阿里云仓库 -->
<mirror>
<id>alimaven</id>
<mirrorOf>central</mirrorOf>
<name>aliyun maven</name>
<url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
</mirror>

在这里插入图片描述
原来的默认配置条件，也可以删除掉，重复了有些会出现报错，有的人下载的版本就没有默认的镜像配置，反正我是删除了，不过也没啥影响，已上图为准哦。

值得注意的是：
mirrors可以配置多个子节点，但是它只会使用其中的一个节点，即默认情况下配置多个mirror的情况下，只有第一个生效，只有当前一个mirror无法连接的时候，才会去找后一个；当然对于配置阿里镜像来说这个配置显得多余了（你在怀疑阿里镜像不够强吗，所以我把默认的删掉了）。

在这里插入图片描述
在settings.xml配置文件中找到profiles节点，添加如下JDK版本配置：

 <!--	JDK版本配置-->
	<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>
</profile>

在这里插入图片描述
到这里关于MAVEN的配置已经完成，测试成功与否：win+R运行cmd，输入mvn help:system测试，配置成功则本地D:\Software.m2\repository中会出现一些文件，运行效果如图：

配置文件的内容参考文件,版本相同的话可直接复制，当然还是需要修改路径：

<?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>D:\Software\.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>

<id>alimaven</id>

<mirrorOf>central</mirrorOf>

<name>aliyun maven</name>

<url>http://maven.aliyun.com/nexus/content/repositories/central/</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>
    -->
 <!--	JDK版本配置-->
	<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>
</profile>
  </profiles>
<!-- java版本 --> 


  <!-- activeProfiles
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
  -->
</settings>

第二大步骤：配置idea，并运行MAVEN：

点击File–>settings…–>Build,Execution,Deployment–>Build Tools–>Maven–>
修改这三个地方：
Maven home path:MAVEN的安装位置，定位到有bin的那一层目录；
User settings file: settings的安装位置，定位到config目录下setting的位置；
Local repository:定位到本地仓库安装目录；
如图仅供参考：
在这里插入图片描述
到这里关于idea的MAVEN已经配置完成了，我也新建运行了几个项目，没出现什么问题。

结尾小叙：

1.开头我不是说我以前配置MAVEN每次点击idea都要重新配置一遍吗。其实还是我没有将idea的maven配置好，导致的错误，在这里向曾经的自己道歉，是我的粗心；这一步我用了默认配置导致的；
在这里插入图片描述

2.之所以回来修改maven的配置问题，因为我现在已经学习到springboot了，用的maven项目越来越多，往后下载更新其他人的项目，C盘毕竟越来越满，本着能不占有C盘就不占有C盘的原则，没办法还是要回来搞一搞的，况且也快工作了，加油吧！
3.当然关于修改idea配置，你也可以使用在idea提供的settings里进行修改，这也是可行，具体步骤可以CSDN搜一搜的；
4.我知道有些人安装MAVEN的会遇到各种各样的问题，我刚开始也一样，大概原因是安装不细心，少个东西，或者位置不对等等，至少我的这个安装过程亲测是可执行的，有问题欢迎底下评论交流，会及时回复！