settings.xml配置

原文

  1. <?xml version="1.0" encoding="UTF-8"?>
  2.  
  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
  11.  
  12. http://www.apache.org/licenses/LICENSE-2.0
  13.  
  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. -->
  21.  
  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. -->
  55. <localRepository>
  56. D:/apache-maven-3.5.2/repository
  57. </localRepository>
  58.  
  59. <!-- interactiveMode
  60. | This will determine whether maven prompts you when it needs input. If set to false,
  61. | maven will use a sensible default value, perhaps based on some other setting, for
  62. | the parameter in question.
  63. |
  64. | Default: true
  65. <interactiveMode>true</interactiveMode>
  66. -->
  67.  
  68. <!-- offline
  69. | Determines whether maven should attempt to connect to the network when executing a build.
  70. | This will have an effect on artifact downloads, artifact deployment, and others.
  71. |
  72. | Default: false
  73. <offline>false</offline>
  74. -->
  75.  
  76. <!-- pluginGroups
  77. | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
  78. | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
  79. | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
  80. |-->
  81. <pluginGroups>
  82. <!-- pluginGroup
  83. | Specifies a further group identifier to use for plugin lookup.
  84. <pluginGroup>com.your.plugins</pluginGroup>
  85. -->
  86. </pluginGroups>
  87.  
  88. <!-- proxies
  89. | This is a list of proxies which can be used on this machine to connect to the network.
  90. | Unless otherwise specified (by system property or command-line switch), the first proxy
  91. | specification in this list marked as active will be used.
  92. |-->
  93. <proxies>
  94. <!-- proxy
  95. | Specification for one proxy, to be used in connecting to the network.
  96. |
  97. <proxy>
  98. <id>optional</id>
  99. <active>true</active>
  100. <protocol>http</protocol>
  101. <username>proxyuser</username>
  102. <password>proxypass</password>
  103. <host>proxy.host.net</host>
  104. <port>80</port>
  105. <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
  106. </proxy>
  107. -->
  108. </proxies>
  109.  
  110. <!-- servers
  111. | This is a list of authentication profiles, keyed by the server-id used within the system.
  112. | Authentication profiles can be used whenever maven must make a connection to a remote server.
  113. |-->
  114. <servers>
  115. <!-- server
  116. | Specifies the authentication information to use when connecting to a particular server, identified by
  117. | a unique name within the system (referred to by the 'id' attribute below).
  118. |
  119. | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
  120. | used together.
  121. |
  122. <server>
  123. <id>deploymentRepo</id>
  124. <username>repouser</username>
  125. <password>repopwd</password>
  126. </server>
  127. -->
  128.  
  129. <!-- Another sample, using keys to authenticate.
  130. <server>
  131. <id>siteServer</id>
  132. <privateKey>/path/to/private/key</privateKey>
  133. <passphrase>optional; leave empty if not used.</passphrase>
  134. </server>
  135. -->
  136. </servers>
  137.  
  138. <!-- mirrors
  139. | This is a list of mirrors to be used in downloading artifacts from remote repositories.
  140. |
  141. | It works like this: a POM may declare a repository to use in resolving certain artifacts.
  142. | However, this repository may have problems with heavy traffic at times, so people have mirrored
  143. | it to several places.
  144. |
  145. | That repository definition will have a unique id, so we can create a mirror reference for that
  146. | repository, to be used as an alternate download site. The mirror site will be the preferred
  147. | server for that repository.
  148. |-->
  149. <mirrors>
  150. <!-- mirror
  151. | Specifies a repository mirror site to use instead of a given repository. The repository that
  152. | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
  153. | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
  154. |
  155. <mirror>
  156. <id>mirrorId</id>
  157. <mirrorOf>repositoryId</mirrorOf>
  158. <name>Human Readable Name for this Mirror.</name>
  159. <url>http://my.repository.com/repo/path</url>
  160. </mirror>
  161. -->
  162. <mirror>
  163. <id>alimaven</id>
  164. <name>aliyun maven</name>
  165. <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
  166. <mirrorOf>central</mirrorOf>
  167. </mirror>
  168.  
  169. </mirrors>
  170.  
  171. <!-- profiles
  172. | This is a list of profiles which can be activated in a variety of ways, and which can modify
  173. | the build process. Profiles provided in the settings.xml are intended to provide local machine-
  174. | specific paths and repository locations which allow the build to work in the local environment.
  175. |
  176. | For example, if you have an integration testing plugin - like cactus - that needs to know where
  177. | your Tomcat instance is installed, you can provide a variable here such that the variable is
  178. | dereferenced during the build process to configure the cactus plugin.
  179. |
  180. | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
  181. | section of this document (settings.xml) - will be discussed later. Another way essentially
  182. | relies on the detection of a system property, either matching a particular value for the property,
  183. | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
  184. | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
  185. | Finally, the list of active profiles can be specified directly from the command line.
  186. |
  187. | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
  188. | repositories, plugin repositories, and free-form properties to be used as configuration
  189. | variables for plugins in the POM.
  190. |
  191. |-->
  192. <profiles>
  193. <!-- profile
  194. | Specifies a set of introductions to the build process, to be activated using one or more of the
  195. | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
  196. | or the command line, profiles have to have an ID that is unique.
  197. |
  198. | An encouraged best practice for profile identification is to use a consistent naming convention
  199. | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
  200. | This will make it more intuitive to understand what the set of introduced profiles is attempting
  201. | to accomplish, particularly when you only have a list of profile id's for debug.
  202. |
  203. | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
  204. <profile>
  205. <id>jdk-1.4</id>
  206.  
  207. <activation>
  208. <jdk>1.4</jdk>
  209. </activation>
  210.  
  211. <repositories>
  212. <repository>
  213. <id>jdk14</id>
  214. <name>Repository for JDK 1.4 builds</name>
  215. <url>http://www.myhost.com/maven/jdk14</url>
  216. <layout>default</layout>
  217. <snapshotPolicy>always</snapshotPolicy>
  218. </repository>
  219. </repositories>
  220. </profile>
  221. -->
  222.  
  223. <!--
  224. | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
  225. | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
  226. | might hypothetically look like:
  227. |
  228. | ...
  229. | <plugin>
  230. | <groupId>org.myco.myplugins</groupId>
  231. | <artifactId>myplugin</artifactId>
  232. |
  233. | <configuration>
  234. | <tomcatLocation>${tomcatPath}</tomcatLocation>
  235. | </configuration>
  236. | </plugin>
  237. | ...
  238. |
  239. | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
  240. | anything, you could just leave off the <value/> inside the activation-property.
  241. |
  242. <profile>
  243. <id>env-dev</id>
  244.  
  245. <activation>
  246. <property>
  247. <name>target-env</name>
  248. <value>dev</value>
  249. </property>
  250. </activation>
  251.  
  252. <properties>
  253. <tomcatPath>/path/to/tomcat/instance</tomcatPath>
  254. </properties>
  255. </profile>
  256. -->
  257. </profiles>
  258.  
  259. <!-- activeProfiles
  260. | List of profiles that are active for all builds.
  261. |
  262. <activeProfiles>
  263. <activeProfile>alwaysActiveProfile</activeProfile>
  264. <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  265. </activeProfiles>
  266. -->
  267. </settings>

