maven 订阅
Maven项目对象模型(POM),可以通过一小段描述信息来管理项目的构建,报告和文档的项目管理工具软件。Maven 除了以程序构建能力为特色之外,还提供高级项目管理工具。由于 Maven 的缺省构建规则有较高的可重用性,所以常常用两三行 Maven 构建脚本就可以构建简单的项目。由于 Maven 的面向项目的方法,许多 Apache Jakarta 项目发文时使用 Maven,而且公司项目采用 Maven 的比例在持续增长。Maven这个单词来自于意第绪语(犹太语),意为知识的积累,最初在Jakata Turbine项目中用来简化构建过程。当时有一些项目(有各自Ant build文件),仅有细微的差别,而JAR文件都由CVS来维护。于是希望有一种标准化的方式构建项目,一个清晰的方式定义项目的组成,一个容易的方式发布项目的信息,以及一种简单的方式在多个项目中共享JARs。 [1] 展开全文
Maven项目对象模型(POM),可以通过一小段描述信息来管理项目的构建,报告和文档的项目管理工具软件。Maven 除了以程序构建能力为特色之外,还提供高级项目管理工具。由于 Maven 的缺省构建规则有较高的可重用性,所以常常用两三行 Maven 构建脚本就可以构建简单的项目。由于 Maven 的面向项目的方法,许多 Apache Jakarta 项目发文时使用 Maven,而且公司项目采用 Maven 的比例在持续增长。Maven这个单词来自于意第绪语(犹太语),意为知识的积累,最初在Jakata Turbine项目中用来简化构建过程。当时有一些项目(有各自Ant build文件),仅有细微的差别,而JAR文件都由CVS来维护。于是希望有一种标准化的方式构建项目,一个清晰的方式定义项目的组成,一个容易的方式发布项目的信息,以及一种简单的方式在多个项目中共享JARs。 [1]
信息
本    质
项目对象模型
定    义
项目构建管理
分    类
java
中文名
麦文
外文名
Maven
Maven特点
那么,Maven 和 Ant 有什么不同呢?在回答这个问题以前,首先要强调一点:Maven 和 Ant 针对构建问题的两个不同方面。Ant 为 Java 技术开发项目提供跨平台构建任务。Maven 本身描述项目的高级方面,它从 Ant 借用了绝大多数构建任务。因此,由于 Maven 和 Ant代表两个差异很大的工具,所以接下来只说明这两个工具的等同组件之间的区别,如表 1 所示。 [1]  Maven是一个项目管理工具,它包含了一个项目对象模型 (Project Object Model),一组标准集合,一个项目生命周期(Project Lifecycle),一个依赖管理系统(Dependency Management System),和用来运行定义在生命周期阶段(phase)中插件(plugin)目标(goal)的逻辑。当你使用Maven的时候,你用一个明确定义的项目对象模型来描述你的项目,然后Maven可以应用横切的逻辑,这些逻辑来自一组共享的(或者自定义的)插件。Maven 有一个生命周期,当你运行 mvn install 的时候被调用。这条命令告诉 Maven 执行一系列的有序的步骤,直到到达你指定的生命周期。遍历生命周期旅途中的一个影响就是,Maven 运行了许多默认的插件目标,这些目标完成了像编译和创建一个 JAR 文件这样的工作。此外,Maven能够很方便的帮你管理项目报告,生成站点,管理JAR文件,等等。
收起全文
精华内容
下载资源
问答
  • maven
    千次阅读
    2022-04-14 10:53:20

    本文介绍了在jenkins中maven的安装及配置(安装maven及jdk的方法),以及如何在jenkins中创建maven任务。

    有三点需要注意的地方。

    •         maven一定要安装在jenkins服务器上。
    •         maven安装之前要先安装jdk。
    •         建任务前,需要有git环境,并配置好用户名密码。

    1. JDK的安装

    centos7是自带OPEN JDK1.8的,但是不建议用,因为后面在jenkins中配置JDK目录的时候,自带的OPEN JDK无法识别,还是建议到官网下载安装。

    1)到oracle官网下载JDK1.8文件,并上传至服务器解压缩,无需安装,直接使用。

    2)执行java文件,看下版本。

    2. maven的安装

    1)到apache官网下载maven 包,并上传至服务器,无需安装,解压直接使用。

    2)配置maven文件settings.xml,在/app/maven-3.0.5/conf下。

    主要修改2个地方,localRepository目录  以及   MIRRORS镜像的URL(国外的太慢,改为阿里云的)。

    localRepository目录修改方式:

    默认在m2下,我们自己新建一个目录/app/maven-3.0.5/mvnrepository,重新添加一行

      <!-- localRepository
       | The path to the local repository maven will use to store artifacts.
       |
       | Default: ~/.m2/repository
      <localRepository>/path/to/local/repo</localRepository>
      -->
      <localRepository>/app/maven-3.0.5/mvnrepository</localRepository>

      依赖包镜像的下载地址URL修改方式:

    <!-- 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>
          <name>aliyun maven</name>
          <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
          <mirrorOf>central</mirrorOf> 
        </mirror>
      </mirrors>

     3. 服务器系统环境变量的设置

    1)编辑环境变量文件  vi /etc/profile

    2)添加如下变量(根据自己的安装目录设置)

    export JAVA_HOME=/app/jdk1.8.0_201
    export MAVEN_HOME=/app/maven-3.0.5
    export PATH=$JAVA_HOME/bin:$PATH:$MAVEN_HOME/bin

    3)生效环境变量,source /etc/profile

    4)验证环境变量是否生效。能正确显示版本、home路径即可。

    4.jenkins中的变量设置

    1)设置“全局工具配置”

    新增JDK设置,目录为上面讲的安装目录。(不能用系统自带的OPENJDK,不然会提示报错)

     新增MVN设置

    2)设置“系统配置”,增加环境变量,共3个,根据自己的安装目录填写。

     5. 在jenkins中新建maven项目

    1) 构建一个maven项目

     2)源码部分,根据自己的情况填写。

    3)PRE STEP部分,"ROOT POM"还是使用pom.xml文件,"Goals and options"根据maven的命令填写,具体可以看提示“Specifies the goals to execute, such as "clean install" or "deploy". This field can also accept any other command line options to Maven, such as "-e" or "-Djava.net.preferIPv4Stack=true".

    4)Post Steps我们先不填,先运行下看看是否可以编译成功。

    5)运行任务,第一次运行会下载大量的java依赖包。

         最后会出现success,说明编译成功。

         在会在maven设localRepository目录下,生成war包。

    Downloading: http://maven.aliyun.com/nexus/content/groups/public/org/apache/maven/shared/maven-filtering/1.3/maven-filtering-1.3.jar
    Downloaded: http://maven.aliyun.com/nexus/content/groups/public/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.jar (25 KB at 52.2 KB/sec)
    Downloading: http://maven.aliyun.com/nexus/content/groups/public/org/apache/maven/shared/maven-mapping/1.0/maven-mapping-1.0.jar
    Downloaded: http://maven.aliyun.com/nexus/content/groups/public/org/apache/commons/commons-compress/1.9/commons-compress-1.9.jar (370 KB at 564.8 KB/sec)
    Downloaded: http://maven.aliyun.com/nexus/content/groups/public/com/thoughtworks/xstream/xstream/1.4.4/xstream-1.4.4.jar (473 KB at 723.0 KB/sec)
    Downloaded: http://maven.aliyun.com/nexus/content/groups/public/org/codehaus/plexus/plexus-utils/3.0.20/plexus-utils-3.0.20.jar (238 KB at 686.2 KB/sec)
    Downloaded: http://maven.aliyun.com/nexus/content/groups/public/org/apache/maven/shared/maven-mapping/1.0/maven-mapping-1.0.jar (10 KB at 37.9 KB/sec)
    Downloaded: http://maven.aliyun.com/nexus/content/groups/public/org/apache/maven/shared/maven-filtering/1.3/maven-filtering-1.3.jar (50 KB at 127.8 KB/sec)
    [INFO] Packaging webapp
    [INFO] Assembling webapp [bbs] in [/var/lib/jenkins/workspace/maven_t1/target/bbs-5.7]
    [INFO] Processing war project
    [INFO] Copying webapp webResources [/var/lib/jenkins/workspace/maven_t1/lib] to [/var/lib/jenkins/workspace/maven_t1/target/bbs-5.7]
    [INFO] Copying webapp resources [/var/lib/jenkins/workspace/maven_t1/src/main/webapp]
    [INFO] Webapp assembled in [480 msecs]
    [INFO] Building war: /var/lib/jenkins/workspace/maven_t1/target/bbs-5.7.war
    [INFO] 
    [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ bbs ---
    Downloading: http://maven.aliyun.com/nexus/content/groups/public/org/codehaus/plexus/plexus-digest/1.0/plexus-digest-1.0.pom
    Downloaded: http://maven.aliyun.com/nexus/content/groups/public/org/codehaus/plexus/plexus-digest/1.0/plexus-digest-1.0.pom (2 KB at 3.9 KB/sec)
    Downloading: http://maven.aliyun.com/nexus/content/groups/public/org/codehaus/plexus/plexus-components/1.1.7/plexus-components-1.1.7.pom
    Downloaded: http://maven.aliyun.com/nexus/content/groups/public/org/codehaus/plexus/plexus-components/1.1.7/plexus-components-1.1.7.pom (5 KB at 17.0 KB/sec)
    Downloading: http://maven.aliyun.com/nexus/content/groups/public/org/codehaus/plexus/plexus/1.0.8/plexus-1.0.8.pom
    Downloaded: http://maven.aliyun.com/nexus/content/groups/public/org/codehaus/plexus/plexus/1.0.8/plexus-1.0.8.pom (8 KB at 25.2 KB/sec)
    Downloading: http://maven.aliyun.com/nexus/content/groups/public/org/codehaus/plexus/plexus-container-default/1.0-alpha-8/plexus-container-default-1.0-alpha-8.pom
    Downloaded: http://maven.aliyun.com/nexus/content/groups/public/org/codehaus/plexus/plexus-container-default/1.0-alpha-8/plexus-container-default-1.0-alpha-8.pom (8 KB at 26.6 KB/sec)
    Downloading: http://maven.aliyun.com/nexus/content/groups/public/org/codehaus/plexus/plexus-digest/1.0/plexus-digest-1.0.jar
    Downloaded: http://maven.aliyun.com/nexus/content/groups/public/org/codehaus/plexus/plexus-digest/1.0/plexus-digest-1.0.jar (12 KB at 43.7 KB/sec)
    [INFO] Installing /var/lib/jenkins/workspace/maven_t1/target/bbs-5.7.war to /app/maven-3.0.5/mvnrepository/bbs/bbs/5.7/bbs-5.7.war
    [INFO] Installing /var/lib/jenkins/workspace/maven_t1/pom.xml to /app/maven-3.0.5/mvnrepository/bbs/bbs/5.7/bbs-5.7.pom
    [INFO] [1m------------------------------------------------------------------------[m
    [INFO] [1;32mBUILD SUCCESS[m
    [INFO] [1m------------------------------------------------------------------------[m
    [INFO] Total time: 39.307 s
    [INFO] Finished at: 2022-04-13T23:04:19+08:00
    [INFO] [1m------------------------------------------------------------------------[m
    Waiting for Jenkins to finish collecting data
    [JENKINS] Archiving /var/lib/jenkins/workspace/maven_t1/pom.xml to bbs/bbs/5.7/bbs-5.7.pom
    [JENKINS] Archiving /var/lib/jenkins/workspace/maven_t1/target/bbs-5.7.war to bbs/bbs/5.7/bbs-5.7.war
    channel stopped
    Finished: SUCCESS

     

     

    更多相关内容
  • apache-maven-3.3.9

    千次下载 热门讨论 2015-12-02 15:22:47
    现在Java新架构的不断出现,例如Struts,Spring,Hibernate...为了解决上述问题,Apache开源组织 早在几年前就发布了Maven,它适用于大的Java项目。开发中国移动的项目时,记得J2EE项目组都是采用这种方式管理项目的。
  • Maven

    千次阅读 2022-04-13 12:16:31
    Maven

    1.Maven

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

    为什么要学习Maven

    1. 在javaweb开发中需要使用大量的jar包
    2. 如何能够让一个东西自动帮我们生成jar包

    1.1Maver项目架构管理工具

    Maven的核心思想:约定大于配置

    • 有约束,不要去违反

    Maven会规定好你该如何去编写我们的代码

    1.2 下载安装Maven

    在这里插入图片描述

    1.3 配置环境变量

    1. M2_HOME

    ​ D:\JavaMaven\apache-maven-3.8.5\bin

    1. MAVEN_HOME

    ​ D:\JavaMaven\apache-maven-3.8.5

    1. path

      %MAVEN_HOME%\bin

    测试Maven是否安装成功
    在这里插入图片描述

    1.4 阿里云镜像

    • 镜像 mirrors

      • 作用:加速我们的下载
    • 国内建议使用阿里云镜像

    <mirror>
          <id>alimaven</id>
          <name>aliyun maven</name>
          <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
          <mirrorOf>central</mirrorOf>        
        </mirror>
    

    1.5 本地仓库

    建立一个本地仓库: localRepository

      <localRepository>D:\JavaMaven\apache-maven-3.8.5\maven-repo</localRepository>
    

    1.6 在IDEA中使用Maven

    在这里插入图片描述

    在这里插入图片描述

    在这里插入图片描述

    1. 观察Maven仓库在多了什么东西

    2. idea中的Maven设置

      idea项目创建成功后看一眼Maven的配置

    在这里插入图片描述

    1.7 创建一个普通的Maven项目

    在这里插入图片描述

    5.8在IDEA中标记文件夹功能

    在这里插入图片描述

    1.8 标记文件夹功能

    在这里插入图片描述

    1.9 在IDEA中配置Tomcat

    在这里插入图片描述

    在这里插入图片描述

    在这里插入图片描述

    1.10 pom文件

    在这里插入图片描述

    maven由于它的约定大于配置

    展开全文
  • 最新版本apache-maven-3.5.0下载

    千次下载 热门讨论 2017-04-14 13:53:23
    apache-maven-3.5.0
  • 阿里云的maven私服的setting.xml 工具

    千次下载 热门讨论 2016-12-27 16:46:34
    这是我配置阿里云的maven私服的setting.xml文件,MirroOf配置不是*号,是central,这样在项目pom中配置repository依然生效
  • Maven官网下载

    千次下载 热门讨论 2014-08-25 23:01:51
    Maven 资源,从官方下载的,使用于windows
  • 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安装与配置

    万次阅读 多人点赞 2021-04-20 22:38:12
    安装Maven 官网下载maven Binary是可执行版本,已经编译好可以直接使用。 Source是源代码版本,需要自己编译成可执行软件才可使用。 tar.gz和zip两种压缩格式,其实这两个压缩文件里面包含的内容是同样的,只是...

    一、安装Maven

    1. 官网下载maven

    Binary是可执行版本,已经编译好可以直接使用。
    Source是源代码版本,需要自己编译成可执行软件才可使用。

    tar.gz和zip两种压缩格式,其实这两个压缩文件里面包含的内容是同样的,只是压缩格式不同
    tar.gz格式的文件比zip文件小很多,用于unix操作系统。
    zip格式用于Windows操作系统,但在Windows系统使用WinRar工具一样能够解压缩tar.gz格式

    1. 下载完成后,解压到某一路径下。本文以E:\Tools\Maven\apache-maven-3.8.1为例,实际配置环境变量时以自己安装的路径为准

    二、配置环境变量

    1. 右键此电脑–>属性–>高级系统设置–>环境变量
    2. 新建变量MAVEN_HOME = E:\Tools\Maven\apache-maven-3.8.1(以自己的安装路径为准)
    3. 编辑变量Path,添加变量值%MAVEN_HOME%\bin
    4. 然后win+R运行cmd,输入mvn -version,如图所示则配置成功

    三、配置本地仓库

    1. 在E:\Tools\Maven\路径下新建maven-repository文件夹,用作maven的本地库。
      在这里插入图片描述

    2. 在路径E:\Tools\Maven\apache-maven-3.8.1\conf下找到settings.xml文件

    3. 找到节点localRepository,在注释外添加

    <localRepository>E:\Tools\Maven\maven-repository</localRepository>
    

    在这里插入图片描述

    localRepository节点用于配置本地仓库,本地仓库其实起到了一个缓存的作用,它的默认地址是 C:\Users\用户名.m2。
    当我们从maven中获取jar包的时候,maven首先会在本地仓库中查找,如果本地仓库有则返回;如果没有则从远程仓库中获取包,并在本地库中保存。
    此外,我们在maven项目中运行mvn install,项目将会自动打包并安装到本地仓库中。

    四、配置镜像

    1. 在settings.xml配置文件中找到mirrors节点
    2. 添加如下配置(注意要添加在<mirrors>和</mirrors>两个标签之间,其它配置同理)
    <!-- 阿里云仓库 -->
    <mirror>
    	<id>alimaven</id>
    	<mirrorOf>central</mirrorOf>
    	<name>aliyun maven</name>
    	<url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
    </mirror>
    

    在这里插入图片描述

    因为国外的服务器下载jar包很慢所以我们改为阿里云服务器

    虽然mirrors可以配置多个子节点,但是它只会使用其中的一个节点,即默认情况下配置多个mirror的情况下,只有第一个生效,只有当前一个mirror无法连接的时候,才会去找后一个;而我们想要的效果是:当a.jar在第一个mirror中不存在的时候,maven会去第二个mirror中查询下载,但是maven不会这样做!

    五、配置JDK

    1. 在settings.xml配置文件中找到profiles节点
    2. 添加如下配置
    <!-- 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>
    

    在这里插入图片描述


    配置完成,win+R运行cmd,输入mvn help:system测试,配置成功则本地仓库(E:\Tools\Maven\maven-repository)中会出现一些文件
    在这里插入图片描述

    首次执行 mvn help:system 命令,Maven相关工具自动帮我们到Maven中央仓库下载缺省的或者Maven中央仓库更新的各种配置文件和类库(jar包)到Maven本地仓库中。
    下载完各种文件后, mvn help:system 命令会打印出所有的Java系统属性和环境变量,这些信息对我们日常的编程工作很有帮助。

    若需要IDEA配置Maven,请参考 https://blog.csdn.net/qq_38190185/article/details/115943152?spm=1001.2014.3001.5501

    附录

    完整的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.2.0"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
              xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 http://maven.apache.org/xsd/settings-1.2.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>E:\Tools\Maven\maven-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>
    	
        <mirror>
          <id>maven-default-http-blocker</id>
          <mirrorOf>external:http:*</mirrorOf>
          <name>Pseudo repository to mirror external repositories initially using HTTP.</name>
          <url>http://0.0.0.0/</url>
          <blocked>true</blocked>
        </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>
      
    	<!-- 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>
    	
        <!-- 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>
        -->
      </profiles>
    
      <!-- activeProfiles
       | List of profiles that are active for all builds.
       |
      <activeProfiles>
        <activeProfile>alwaysActiveProfile</activeProfile>
        <activeProfile>anotherAlwaysActiveProfile</activeProfile>
      </activeProfiles>
      -->
    </settings>
    

    References

    https://blog.csdn.net/a805814077/article/details/100545928
    https://blog.csdn.net/github_37759996/article/details/90748461
    https://www.cnblogs.com/Lints/p/11163073.html

    展开全文
  • eclipse maven插件包

    千次下载 热门讨论 2014-03-27 13:19:31
    eclipse maven插件。 因在线安装地址出错,虽然可以去eclipse market中搜到,但有时版本问题,而安装失败。 该文件可以直接copy到eclipse直接子目录下,覆盖原来的plugin和feature文件夹。 不过推荐使用link...
  • Maven配置教程

    万次阅读 多人点赞 2018-08-26 17:20:22
    Maven配置 Maven项目对象模型(POM),可以通过一小段描述信息来管理项目的构建,报告和文档的软件项目管理工具。 Maven 的配置却让一些初学者望而却步,这里我就把Maven的详细配置过程写下,希望能对你有所帮助...
  • maven jar包

    千次下载 热门讨论 2014-08-05 14:43:33
    maven-aether-provider-3.2.1-sources.jar maven-antrun-plugin-1.3.jar maven-archiver-2.2.jar maven-artifact-3.2.1-sources.jar maven-assembly-plugin-2.2-beta-5.jar maven-bundle-plugin-1.0.0.jar maven-...
  • apache-maven-3.0.3

    千次下载 热门讨论 2012-03-10 01:00:15
    将下载好的apache-maven-3.0.3解压缩后,配置Path环境变量即可。需要注意的是,安装Maven的机器上,需要JDK环境,并且JAVA_HOME环境变量的配置无误。 输入mvn –v命令,若显示如下的版本信息,说明已经OK了。 ...
  • IDEA配置Maven

    万次阅读 多人点赞 2022-01-02 18:27:51
    文章目录一、Maven下载&环境配置1.下载Maven2.解压3.配置环境变量4.测试二、更改Maven中的设置1.编辑settings.xml2.配置本地仓库3.更换默认更新源4.添加JDK的版本三、在IDEA中配置Maven1. 打开IDEA,新建一个空...
  • Maven安装与配置,Idea配置Maven

    万次阅读 多人点赞 2021-11-16 13:26:29
    一、安装本地Maven 官网下载传送门 1.我使用的是3.6.1版本 maven-3.6.1-bin.zip 二、安装 把下载好的maven压缩包解压到一个没有中文,空格或其他特殊字符的文件夹,如: 三、配置环境变量 1.右键此电脑->属性-&...
  • Maven详细安装教程

    万次阅读 多人点赞 2022-03-11 10:21:52
    Maven – Download Apache Mavenhttps://maven.apache.org/download.cgi 二、配置环境变量 新建 系统变量 变量名:MAVEN_HOME 值:你解压的路径 eg:D:\xxx\apache-maven-3.8.4 编辑 系统变量 Path 打开 -...
  • Maven入门---如何在idea中配置Maven

    千次阅读 多人点赞 2022-03-15 20:07:36
    Maven入门---如何在idea中配置Maven一、下载Maven二、配置环境变量三、配置本地仓库四、配置镜像五、配置统一的JDK六、创建Maven项目七、Maven项目变为Web项目 一、下载Maven Maven官网:...
  • IDEA Maven 依赖分析插件Maven Helper

    千次阅读 2022-04-20 01:48:44
    IDEA 安装Maven Helper插件 1、打开setting,找到Plugins选项(安装Maven Helper 插件(如果有就跳过这一步)) 检索:Maven Helper 安装成功后,重新启动IDEA编辑器 2、使用Maven Helper 当Maven Helper 插件...
  • maven仓库

    千次阅读 2021-11-04 20:44:42
    1. 为什么使用maven? 2. 什么是maven? 3. 如何使用maven?
  • 使用Maven构建Spring MVC项目的简单示例

    千次下载 热门讨论 2013-09-29 12:31:42
    本人博客里面“使用Maven构建Spring MVC项目的简单示例”的源代码
  • Maven仓库介绍

    万次阅读 2022-01-29 13:33:45
    介绍了Maven仓库的基本概念。
  • Mac 配置maven

    千次阅读 2022-03-26 00:46:09
    首先你需要在maven官网上下载mac专用的二进制maven压缩包。也就是下图的这个: 下载好之后,请不要着急,为了之后这个包不会被你一不小心删掉,可以把它放在一个你平时碰不到的地方。 然后,开始我们的配置。 1、...
  • Maven环境配置

    千次阅读 2022-04-28 14:19:17
    maven安装及配置
  • 史上最详细的Maven安装教程

    万次阅读 多人点赞 2022-02-14 22:12:54
    本文须知:安装maven环境之前要先安装javajdk环境(没有安装java环境的可以先去看安装JAVA环境的教程)Maven 3.3+ require JDK 1.7及以上。 第一步:下载maven(本教程安装的是3.8.4) 官方下载链接:...
  • 通过MAVEN安装Spark、&& EclipseIDE

    万次阅读 2022-03-25 10:40:40
    Spark Installation with Maven & Eclipse IDE 文章目录Spark Installation with Maven & Eclipse IDE安装说明Maven & Eclipse IDE说明参考网站安装过程JDK安装Eclipse IDE安装Maven安装Spark安装新建...
  • linux 安装 maven

    千次阅读 多人点赞 2022-04-01 16:48:19
    在 linux 上安装 maven,步骤如下 笔者这里使用 centos7,apache-maven-3.8.5 安装 maven 环境前,需要先安装 java 环境,笔者这里已经成功安装 java 环境,如果没有安装 java 环境,可以参考:...
  • apache-maven-3.2.1 官方绿色安装包

    千次下载 热门讨论 2015-12-14 19:27:07
    apache-maven-3.2.1安装包,解压可用。Maven是一个项目管理工具,它包含了一个项目对象模型 (Project Object Model),一组标准集合,一个项目生命周期(Project Lifecycle),一个依赖管理系统(Dependency Management ...
  • apache-maven-3.3.9 最新下载

    千次下载 热门讨论 2015-11-22 15:45:53
    Maven是基于项目对象模型(POM),可以通过一小段描述信息来管理项目的构建,报告和文档的软件项目管理工具。 Maven 除了以程序构建能力为特色之外,还提供高级项目管理工具。由于 Maven 的缺省构建规则有较高的可重用...
  • Maven的下载和安装

    千次阅读 2022-03-21 17:31:46
    一、什么是maven? Apache Maven是个项目管理和自动构建工具,基于项目对象模型(POM)的概念。 作用:完成项目的相关操作,如:编译,构建,单元测试,安装,网站生成和基于Maven部署项目。 二、Maven的安装与...
  • 直接使用阿里云镜像仓库打包没问题,替换为私服镜像仓库后报错: 就是pom.xml中的plugin报错 ``` org.apache.maven.plugins maven-compiler-plugin 3.5 1.8 1.8 UTF-8 ``` 网上找了半天说这个指定的jdk版本的问题,...
  • maven命令行打包

    千次阅读 2021-12-10 15:03:41
    maven打包项目到远程仓库maven项目打包命令行maven打包本地资源文件夹使用命令行打包(maven)功能快捷键合理的创建标题,有助于目录的生成如何改变文本的样式插入链接与图片如何插入一段漂亮的代码片生成一个适合你的...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 1,095,564
精华内容 438,225
关键字:

maven

友情链接: Indicators.rar