maven安装方式，在eclipse中的配置

最新推荐文章于 2022-11-17 23:09:49 发布

_大白_

最新推荐文章于 2022-11-17 23:09:49 发布

阅读量213

点赞数

分类专栏： maven 文章标签： maven

本文链接：https://blog.csdn.net/qq_39533140/article/details/98482288

版权

maven 专栏收录该内容

0 篇文章 0 订阅

订阅专栏

一. 安装与配置
- 1.1官网下载安装包
- 1.1、官网下载安装包
- 1.2、配置环境变量
- 1.3、本地仓储配置
- 1.4、中央仓库配置
二.eclipse中使用maven
- 2.1 eclipse配置maven
- 2.2 在eclipse中使用maven创建项目
  一 . 安装与配置
  其实主流的开发工具如IDEA、Eclipse都集成了Maven（可见重要性），但为了更加深刻的学习与管理该工具（比如多个IDE共享的问题），个人建议还是单独安装比较好。

1.1、官网下载安装包
在浏览器中打开下载地址：http://maven.apache.org/download.cgi
在这里插入图片描述

1.2、配置环境变量
注意：安装maven之前，必须先确保你的机器中已经安装了JDK，如果是Maven3则必须JDK1.7以上。

1．下载后解压压缩包，本人解压到，D:\maven\apache-maven-3.6.1目录下，注意：安装路径下没有中文
在这里插入图片描述
2．添加环境变量MAVEN_HOME，值为apache-maven的安装路径(没有中文)

3．在Path环境变量的变量值末尾添加%MAVEN_HOME%\bin;
window7 系统要用";"间隔，如下图，win10，直接添加即可
在这里插入图片描述
4．在命令行中输入mvn –version，如果出现maven的版本信息，说明配置成功。

1.3、本地仓储配置
如果您不配置，默认会在如下位置存放从远程下载到的包：
在这里插入图片描述
从中央仓库下载的jar包，都会统一存放到本地仓库中。我们需要配置本地仓库的位置。

打开maven安装目录，打开conf目录下的setting.xml文件。

可以参照下图配置本地仓储位置。

在这里插入图片描述
你还可以在运行时指定本地仓库位置：

mvn clean install -Dmaven.repo.local=d:\yourpath

1.4、中央仓库配置
当构建一个Maven项目时，首先检查pom.xml文件以确定依赖包的下载位置，执行顺序如下：

1、从本地资源库中查找并获得依赖包，如果没有，执行第2步。
2、从Maven默认中央仓库中查找并获得依赖包如果没有，执行第3步。
3、如果在pom.xml中定义了自定义的远程仓库，那么也会在这里的仓库中进行查找并获得依赖包，如果都没有找到，那么Maven就会抛出异常。

在这里插入图片描述

修改默认中央仓库地址

 <mirror>
		<id>nexus-aliyun</id>  
		<mirrorOf>*,!jeecg,!jeecg-snapshots</mirrorOf>  
		<name>Nexus aliyun</name>  
		<url>http://maven.aliyun.com/nexus/content/groups/public</url>  
	</mirror>
 </mirrors>

以下为常用地址，建议使用阿里云

1、http://www.sonatype.org/nexus/  私服nexus工具使用
2、http://mvnrepository.com/ （推荐）
3、http://repo1.maven.org/maven2
4、http://maven.aliyun.com/nexus/content/groups/public/  阿里云  （强力推荐）
5、http://repo2.maven.org/maven2/ 私服nexus工具使用
6、http://uk.maven.org/maven2/
7、http://repository.jboss.org/nexus/content/groups/public
8、http://maven.oschina.net/content/groups/public/  
9、http://mirrors.ibiblio.org/maven2/
10、http://maven.antelink.com/content/repositories/central/
11、http://nexus.openkoala.org/nexus/content/groups/Koala-release/
12、http://maven.tmatesoft.com/content/groups/public/

提供本人配置完整的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.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:\maven\InstallFiles\javaKit\mavenRes</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>nexus-aliyun</id>  
		<mirrorOf>*,!jeecg,!jeecg-snapshots</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 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>
    -->
	<profile>   
		<id>jdk1.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>

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

二 . maven在eclipse中的使用
2.1 配置maven
eclipse一个集成的开发环境，在开发过程中用的很广泛，下面看如何在eclipse中使用maven，在eclipse的4.4以上的版本加入了对maven的支持，即不需要安装maven插件，但对4.4以下的版本需要自己安装插件，可以在下面的网址：http://marketplace.eclipse.org/content/maven-integration-eclipse-luna，去了解安装过程，安装完成之后，
1、在windows–>>preferences中找到maven选项，下图，
在这里插入图片描述
上图中我们找到maven–>>installations看到，已经有了，但是我们要使用刚才安装的maven，选择add按钮，找到刚才解压的maven的路径，如下，

在这里插入图片描述

2、eclipse中更新配置文件：
在eclipse中windows–>preferences，找到maven，然后如下图所示，找到User settings，修改配置文件为刚才修改的配置文件，

在这里插入图片描述

全局配置（global settings ）
本台电脑的配置，使用这台电脑的所有用户都是用这个配置

个人配置（user settings）
当前用户的配置

个人配置（user settings ）会覆盖全局配置（global settings）

修改完成之后，则和eclipse的集成完成。

经过以上的步骤则maven和eclipse的集成完成，接下来可以使用maven了，但，如果你的电脑是通过代理上网的话，必须在settings.xml文件中配置代理，这样才可以从maven的仓库中下载所需的文件，配置的代理的方式如下，在settings.xml文件中添加如下内容，

	<proxy>  
     <id>myProxy</id>  
     <active>true</active>  
     <protocol>http</protocol>
     <username></username>
      <password></password>     
     <host>proxy.xxxxx</host>  
     <port>910</port>    
   </proxy> 
<!--
id  代理ID 标识代理

active  设置代理是否启用

protocol  代理使用的协议

username  连接代理的用户名，如，此代理不需要用户名则可以把此标签删掉

password  连接代理的密码，如，同上

host  代理的网址

port  代理使用的端口

上面是使用代理上网的配置，如果上网没使用代理，则不需要配置。
-->

2.2 在eclipse中使用maven创建项目

java开发过程中使用的最多的是java、javaWeb项目，

file–>>new—>project，然后找到maven，如下图选择，
在这里插入图片描述
点击next

选择webapp，点击next

在这里插入图片描述
第一个红框内表示的是新建java项目，第二个是javaWeb项目，这里选择第一个，

输入红框的内容之后，点击finish，ecplise则会开始创建项目，此时会连接网络从网上下载需要的jar包，jar包存放的路径就是配置的本地仓库的路径，我的在：D:\maven\InstallFiles\javaKit\mavenResy路径下，在D:\maven\InstallFiles\javaKit\mavenRes\org\apache\maven\plugins文件夹下是maven插件所需的依赖插件。

部分转载至
https://www.cnblogs.com/best/p/9676515.html#_lab2_1_0