maven setting.xml配置
参考:https://blog.51cto.com/u_15344989/5006930
-
<servers>
:这部分用于配置 Maven 服务器信息,包括仓库的认证信息。在你的配置中有两个服务器配置:sy-releases
:ID为sy-releases
的服务器,用户名为sy_dev
,密码为26217d52-a8a8-41d6-86d6-ae2586329500
。sy-snapshot
:ID为sy-snapshot
的服务器,用户名为sy_dev
,密码为26217d52-a8a8-41d6-86d6-ae2586329500
。
-
<mirrors>
:这部分定义了镜像配置,用于指示 Maven 在下载依赖时使用哪个镜像地址。每个<mirror>
元素包括以下信息:id
:镜像的唯一标识符。name
:镜像的名称。url
:镜像的地址。mirrorOf
:指定该镜像用于代理哪个仓库。repository的id对应
在你的配置中有两个镜像配置:
alimaven
:用于代理 Maven 中央仓库(central
)的阿里云镜像。sy-releases
和sy-snapshot
:分别用于代理sy-releases
和sy-snapshot
这两个仓库的镜像。
-
<profiles>
:这部分定义了 Maven 的 profile(配置文件),可以根据不同的环境激活不同的配置。每个<profile>
元素包括以下信息:id
:配置文件的唯一标识符。repositories
:定义了该配置文件下需要使用的仓库信息。
在你的配置中有以下几个 profile:
nexus-profile
:定义了两个仓库sy-releases
和sy-snapshot
的地址,并指定了是否允许快照和发布版本。rw
和uat
:这两个配置文件定义了不同环境下的配置属性,比如 Nacos 的地址、用户名、密码等信息。
-
<activeProfiles>
:这部分指定了当前激活的 profile,即默认生效的配置文件。在你的配置中激活了nexus-profile
这个配置文件。 profile 默认一直处于激活状态
activeProfile指定的profile默认一直处于激活状态。mvn clean install -P dev_env,test_evn,mvn命令的-P指定激活profile不影响activeProfile
mvn常用命令
mvn clean package -P rw -s /data/rw_dev/settings.xml
-P 指定profile
-s 指定settings配置文件
配置示例
<?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>/root/.m2/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> <id>sy-releases</id> <username>sy_dev</username> <password>26217d52-a8a8-41d6-86d6-ae2586329500</password> </server> <server> <id>sy-snapshot</id> <username>sy_dev</username> <password>26217d52-a8a8-41d6-86d6-ae2586329500</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> <id>alimaven</id> <name>aliyun maven</name> <url>http://maven.aliyun.com/nexus/content/groups/public/</url> <mirrorOf>central</mirrorOf> </mirror> <mirror> <id>sy-releases</id> <name>sy nexus repository</name> <url>http://nexus.seewintech.com/repository/maven-releases/</url> <mirrorOf>sy-releases</mirrorOf> </mirror> <mirror> <id>sy-snapshot</id> <name>sy nexus snapshot repository</name> <url>http://nexus.seewintech.com/repository/maven-snapshots/</url> <mirrorOf>sy-snapshot</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> <id>nexus-profile</id> <repositories> <repository> <id>sy-releases</id> <name>sy nexus repository</name> <url>http://nexus.seewintech.com/repository/maven-releases/</url> <snapshots> <enabled>false</enabled> <updatePolicy>always</updatePolicy> </snapshots> <releases> <enabled>true</enabled> <updatePolicy>always</updatePolicy> </releases> </repository> <repository> <id>sy-snapshot</id> <name>sy nexus snapshot repository</name> <url>http://nexus.seewintech.com/repository/maven-snapshots/</url> <snapshots> <enabled>true</enabled> <updatePolicy>always</updatePolicy> </snapshots> <releases> <enabled>false</enabled> <updatePolicy>always</updatePolicy> </releases> </repository> <repository> <id>nexus-maven</id> <name>nexus-maven-name</name> <url>https://oss.sonatype.org/content/repositories/releases/</url> </repository> </repositories> </profile> <!-- 多环境配置方案 --> <profile> <!-- 本地环境--> <id>rw</id> <properties> <config.profiles.active>rw</config.profiles.active> <config.nacos.discovery>192.168.1.227:8848</config.nacos.discovery> <config.nacos.config>192.168.1.227:8848</config.nacos.config> <config.nacos.username>nacos</config.nacos.username> <config.nacos.password>nacos</config.nacos.password> <config.nacos.namespace>0e90b8c1-17ce-4b78-8a40-6db598f928ff</config.nacos.namespace> <config.nacos.dubbo.namespace>f8a077e0-c9ae-4dbc-8768-53266355fea6</config.nacos.dubbo.namespace> </properties> <!-- 默认开启这个配置 --> <activation> <activeByDefault>true</activeByDefault> </activation> </profile> <profile> <!-- 本地环境--> <id>uat</id> <properties> <config.profiles.active>uat</config.profiles.active> <config.nacos.discovery>192.168.1.227:8848</config.nacos.discovery> <config.nacos.config>192.168.1.227:8848</config.nacos.config> <config.nacos.username>nacos</config.nacos.username> <config.nacos.password>nacos</config.nacos.password> <config.nacos.namespace>435d345c-4e1d-4bd7-b77f-004ae0debfef</config.nacos.namespace> <config.nacos.dubbo.namespace>a172ada1-5d3b-433a-a1bc-124e361ade2a</config.nacos.dubbo.namespace> </properties> </profile> </profiles> <activeProfiles> <activeProfile>nexus-profile</activeProfile> </activeProfiles> </settings>