该settings.xml位于maven文件夹中的conf文件夹下

简介

略过第一段注释(全是废话),看第二段注释

如第二段注释所说,配置有2处:用户配置和全局配置

用户配置路径为${user.home}/.m2/settings.xml,该配置需用户自行创建

全局配置路径为${maven.conf}/settings.xml,该配置为maven自带配置,即原文所在位置

当两者都存在时,maven会合并这2个配置;有相同配置参数时,有效值为用户配置中的参数

看完开头的介绍后,可以开始看配置的正文部分了,为方便查看,先将所有注释去掉,保留默认部分,如下

  1. <?xml version="1.0" encoding="UTF-8"?>
  2.  
  3. <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  4. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  5. xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  6.  
  7. <localRepository>${user.home}/.m2/repository</localRepository>
  8.  
  9. <interactiveMode>true</interactiveMode>
  10.  
  11. <offline>false</offline>
  12.  
  13. <pluginGroups></pluginGroups>
  14.  
  15. <proxies></proxies>
  16.  
  17. <servers></servers>
  18.  
  19. <mirrors></mirrors>
  20.  
  21. <profiles></profiles>
  22.  
  23. <activeProfiles></activeProfiles>
  24.  
  25. </settings>

localRepository

本地仓库路径,默认路径为${user.home}/.m2/repository。为了避免重装系统而被删除,可在maven文件夹下创建个repository文件夹,将该节点改为该repository文件夹的路径即可

interactiveMode

互动模式,默认值为true。该值使用默认值即可,无需更改

offline

离线模式,默认值为false。当因为各种原因无法与远程仓库连接时,可将该值修改为true

pluginGroups

  1. <pluginGroups>
  2. <pluginGroup>com.your.plugins</pluginGroup>
  3. </pluginGroups>

