Maven

Maven的下载安装及使用

一、理解

Maven是一款自动化构建工具，专家 内行 专注服务于Java的构建和依赖管理
        
构建：将Java代码 配置文件 框架等等 最为“原材料”，进行一系列“生产”形成一个可以运行的项目的过程 
    
    
构建环节：
    1. 清理
    2. 编译  将java源码编译字节码文件
    3. 测试  针对项目测试  确保正确
    4. 报告  将测试后的结果形成文档
    5. 打包  java项目打成jar  JavaWeb应用打成 war
    6. 安装  将打包后的结果 安装到指定的仓库中  提供给别人使用
    7. 部署  将打包后的结果 部署远程仓库或者服务器中
Maven 可以自动从构建的起点 一直执行到终点    

二、Maven的作用

1. 自动打包
2. 添加第三方jar包
3. 处理jar之间的依赖关系
4. 处理jar之间的冲突
5. 将项目拆分成多个模块
6. 实现项目的分布式部署

三、Maven的配置

1. 下载地址：http://maven.apache.org/download.cgi
2. 解压：目录不要过深  不要有中文和特殊符号
3. 必须配置JAVA_HOME环境变量
4. 配置Maven的环境变量 
    	MAVEN_HOME : D:\javaTools3\apache-maven-3.5.2
         path添加：;%MAVEN_HOME%\bin;
5. 检查maven是否可用
    	doc命令窗口：mvn -v

Maven 依赖本地仓库 配置
    修改D:\javaTools3\apache-maven-3.5.2\conf\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>
  -->
    <!-- 1. 本地仓库 -->
	<localRepository>D:\javaTools3\RepMaven</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>
    -->
      <!-- 2. 镜像服务器 -->
	<server>
		<id>huaweicloud</id>
		<username>anonymous</username>
		<password>devcloud</password>
	</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>
	-->
	<!-- 3. 镜像地址 -->
	<mirror>
		<id>huaweicloud</id>
		<mirrorOf>*</mirrorOf>
		<url>https://mirrors.huaweicloud.com/repository/maven/</url>
	</mirror>
	<!--
	<mirror>
		<id>uk</id>
		<mirrorOf>central</mirrorOf>
		<name>Human Readable Name for this Mirror.</name>
		<url>http://uk.maven.org/maven2/</url>
	</mirror>

	<mirror>
		<id>CN</id>
		<name>OSChina Central</name>
		<url>http://maven.oschina.net/content/groups/public/</url>
		<mirrorOf>central</mirrorOf>
	</mirror>

	<mirror>
		<id>nexus</id>
		<name>internal nexus repository</name>
		
		<url>http://repo.maven.apache.org/maven2</url>
		<mirrorOf>central</mirrorOf>
	</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>
    -->
      <!-- 4. 配置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>

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

四、Maven的使用

约定大于配置  需要遵循Maven的格式
1. 编写Maven程序
    MavenDemo01 
    	src        ----> 核心代码
    		main  ----> 主程序的代码
    			java  ---> Java代码
    			resources ---> 配置文件
    		test  ----> 测试程序
    			java  ---> Java代码
    			resources ---> 配置文件
    		
    	pom.xml    ----> Maven项目的配置信息

2. idea创建Maven项目  
    ① 将idea与maven整合
    ② 创建Maven项目
    ③ 一路next

五、使用的细节

1. 主程序和测试做了分离 main目录  test目录
2. pom.xml   ---->  根据坐标引入依赖包
3. pom.xml指定当前的项目的坐标
    	<groupId>com.ujiuye</groupId>     公司域名的倒序
    	<artifactId>MavenDemo01</artifactId>  当前项目的名称
    	<version>1.0-SNAPSHOT</version>    当前的版本号
4. 引入其他jar 包  根据这个jar的坐标来引入
    	在pom文件中根据 
    		<dependencies>
                <!-- https://mvnrepository.com/artifact/junit/junit -->
                <dependency>
                    <groupId>junit</groupId>
                    <artifactId>junit</artifactId>
                    <version>4.11</version>
                    <scope>test</scope>
                </dependency>

            </dependencies>
