settings.xml

推荐使用华为云，不限速

  1. <?xml version="1.0" encoding="UTF-8"?>
  3. <!--
  4. Licensed to the Apache Software Foundation (ASF) under one
  5. or more contributor license agreements.  See the NOTICE file
  6. distributed with this work for additional information
  7. regarding copyright ownership.  The ASF licenses this file
  8. to you under the Apache License, Version 2.0 (the
  9. "License"); you may not use this file except in compliance
  10. with the License.  You may obtain a copy of the License at
  12.     http://www.apache.org/licenses/LICENSE-2.0
  14. Unless required by applicable law or agreed to in writing,
  15. software distributed under the License is distributed on an
  16. "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  17. KIND, either express or implied.  See the License for the
  18. specific language governing permissions and limitations
  19. under the License.
  20. -->
  22. <!--
  23.  | This is the configuration file for Maven. It can be specified at two levels:
  24.  |
  25.  |  1. User Level. This settings.xml file provides configuration for a single user,
  26.  |                 and is normally provided in ${user.home}/.m2/settings.xml.
  27.  |
  28.  |                 NOTE: This location can be overridden with the CLI option:
  29.  |
  30.  |                 -s /path/to/user/settings.xml
  31.  |
  32.  |  2. Global Level. This settings.xml file provides configuration for all Maven
  33.  |                 users on a machine (assuming they're all using the same Maven
  34.  |                 installation). It's normally provided in
  35.  |                 ${maven.conf}/settings.xml.
  36.  |
  37.  |                 NOTE: This location can be overridden with the CLI option:
  38.  |
  39.  |                 -gs /path/to/global/settings.xml
  40.  |
  41.  | The sections in this sample file are intended to give you a running start at
  42.  | getting the most out of your Maven installation. Where appropriate, the default
  43.  | values (values used when the setting is not specified) are provided.
  44.  |
  45.  |-->
  46. <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  47.           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  48.           xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  49.   <!-- localRepository
  50.    | The path to the local repository maven will use to store artifacts.
  51.    |
  52.    | Default: ${user.home}/.m2/repository
  53.   <localRepository>/path/to/local/repo</localRepository>
  54.   -->
  56.   <!-- interactiveMode
  57.    | This will determine whether maven prompts you when it needs input. If set to false,
  58.    | maven will use a sensible default value, perhaps based on some other setting, for
  59.    | the parameter in question.
  60.    |
  61.    | Default: true
  62.   <interactiveMode>true</interactiveMode>
  63.   -->
  65.   <!-- offline
  66.    | Determines whether maven should attempt to connect to the network when executing a build.
  67.    | This will have an effect on artifact downloads, artifact deployment, and others.
  68.    |
  69.    | Default: false
  70.   <offline>false</offline>
  71.   -->
  73.   <!-- pluginGroups
  74.    | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
  75.    | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
  76.    | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
  77.    |-->
  78.   <pluginGroups>
  79.     <!-- pluginGroup
  80.      | Specifies a further group identifier to use for plugin lookup.
  81.     <pluginGroup>com.your.plugins</pluginGroup>
  82.     -->
  83.   </pluginGroups>
  85.   <!-- proxies
  86.    | This is a list of proxies which can be used on this machine to connect to the network.
  87.    | Unless otherwise specified (by system property or command-line switch), the first proxy
  88.    | specification in this list marked as active will be used.
  89.    |-->
  90.   <proxies>
  91.     <!-- proxy
  92.      | Specification for one proxy, to be used in connecting to the network.
  93.      |
  94.     <proxy>
  95.       <id>optional</id>
  96.       <active>true</active>
  97.       <protocol>http</protocol>
  98.       <username>proxyuser</username>
  99.       <password>proxypass</password>
  100.       <host>proxy.host.net</host>
  101.       <port>80</port>
  102.       <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
  103.     </proxy>
  104.     -->
  105.   </proxies>
  107.   <!-- servers
  108.    | This is a list of authentication profiles, keyed by the server-id used within the system.
  109.    | Authentication profiles can be used whenever maven must make a connection to a remote server.
  110.    |-->
  111.   <servers>
  112.     <!-- server
  113.      | Specifies the authentication information to use when connecting to a particular server, identified by
  114.      | a unique name within the system (referred to by the 'id' attribute below).
  115.      |
  116.      | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
  117.      |       used together.
  118.      |
  119.     <server>
  120.       <id>deploymentRepo</id>
  121.       <username>repouser</username>
  122.       <password>repopwd</password>
  123.     </server>
  124.     -->
  126.     <!-- Another sample, using keys to authenticate.
  127.     <server>
  128.       <id>siteServer</id>
  129.       <privateKey>/path/to/private/key</privateKey>
  130.       <passphrase>optional; leave empty if not used.</passphrase>
  131.     </server>
  132.     -->
  133.   </servers>
  135.   <!-- mirrors
  136.    | This is a list of mirrors to be used in downloading artifacts from remote repositories.
  137.    |
  138.    | It works like this: a POM may declare a repository to use in resolving certain artifacts.
  139.    | However, this repository may have problems with heavy traffic at times, so people have mirrored
  140.    | it to several places.
  141.    |
  142.    | That repository definition will have a unique id, so we can create a mirror reference for that
  143.    | repository, to be used as an alternate download site. The mirror site will be the preferred
  144.    | server for that repository.
  145.    |-->
  146.   <mirrors>
  147.     <mirror>
  148.       <id>huaweicloud</id>
  149.       <mirrorOf>*</mirrorOf>
  150.       <url>https://repo.huaweicloud.com/repository/maven/</url>
  151.     </mirror>
  153.     <!-- mirror
  154.      | Specifies a repository mirror site to use instead of a given repository. The repository that
  155.      | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
  156.      | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
  157.      |
  158.     <mirror>
  159.       <id>mirrorId</id>
  160.       <mirrorOf>repositoryId</mirrorOf>
  161.       <name>Human Readable Name for this Mirror.</name>
  162.       <url>http://my.repository.com/repo/path</url>
  163.     </mirror>
  164.      -->
  165.   </mirrors>
  167.   <!-- profiles
  168.    | This is a list of profiles which can be activated in a variety of ways, and which can modify
  169.    | the build process. Profiles provided in the settings.xml are intended to provide local machine-
  170.    | specific paths and repository locations which allow the build to work in the local environment.
  171.    |
  172.    | For example, if you have an integration testing plugin - like cactus - that needs to know where
  173.    | your Tomcat instance is installed, you can provide a variable here such that the variable is
  174.    | dereferenced during the build process to configure the cactus plugin.
  175.    |
  176.    | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
  177.    | section of this document (settings.xml) - will be discussed later. Another way essentially
  178.    | relies on the detection of a system property, either matching a particular value for the property,
  179.    | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
  180.    | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
  181.    | Finally, the list of active profiles can be specified directly from the command line.
  182.    |
  183.    | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
  184.    |       repositories, plugin repositories, and free-form properties to be used as configuration
  185.    |       variables for plugins in the POM.
  186.    |
  187.    |-->
  188.   <profiles>
  189.     <!-- profile
  190.      | Specifies a set of introductions to the build process, to be activated using one or more of the
  191.      | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
  192.      | or the command line, profiles have to have an ID that is unique.
  193.      |
  194.      | An encouraged best practice for profile identification is to use a consistent naming convention
  195.      | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
  196.      | This will make it more intuitive to understand what the set of introduced profiles is attempting
  197.      | to accomplish, particularly when you only have a list of profile id's for debug.
  198.      |
  199.      | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
  200.     <profile>
  201.       <id>jdk-1.4</id>
  203.       <activation>
  204.         <jdk>1.4</jdk>
  205.       </activation>
  207.       <repositories>
  208.         <repository>
  209.           <id>jdk14</id>
  210.           <name>Repository for JDK 1.4 builds</name>
  211.           <url>http://www.myhost.com/maven/jdk14</url>
  212.           <layout>default</layout>
  213.           <snapshotPolicy>always</snapshotPolicy>
  214.         </repository>
  215.       </repositories>
  216.     </profile>
  217.     -->
  219.     <!--
  220.      | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
  221.      | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
  222.      | might hypothetically look like:
  223.      |
  224.      | ...
  225.      | <plugin>
  226.      |   <groupId>org.myco.myplugins</groupId>
  227.      |   <artifactId>myplugin</artifactId>
  228.      |
  229.      |   <configuration>
  230.      |     <tomcatLocation>${tomcatPath}</tomcatLocation>
  231.      |   </configuration>
  232.      | </plugin>
  233.      | ...
  234.      |
  235.      | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
  236.      |       anything, you could just leave off the <value/> inside the activation-property.
  237.      |
  238.     <profile>
  239.       <id>env-dev</id>
  241.       <activation>
  242.         <property>
  243.           <name>target-env</name>
  244.           <value>dev</value>
  245.         </property>
  246.       </activation>
  248.       <properties>
  249.         <tomcatPath>/path/to/tomcat/instance</tomcatPath>
  250.       </properties>
  251.     </profile>
  252.     -->
  253.   </profiles>
  255.   <!-- activeProfiles
  256.    | List of profiles that are active for all builds.
  257.    |
  258.   <activeProfiles>
  259.     <activeProfile>alwaysActiveProfile</activeProfile>
  260.     <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  261.   </activeProfiles>
  262.   -->
  263. </settings>