插件组,内部由n个pluginGroup节点组成,默认自带了org.apache.maven.plugins和org.codehaus.mojo。若有特殊的需求是可进行扩展

proxies

  1. <proxies>
  2. <proxy>
  3. <id>optional</id>
  4. <active>true</active>
  5. <protocol>http</protocol>
  6. <username>proxyuser</username>
  7. <password>proxypass</password>
  8. <host>proxy.host.net</host>
  9. <port>80</port>
  10. <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
  11. </proxy>
  12. </proxies>

代理设置,内部由n个proxy节点组成。部分公司出于安全考虑会需要员工通过代理才可上网,这时,就需配置该节点的参数了。

参数说明:

id:唯一标识符

active:是否被激活使用,默认为true。当有多个proxy节点存在时,用于选择使用哪个代理,但同一时间仅有一个代理会被被激活

protocol:协议类型

username:用户名,没有可不填

password:密码,没有可不填

host:IP地址

port:端口号

nonProxyHosts:不使用代理的地址

以上参数在通常配置代理的情况都会使用到,一样填上即可,最终的代理地址为protocol://host:port

servers

  1. <servers>
  2. <server>
  3. <id>deploymentRepo</id>
  4. <username>repouser</username>
  5. <password>repopwd</password>
  6. </server>
  7. <server>
  8. <id>siteServer</id>
  9. <privateKey>/path/to/private/key</privateKey>
  10. <passphrase>optional; leave empty if not used</passphrase>
  11. </server>
  12. </servers>

服务器,内部由n个server节点组成。有2种配置方式:一种是通过id匹配,username和password进行认证登录;另一种是通过id匹配指向一个privateKey(私钥)和一个passphrase

mirrors

  1. <mirrors>
  2. <mirror>
  3. <id>mirrorId</id>
  4. <mirrorOf>repositoryId</mirrorOf>
  5. <name>Human Readable Name for this Mirror.</name>
  6. <url>http://my.repository.com/repo/path</url>
  7. </mirror>
  8. </mirrors>

镜像仓库,内部由n个mirror节点组成。用来代替中央仓库(Maven默认的远程仓库),用于提升传输速度。因此此处可以添加一个镜像,以提升我们下载的速度

  1. <mirrors>
  2. <mirror>
  3. <id>alimaven</id>
  4. <name>aliyun maven</name>
  5. <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
  6. <mirrorOf>central</mirrorOf>
  7. </mirror>
  8. </mirrors>

profiles

  1. <profiles>
  2. <profile>
  3. <id>jdk-1.4</id>
  4. <activation>
  5. <jdk>1.4</jdk>
  6. </activation>
  7. <repositories>
  8. <repository>
  9. <id>jdk14</id>
  10. <name>Repository for JDK 1.4 builds</name>
  11. <url>http://www.myhost.com/maven/jdk14</url>
  12. <layout>default</layout>
  13. <snapshotPolicy>always</snapshotPolicy>
  14. </repository>
  15. </repositories>
  16. </profile>
  17. <profile>
  18. <id>env-dev</id>
  19. <activation>
  20. <property>
  21. <name>target-env</name>
  22. <value>dev</value>
  23. </property>
  24. </activation>
  25. <properties>
  26. <tomcatPath>/path/to/tomcat/instance</tomcatPath>
  27. </properties>
  28. </profile>
  29. </profiles>

用于覆盖在一个POM或者profiles.xml文件中的任何相同id的profiles节点

activeProfiles

  1. <activeProfiles>
  2. <activeProfile>alwaysActiveProfile</activeProfile>
  3. <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  4. </activeProfiles>

activeProfile值为profile中所定义的id,在这里定义的activeProfile总是被激活

总结

一般情况而言,settings.xml无需配置太多的东西,作为优化,可配置localRepository和mirrors

  1. <?xml version="1.0" encoding="UTF-8"?>
  2.  
  3. <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  4. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  5. xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  6.  
  7. <localRepository>
  8. D:/apache-maven-3.5.2/repository
  9. </localRepository>
  10.  
  11. <pluginGroups></pluginGroups>
  12.  
  13. <proxies></proxies>
  14.  
  15. <servers></servers>
  16.  
  17. <mirrors>
  18. <mirror>
  19. <id>alimaven</id>
  20. <name>aliyun maven</name>
  21. <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
  22. <mirrorOf>central</mirrorOf>
  23. </mirror>
  24. </mirrors>
  25.  
  26. <profiles></profiles>
  27.  
  28. </settings>

转载至:https://www.cnblogs.com/s1165482267/p/7928275.html

