Maven介绍,IDEA安装和配置maven和maven指令

Maven

构建项目的工具

一,非maven项目:
1)第三方jar,需要自己下载,把jar拷贝到项目中
2)自己的项目需要打包,需要使用idea进行打包,其他项目需要使用,把jar拷贝到其他项目,如果jar对应项目更新,需要手动进行更新(重新打包),把其他项目之前jar删除,重新把新的jar拷贝到其他项目
3)jar之前的依赖关系,需要自己了解
4)对项目的整个构建(从项目开始(创建项目),编译,测试,运行到项目结束(打包)),每一个步骤都要
手动操作
5)项目结构没有统一的标准,多人,多团队开发,在项目合并会发生冲突

二,maven项目:(apache 提供)
1)通过maven管理jar,如果本地仓库没有依赖的jar,自动到远程仓库/中央仓库下载
2)Maven提供指令,所有操作直接一个指令完成jar更新,一个指令安装本地仓库,
发布远程仓库,其他项目的jar自动更新
3)Maven自动下载jar依赖的jar
4)统一项目结构

三,Maven安装
参考链接如下:https://blog.csdn.net/a805814077/article/details/100545928
下载:省略
1)解压就可以使用,maven
2)在系统环境变量,配置,aven

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

无视下载速度以及需要其他版本的伙伴点此进入Maven官网下载
选择左侧Download

点击箭头所指的链接进行下载

4.下载完成后，选择一个路径进行解压
5.然后配置path环境变量,如图

系统变量:MAVEN_HOME = F:\dev\apache-maven-3.6.1
系统变量:path = %MAVEN_HOME%\bin
MAVEN_HOME:

path:

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

四、配置settings文件
1.在D:\java46\Tools\maven\apache-maven-3.6.3\conf下可以找到settings文件，打开(嫌麻烦的直接看最后一步)

2.找到第52行，这里是maven默认的仓库

3.我们复制第53行

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

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

<localRepository>F:/repository</localRepository>

这里的路径随便设置，注意这里是正斜杠

4.因为国外的服务器下载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>

5.如图，要夹在两个mirrors标签之间

6.在最后配置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>

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

8.嫌麻烦的直接复制配置文件的内容即可,不过路径还是要改(参考第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 athttp://www.apache.org/licenses/LICENSE-2.0Unless 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>

五 ,在idea中配置maven
首先打开file --> Other setting --> Defualt setting ，idea2019版本应该是 setting for new project 里面，作如下修改：
第一个红框选择maven解压位置，第二个红框选择我们刚刚配置的setting.xml文件，第三个红框选择我们新建的本地仓库repository
需要注意的是：idea使用的JDK版本要和第二步试运行maven时显示的JDK版本一致。

然后打开Settings设置maven参数与上面一致。其中的Importing 和 Runner 内的 JDK 和 JRE 版本要一致。
在新建项目中，会出现一个pom.xml文件，这里是存储你版本信息以及进行maven仓库配置和下载的。
至此，maven在idea中的配置结束。

*六 .Maven指令

mvn archetype:generate ：创建 Maven 项目
mvn compile ：编译源代码
mvn test-compile ：编译测试代码
mvn test ： 运行应用程序中的单元测试
mvn site ： 生成项目相关信息的网站
mvn clean ：清除目标目录中的生成结果
mvn package ： 依据项目生成 jar 文件
mvn install ：在本地 Repository 中安装 jar
mvn deploy：将jar包发布到远程仓库
mvn eclipse:eclipse ：生成 Eclipse 项目文件

Maven介绍,IDEA安装和配置maven和maven指令相关推荐

eclipse maven plugin 插件安装和配置
本文转自:http://www.blogjava.net/fancydeepin/archive/2012/07/13/eclipse_maven3_plugin.html maven3 安装: 安装 ...
Android Studio(一)：介绍、安装、配置
Android Studio相关博客: Android Studio(一):介绍.安装.配置 Android Studio(二):快捷键设置.插件安装 Android Studio(三):设置Andr ...
五十、Maven系列：安装和配置Maven镜像
@Author:Runsen @Date:2020/6/11 人生最重要的不是所站的位置,而是内心所朝的方向.只要我在每篇博文中写得自己体会,修炼身心:在每天的不断重复学习中,耐住寂寞,练就真功,不畏 ...
Maven私库安装与配置
前言项目开发时,一般采用Maven来进行项目构建,管理,jar包下载,项目组开发人员开发时,只要在项目的pom.xml文件中,添加如下pom.xml信息从公共的库中下载相关的Jar包以及依赖Jar包 ...
Maven下载、安装和配置(转)
转载地址:http://blog.csdn.net/jiuqiyuliang/article/details/45390313 ; 前言在上篇博文[项目管理和构建]--Maven简介(一)中我们了解 ...
linux java maven_Linux下安装及配置Java与Maven
1.1安装Java sudo yum -y install java-1.8.0-openjdk #jre sudo yum -y install java-1.8.0-openjdk-devel # ...
java plugin 安装_eclipse maven plugin 插件安装和配置
Posted on 2012-07-13 12:40 fancydeepin 阅读(96246) 评论(45) 编辑收藏所属分类: Maven3 Guide 环境准备: eclipse(He ...
maven仓库的安装与配置
1.这是我所安装的版本,解压到没有中文空格特殊字符的目录下 2.maven 的使用是在jdk的基础上,所以电脑必须有jdk,没有安装配置jdk的可以先去配置一下,配置完的我们可以去配置配置MAVEN_ ...
eclipse maven plugin 插件安装和配置
2019独角兽企业重金招聘Python工程师标准>>> 环境准备: eclipse(Helios) 3.6 maven 3.0.4 maven3 安装: 安装 Maven 之前要求先 ...
eclipse maven 插件的安装和配置
maven3 安装: 安装 Maven 之前要求先确定你的 JDK 已经安装配置完毕.Maven是 Apache 下的一个项目.眼下最新版本号是 3.0.4.我用的也是这个. 首先去官网下载 Mave ...

Maven介绍,IDEA安装和配置maven和maven指令

Maven

Maven介绍,IDEA安装和配置maven和maven指令相关推荐

最新文章

热门文章