5.如果不知道jar的坐标 直接通过 maven酷站找
       https://mvnrepository.com/ 

6. maven的生命周期
    

六、Maven依赖

1. 依赖第三方jar   从酷站中找坐标
2. 依赖自己的jar   从maven的本地仓库 根据坐标找 

七、Maven依赖范围

1. <scope>依赖的范围值</scope>
    *① compile 编译时生效
    	1. main目录下 可以访问当前的依赖
    	2. test目录下 可以访问当前的依赖
    	3. 部署到服务器中是 随之应用部署到WEB-INF lib导入依赖
    *② test 测试是生效
    	1. main目录下 不可以访问当前依赖
    	2. test目录下 可以访问当前依赖
    	3. 部署到服务器中是 不随之应用部署到WEB-INF lib导入依赖
    
    ③ runtime 运行时生效
    	1. main目录下 不可以访问当前的依赖
    	2. test目录下 可以访问当前的依赖
    	3. 部署到服务器中是 不随之应用部署到WEB-INF lib导入依赖
    
    ④ provided 当前项目编译和测试生效
    	
    	1. main目录下 可以访问当前的依赖
    	2. test目录下 可以访问当前的依赖
    	3. 部署到服务器中是 不随之应用部署到WEB-INF lib导入依赖

八、Maven的传递性

原则：
    1. 路径最短者优先
    2. 最新版本者优先

九、Maven的依赖排除

 	在依赖的传递过程中，传递重复的jar当前不用jar ,maven可以不让传递(依赖的排除)
     只需要在pom文件中 指定排除
     <dependency>
            <groupId>com.ujiuye</groupId>
            <artifactId>MavenDemo01</artifactId>
            <version>1.0-SNAPSHOT</version>
            <!-- 依赖的排除 -->
            <exclusions>
                <exclusion>
                    <groupId>junit</groupId>
                    <artifactId>junit</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

十、Maven版本统一管理

1. 依赖的jar可以指定统一的版本号
2. 如果需要修改版本号的话 只要改一个地方即可

<properties>
      <spring.version>5.2.1.RELEASE</spring.version>
  </properties>
  <dependencies>
    <!-- https://mvnrepository.com/artifact/org.springframework/spring-core -->
    <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-core</artifactId>
      <version>${spring.version}</version>
    </dependency>
    <!-- https://mvnrepository.com/artifact/org.springframework/spring-context -->
    <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-context</artifactId>
      <version>${spring.version}</version>
    </dependency>

    <!-- https://mvnrepository.com/artifact/org.springframework/spring-beans -->
    <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-beans</artifactId>
      <version>${spring.version}</version>
    </dependency>

十一、继承

1. 继承关系

1. 创建父工程  ---> 要求打包方式pom
    	 <groupId>com.ujiuye</groupId>
    	<artifactId>Dad</artifactId>
    	<packaging>pom</packaging>
    	<version>1.0-SNAPSHOT</version>
 2. 创建子模块  
    	

在父工程的pom文件中
    <modules>
        <module>son1</module>
        <module>son2</module>
    </modules>

在子模块中的pom文件中
    <parent>
        <artifactId>Dad</artifactId>
        <groupId>com.ujiuye</groupId>
        <version>1.0-SNAPSHOT</version>
    </parent>

2. 子模块继承父工程的依赖

父工程的pom文件中 添加依赖管理
    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>junit</groupId>
                <artifactId>junit</artifactId>
                <version>4.12</version>
                <scope>test</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>

子模块的pom文件  继承父工程的依赖
    <dependencies>
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            
        </dependency>
    </dependencies>

十二、Maven的聚合

将子模块聚合一起形成一个工程
    <modules>
        <module>son1</module>
        <module>son2</module>
    </modules>
为什么要使用聚合呢？
    不使用的情况下：每一个模块都需要Maven管理（清理/编译/打包/安装/部署）
    使用了聚合：只需要管理父工程

十三、Maven酷站

https://mvnrepository.com/