Maven——settings.xml配置的更多相关文章

  1. Maven settings.xml配置(指定本地仓库、阿里云镜像设置)

    转: 详解Maven settings.xml配置(指定本地仓库.阿里云镜像设置) 更新时间:2018年12月18日 11:14:45   作者:AmaniZ   我要评论   一.settings. ...

  2. Maven settings.xml配置解读

    本文对${maven.home}\conf\settings.xml的官方文档作个简单的解读,请确保自己的maven环境安装成功,具体安装流程详见Maven安装 第一步:看settings.xml的内 ...

  3. 学习笔记——Maven settings.xml 配置详解

    文件存放位置 全局配置: ${M2_HOME}/conf/settings.xml 用户配置: ${user.home}/.m2/settings.xml note:用户配置优先于全局配置.${use ...

  4. Maven settings.xml配置详解

    首先:Maven中央仓库的搜索全部公共jar包的地址是,http://search.maven.org/ ===Maven基础-默认中央仓库============================== ...

  5. maven settings.xml配置优化

    <?xml version="1.0" encoding="UTF-8"?> <settings> <localRepositor ...

  6. Maven项目使用Nexus作为远程仓库的settings.xml配置

    Maven项目使用Nexus作为远程仓库的settings.xml配置(转) 在自己电脑C:\Users\hanmm\.m2\下的setting.xml. 1.服务器配置 <server> ...

  7. [java][JEECG] Maven settings.xml JEECG项目初始化 RouYi settings.xml配置

    好吧一下是经验之谈,原本这些坑不应该躺的,从头看手册完全可以避免这些. 懒得整理了,看懂了就看,看不懂自己琢磨JEECG的帮助文档去,不过嘛我喜欢用Intelij IDEA,他里面都是别的IDE,不喜 ...

  8. Maven学习存档(2)——settings.xml配置

    二.settings.xml配置 2.1 原文 <?xml version="1.0" encoding="UTF-8"?> <!-- Lic ...

  9. Maven的settings.xml配置详解

    子节点详细介绍转载:http://www.cnblogs.com/jingmoxukong/p/6050172.html?utm_source=gold_browser_extension 全局配置 ...

随机推荐

  1. zepto 事件分析3(add函数)

    在上一篇的分析中,最后$.on方法返回了一个add方法函数的执行,在这里先看一下其代码: function add(element, events, fn, data, selector, deleg ...

  2. NET(C#)接入Dubbo服务,Zookeeper作为Dubbo服务的注册中心,实现thrift协议访问接口(3)

    如何引用Zookeeper.dll 下载最新版本的Zookeeper 地址:http://mirrors.cnnic.cn/apache/zookeeper/ 没有.NET代码 dotnet代码下载 ...

  3. [转]centos6.5修改yum安装的mysql默认目录

    本文转自:https://www.cnblogs.com/fefjay/p/6044444.html 0.说明 Linux下更改yum默认安装的mysql路径datadir.linux下,MySQL默 ...

  4. .net敏捷开发框架 力软敏捷开发(learun) 让开发变的更简单

    版本:6.1.6.2 体验地址:www.fishcmonkey.com 联系QQ:6539471

  5. SQL Server导入导出不丢主键和视图的方法

    SQL Server导入导出 SQL Server 导入导出 工具/原料 使用Microsoft SQL Server Management Studio 导入导出数据. 直接使用Microsoft  ...

  6. 在SQL中查询某列具有相同值的数据

    SELECT * FROM dbo.SBD_WAYBILL_GOODS WHERE WG_SW_ID ) ORDER BY WG_ID SELECT * FROM dbo.SBD_WAYBILL WH ...

  7. [javaEE] Tomcat的安装与配置

    下载压缩包,解压缩,好,安装完成 进入解压目录/bin/下面,找到startup.bat,双击,此时如果报错,那么就是没有设置环境变量JAVA_HOME,进入环境变量去设置,JAVA_HOME指向jd ...

  8. [android] 采用layoutInflater打气筒创建一个view对象

    上一节知道了ListView的工作原理,数据也展示出来了,但是TextView显示的非常难看,如果想美化一下,就先创建好一个布局出来,这个布局采用了两层LinearLayout嵌套,外层的水平方向,内 ...

  9. intellij error updating changes svn解决办法

    乌龟检出的svn版本为1.8,而1.8在IntelliJ 上跑起来貌似有问题, 经过多次尝试,当Format改为1.7后,问题被解决.

  10. jQuery中页面返回顶部的方法总结

    当页面过长时,通常会在页面下方有一个返回顶部的button,总结一下,大概三种实现方法,下面说下各方法及优缺点. 方法一 锚点定位 ? 1 <a href="#" class ...