多模块

多模块项目是由一个root模块和多个子模块构成；对于 root 模块，其配置项大概类似如下：

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <project xmlns="http://maven.apache.org/POM/4.0.0"
  3.          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  4.          xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  5.     <modelVersion>4.0.0</modelVersion>
  7.     <groupId>com.example</groupId>
  8.     <artifactId>test-platform</artifactId>
  9.     <version>1.0-SNAPSHOT</version>
  11.     <properties>
  12.         <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  13.         <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
  14.     </properties>
  16.     <packaging>pom</packaging>
  17.     <modules>
  18.         <module>gateway</module>
  19.     </modules>
  21. </project>

我们只需要关注第7行开始的代码片段。

<groupId> ， <artifactId> ， <version> 声明了 root 模块的相关信息，子模块则不同：

  1. <parent>
  2.   <groupId>com.zeta</groupId>
  3.   <artifactId>test-platform</artifactId>
  4.   <version>1.0-SNAPSHOT</version>
  5. </parent>
  7. <artifactId>gateway</artifactId>

我们发现，子模块不再声明<groupId> 和 <version>了，原因其实很简单：父模块已经声明了组织id和版本信息，子模块与它一样，不需要重复声明，只需要通过 <parent> 标签告诉maven子模块与父模块之间的关系即可。
子模块的 <parent>告诉我们它的父模块是 test-platform ，那父模块呢，怎么知道它有哪些子模块？显然，是 <modules> 标签告诉我们一个module都有哪些子模块。
父模块可以有子模块，子模块也可以有自己的子模块，可以无限嵌套。在父模块中声明的变量信息，如 <properties> ，子模块中就不需要再声明了，同理，依赖也是。

