精华内容
下载资源
问答
  • Maven的安装与配置

    万次阅读 多人点赞 2019-09-04 19:48:17
    Maven超详细的安装与配置步骤

    一、安装本地Maven

    tips: 官网为外网,下载速度较慢,这里提供3.6.3版本的三方链接下载Maven下载

    1. 无视下载速度以及需要其他版本的伙伴点此进入Maven官网下载

    2. 选择左侧Download
      在这里插入图片描述

    3. 点击箭头所指的链接进行下载
      在这里插入图片描述

    4. 下载完成后,选择一个路径进行解压

    5. 然后配置path环境变量,如图

    • 系统变量:MAVEN_HOME = F:\dev\apache-maven-3.6.1
    • 系统变量:path = %MAVEN_HOME%\bin
      MAVEN_HOME:
      在这里插入图片描述

    在这里插入图片描述

    path:
    在这里插入图片描述

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

    在这里插入图片描述

    二、配置settings文件

    1. 在F:\dev\apache-maven-3.6.1\conf下可以找到settings文件,打开(嫌麻烦的直接看最后一步)

    2. 找到第52行,这里是maven默认的仓库
      在这里插入图片描述

    3. 我们复制第53行

    <localRepository>/path/to/local/repo</localRepository>
    

    将它拿到注释外并将中间的内容改成你需要的路径,如图

    <localRepository>F:/repository</localRepository>
    

    这里的路径随便设置,注意这里是正斜杠
    在这里插入图片描述

    1. 因为国外的服务器下载jar包很慢所以我们改为阿里云服务器(大约在150行左右),这两个仓库只用选一个(根据大家反馈建议使用第一个,第二个在有的版本可能会出现warning)
     <!-- 阿里云仓库 -->
            <mirror>
                <id>alimaven</id>
                <mirrorOf>central</mirrorOf>
                <name>aliyun maven</name>
                <url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
            </mirror>
         或者
          <mirror>
    		<id>nexus-aliyun</id>
    		<mirrorOf>*</mirrorOf>
            <name>Nexus aliyun</name>
            <url>http://maven.aliyun.com/nexus/content/groups/public</url>
    	 </mirror>
    
    
    1. 如图,要夹在两个mirrors标签之间
      在这里插入图片描述

    2. 在最后配置jdk,也要夹在两个profiles标签之间(我这里使用的为jdk8)

    <!-- java版本 --> 
    <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>
    
    

    在这里插入图片描述

    1. 配置完成,在命令行输入mvn help:system测试,看到下载链接里面是ailiyun的链接表示配置成功

    2. 嫌麻烦的直接复制配置文件的内容即可,不过路径还是要改(参考第3步)

    <?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>F:/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.
       |-->
      
        <!-- mirror
    	<mirrors>
         | 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>
    	 </mirrors>
         -->
         <!-- 阿里云仓库 -->
     <mirrors>
    	 <mirror>
    			<id>nexus-aliyun</id>
    			<mirrorOf>*</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.
       |
       |-->
        <!-- profile
    	<profiles>
         | 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>
    	  
        -->
    <profiles>
    <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的安装与配置

    2018-05-21 17:59:39
    maven的安装与配置; maven的安装与配置 ;maven的安装与配置
  • Maven 的安装与配置

    2020-10-23 13:31:42
    Maven 的安装与配置 1.Maven 软件的下载 为了使用 Maven 管理工具,我们首先要到官网去下载它的安装软件,https://maven.apache.org/download.cgi 大家也可以下 载最新版本,也可以使用我在使用的版本,包含本地...

    Maven 的安装与配置

    1.Maven 软件的下载

    为了使用 Maven 管理工具,我们首先要到官网去下载它的安装软件,https://maven.apache.org/download.cgi
    在这里插入图片描述

    大家也可以下 载最新版本,也可以使用我在使用的版本,包含本地仓库文件:
    链接:https://pan.baidu.com/s/1Ai5lnJnC4TeutG9MZD9tbw 提取码:1024

    Maven 下载后,将 Maven 解压到一个没有中文没有空格的路径下,解压后的目录为:在这里插入图片描述
    bin:存放了 maven 的命令。
    boot:存放了一些 maven 本身的引导程序,如类加载器等 conf:存放了 maven 的一些配置文件,如 setting.xml 文件
    lib:存放了 maven 本身运行所需的一些 jar 包 至此我们的 maven 软件就可以使用了,前提是你的电脑上之前已经安装并配置好了 JDK。

    JDK 的准备及统一

    1.JDK 使用 JDK8版本

    1. JDK 环境:
      在这里插入图片描述
      2.Maven 及 JDK 配置

    电脑上需安装 java 环境,安装 JDK1.7 + 版本 (将JAVA_HOME/bin 配置环境变量 path ),我使
    用的是JDK8 相关版本

    > 1.配置 MAVEN_HOME ,变量值就是你的 maven 安装 的路径(bin 目录之前一级目录)

    在这里插入图片描述

    >2.在系统变量path路径下新建:%MAVEN_HOME%\bin在这里插入图片描述

    Maven 软件版本测试

    通过 mvn -v命令检查 maven 是否安装成功,看到 maven 的版本为 3.5.2 (对应你自己使用的版本)及 java 版本为 1.8 即为安装 成功。
    找开 cmd 命令,输入 mvn –v命令,如下图:
    在这里插入图片描述

    Maven 仓库

    maven 的工作需要从仓库下载一些 jar 包,如下图所示,本地的项目 A、项目 B 等都会通过 maven
    软件从远程仓库(可以理解为互联网上的仓库)下载 jar 包并存在本地仓库,本地仓库 就是本地文 件夹,当第二次需要此 jar
    包时则不再从远程仓库下载,因为本地仓库已经存在了,可以将本地仓库 理解为缓存,有了本地仓库就不用每次从远程仓库下载了。

    maven 中仓库的类型

    本地仓库 :用来存储从远程仓库或中央仓库下载的插件和 jar 包,项目使用一些插件或 jar 包, 优先从本地仓库查找 默认本地仓库位置在 user.dir/.m2/repository{user.dir}/.m2/repository,{user.dir}表示windows 用户目录。
    在这里插入图片描述

    打开setting.xml文件编辑以下内容:
    在这里插入图片描述

    远程仓库:如果本地需要插件或者 jar 包,本地仓库没有,默认去远程仓库下载。 远程仓库可以在互联网内也可以在局域网内。

    中央仓库 :在 maven 软件中内置一个远程仓库地址 http://repo1.maven.org/maven2 ,它是中 央仓库,服务于整个互联网,它是由 Maven 团队自己维护,里面存储了非常全的 jar 包,它包 含了世界上大部分流行的开源项目构件

    Maven 本地仓库的配置

    将上面云盘链接中本地仓库文件下的 “maven_repository.rar”解压至自己的 电脑上
    目录:(可以放在没有中文及空格的目录下:在这里插入图片描述

    在 /conf/settings.xml 文件中配置本地仓库位置(maven 的安装目录下):
    在这里插入图片描述
    全局 setting 与用户 setting

    maven 仓库地址、私服等配置信息需要在 setting.xml 文件中配置,分为全局配置和用户配置。 在 maven 安装目录下的有 conf/setting.xml 文件,此 setting.xml 文件用于 maven 的所有 project 项目,它作为 maven 的全局配置。 如需要个性配置则需要在用户配置中设置,用户配置的 setting.xml 文件默认的位置在:user.dir/.m2/settings.xml,{user.dir} /.m2/settings.xml 目录中,{user.dir} 指windows 中的用户目录。 maven会先找用户配置,如果找到则以用户配置文件为准,否则使用全局配置文件。
    在这里插入图片描述
    maven从中央仓库下载jar太慢可以配置国内的 阿里云仓库
    在刚编辑的setting.xml中找到以下位置:
    在这里插入图片描述
    在 标签中加入以下配置:

    <mirror>
        <id>alimaven</id>
        <mirrorOf>central</mirrorOf>
        <name>aliyun maven</name>
        <url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
     
    </mirror>
    <mirror>
        <id>repo1</id>
        <mirrorOf>central</mirrorOf>
        <name>Human Readable Name for this Mirror.</name>
        <url>http://repo1.maven.org/maven2/</url>
    </mirror>
    
    <mirror>
        <id>repo2</id>
        <mirrorOf>central</mirrorOf>
        <name>Human Readable Name for this Mirror.</name>
        <url>http://repo2.maven.org/maven2/</url>
    </mirror>
    
    展开全文
  • MAVEN的安装与配置

    2020-07-20 10:33:34
    MAVEN的安装与配置 下载地址:http://maven.apache.org/download.cgi 获得压缩包后直接解压到一个指定目录即可。 解压后需要配置环境变量。 在系统变量中添加变量:MAVEN_HOME 值为解压的目录 然后找到Path变量,...

    MAVEN的安装与配置

    下载地址:http://maven.apache.org/download.cgi
    在这里插入图片描述

    获得压缩包后直接解压到一个指定目录即可。

    解压后需要配置环境变量。

    在系统变量中添加变量:MAVEN_HOME 值为解压的目录
    在这里插入图片描述

    然后找到Path变量,添加: %MAVEN_HOME%\bin
    在这里插入图片描述

    打开cmd窗口,输入 mvn -v 出现下列指令说明安装成功
    在这里插入图片描述

    展开全文

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 3,644
精华内容 1,457
关键字:

maven的安装与配置