依赖打包

maven-shade-plugin 可以将整个maven工程源代码包括其依赖打成一个jar包，只需在 pom.xml 配置：

  1. <build>
  2.     <plugins>
  3.         <plugin>
  4.             <groupId>org.apache.maven.plugins</groupId>
  5.             <artifactId>maven-shade-plugin</artifactId>
  6.             <version>3.2.1</version>
  7.             <configuration>
  8.                 <createDependencyReducedPom>false</createDependencyReducedPom>
  9.                 <filters>
  10.                     <filter>
  11.                         <artifact>*:*</artifact>
  12.                         <excludes>
  13.                             <exclude>META-INF/*.SF</exclude>
  14.                             <exclude>META-INF/*.DSA</exclude>
  15.                             <exclude>META-INF/*.RSA</exclude>
  16.                         </excludes>
  17.                     </filter>
  18.                 </filters>
  19.             </configuration>
  20.             <executions>
  21.                 <execution>
  22.                     <phase>package</phase>
  23.                     <goals>
  24.                         <goal>shade</goal>
  25.                     </goals>
  26.                     <configuration>
  27.                         <transformers>
  28.                             <transformer
  29.                                     implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/>
  30.                             <transformer
  31.                                     implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
  32.                                 <mainClass>com.example.Main</mainClass>
  33.                             </transformer>
  34.                         </transformers>
  35.                     </configuration>
  36.                 </execution>
  37.             </executions>
  38.         </plugin>
  39.     </plugins>
  40. </build>

对于不同的项目，只需要将 <mainClass> 内容更改为项目的运行主类（包含main方法的类）。

打包过程

  • 点击运行配置，选择Edit Configurations

image.png

  • 在弹出窗口点击「➕」，选择 Maven

image.png

  • 在 Command Line 输入 package

image.png

  • 点击 OK 保存配置，在主界面运行

image.png

  • 生成的jar包在 target 目录下，会生成两个jar包，运行项目名开头的jar包，运行命令如下：

把 example.jar 替换成你自己的jar包即可运行

  1. java -jar example.jar

打包乱码/打包UTF-8编码警告

在 pom.xml 中添加：

  1. <properties>
  2.   <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  3. </properties>

SLF4J: Failed to load class

运行jar包时报如上错误，可在 pom.xml 中添加依赖：

  1. <dependency>
  2.   <groupId>org.slf4j</groupId>
  3.   <artifactId>slf4j-simple</artifactId>
  4.   <version>1.7.21</version>
  5. </dependency>

参考