Maven setting.xml 配置详解

摘要

maven settings.xml详解





Maven setting.xml 配置详解


Maven setting.xml 配置详解

Maven


settings.xml详解

声明规范

  1. <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  2. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  3. xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">

localRepository

  1. <!-- 本地仓库的路径。默认值为 -->
  2. <localRepository>/opt/repository</localRepository>

interactiveMode

  1. <!--Maven是否需要和用户交互以获得输入。如果Maven需要和用户交互以获得输入,则设置成true,反之则应为false。默认为true。-->
  2. <interactiveMode>true</interactiveMode>

usePluginRegistry

  1. <!--Maven是否需要使用plugin-registry.xml文件来管理插件版本。如果需要让Maven使用文件来管理插件版本,则设为true。默认为false。-->
  2. <usePluginRegistry>false</usePluginRegistry>

offline

  1. <!--表示Maven是否需要在离线模式下运行。如果构建系统需要在离线模式下运行,则为true,默认为false。当由于网络设置原因或者安全因素,构建服务器不能连接远程仓库的时候,该配置就十分有用。 -->
  2. <offline>false</offline>

pluginGroups

  1. <!--当插件的组织Id(groupId)没有显式提供时,供搜寻插件组织Id(groupId)的列表。该元素包含一个pluginGroup元素列表,每个子元素包含了一个组织Id(groupId)。当我们使用某个插件,并且没有在命令行为其提供组织Id(groupId)的时候,Maven就会使用该列表。默认情况下该列表包含了org.apache.maven.plugins和org.codehaus.mojo -->
  2. <pluginGroups>
  3. <!--plugin的组织Id(groupId) -->
  4. <pluginGroup>org.codehaus.mojo</pluginGroup>
  5. </pluginGroups>

proxies

  1. <!--用来配置不同的代理,多代理profiles 可以应对笔记本或移动设备的工作环境:通过简单的设置profile id就可以很容易的更换整个代理配置。 -->
  2. <proxies>
  3. <!--代理元素包含配置代理时需要的信息-->
  4. <proxy>
  5. <!--代理的唯一定义符,用来区分不同的代理元素。-->
  6. <id>myproxy</id>
  7. <!--该代理是否是激活的那个。true则激活代理。当我们声明了一组代理,而某个时候只需要激活一个代理的时候,该元素就可以派上用处。 -->
  8. <active>true</active>
  9. <!--代理的协议。 协议://主机名:端口,分隔成离散的元素以方便配置。-->
  10. <protocol>http</protocol>
  11. <!--代理的主机名。协议://主机名:端口,分隔成离散的元素以方便配置。 -->
  12. <host>proxy.somewhere.com</host>
  13. <!--代理的端口。协议://主机名:端口,分隔成离散的元素以方便配置。 -->
  14. <port>8080</port>
  15. <!--代理的用户名,用户名和密码表示代理服务器认证的登录名和密码。 -->
  16. <username>proxyuser</username>
  17. <!--代理的密码,用户名和密码表示代理服务器认证的登录名和密码。 -->
  18. <password>somepassword</password>
  19. <!--不该被代理的主机名列表。该列表的分隔符由代理服务器指定;例子中使用了竖线分隔符,使用逗号分隔也很常见。-->
  20. <nonProxyHosts>*.google.com|ibiblio.org</nonProxyHosts>
  21. </proxy>
  22. </proxies>

servers

  1. <!--配置服务端的一些设置。一些设置如安全证书不应该和pom.xml一起分发。这种类型的信息应该存在于构建服务器上的settings.xml文件中。-->
  2. <servers>
  3. <!--服务器元素包含配置服务器时需要的信息 -->
  4. <server>
  5. <!--这是server的id(注意不是用户登陆的id),该id与distributionManagement中repository元素的id相匹配。-->
  6. <id>server001</id>
  7. <!--鉴权用户名。鉴权用户名和鉴权密码表示服务器认证所需要的登录名和密码。 -->
  8. <username>my_login</username>
  9. <!--鉴权密码 。鉴权用户名和鉴权密码表示服务器认证所需要的登录名和密码。密码加密功能已被添加到2.1.0 +。详情请访问密码加密页面-->
  10. <password>my_password</password>
  11. <!--鉴权时使用的私钥位置。和前两个元素类似,私钥位置和私钥密码指定了一个私钥的路径(默认是${user.home}/.ssh/id_dsa)以及如果需要的话,一个密语。将来passphrase和password元素可能会被提取到外部,但目前它们必须在settings.xml文件以纯文本的形式声明。 -->
  12. <privateKey>${usr.home}/.ssh/id_dsa</privateKey>
  13. <!--鉴权时使用的私钥密码。-->
  14. <passphrase>some_passphrase</passphrase>
  15. <!--文件被创建时的权限。如果在部署的时候会创建一个仓库文件或者目录,这时候就可以使用权限(permission)。这两个元素合法的值是一个三位数字,其对应了unix文件系统的权限,如664,或者775。 -->
  16. <filePermissions>664</filePermissions>
  17. <!--目录被创建时的权限。 -->
  18. <directoryPermissions>775</directoryPermissions>
  19. </server>
  20. </servers>

mirrors

  1. <!--为仓库列表配置的下载镜像列表。高级设置请参阅镜像设置页面 -->
  2. <mirrors>
  3. <!--给定仓库的下载镜像。 -->
  4. <mirror>
  5. <!--该镜像的唯一标识符。id用来区分不同的mirror元素。 -->
  6. <id>planetmirror.com</id>
  7. <!--镜像名称 -->
  8. <name>PlanetMirror Australia</name>
  9. <!--该镜像的URL。构建系统会优先考虑使用该URL,而非使用默认的服务器URL。 -->
  10. <url>http://downloads.planetmirror.com/pub/maven2</url>
  11. <!--被镜像的服务器的id。例如,如果我们要设置了一个Maven中央仓库(http://repo.maven.apache.org/maven2/)的镜像,就需要将该元素设置成central。这必须和中央仓库的id central完全一致。-->
  12. <mirrorOf>central</mirrorOf>
  13. </mirror>
  14. </mirrors>

profiles

  1. <!--根据环境参数来调整构建配置的列表。settings.xml中的profile元素是pom.xml中profile元素的裁剪版本。它包含了id,activation, repositories, pluginRepositories和 properties元素。这里的profile元素只包含这五个子元素是因为这里只关心构建系统这个整体(这正是settings.xml文件的角色定位),而非单独的项目对象模型设置。如果一个settings中的profile被激活,它的值会覆盖任何其它定义在POM中或者profile.xml中的带有相同id的profile。 -->
  2. <profiles>
  3. <!--根据环境参数来调整的构件的配置-->
  4. <profile>
  5. <!--该配置的唯一标识符。 -->
  6. <id>test</id>

Activation

  1. <!--自动触发profile的条件逻辑。Activation是profile的开启钥匙。如POM中的profile一样,profile的力量来自于它能够在某些特定的环境中自动使用某些特定的值;这些环境通过activation元素指定。activation元素并不是激活profile的唯一方式。settings.xml文件中的activeProfile元素可以包含profile的id。profile也可以通过在命令行,使用-P标记和逗号分隔的列表来显式的激活(如,-P test)。-->
  2. <activation>
  3. <!--profile默认是否激活的标识-->
  4. <activeByDefault>false</activeByDefault>
  5. <!--当匹配的jdk被检测到,profile被激活。例如,1.4激活JDK1.4,1.4.0_2,而!1.4激活所有版本不是以1.4开头的JDK。-->
  6. <jdk>1.5</jdk>
  7. <!--当匹配的操作系统属性被检测到,profile被激活。os元素可以定义一些操作系统相关的属性。-->
  8. <os>
  9. <!--激活profile的操作系统的名字 -->
  10. <name>Windows XP</name>
  11. <!--激活profile的操作系统所属家族(如 'windows') -->
  12. <family>Windows</family>
  13. <!--激活profile的操作系统体系结构 -->
  14. <arch>x86</arch>
  15. <!--激活profile的操作系统版本-->
  16. <version>5.1.2600</version>
  17. </os>
  18. <!--如果Maven检测到某一个属性(其值可以在POM中通过${name}引用),其拥有对应的name = 值,Profile就会被激活。如果值字段是空的,那么存在属性名称字段就会激活profile,否则按区分大小写方式匹配属性值字段-->
  19. <property>
  20. <!--激活profile的属性的名称-->
  21. <name>mavenVersion</name>
  22. <!--激活profile的属性的值 -->
  23. <value>2.0.3</value>
  24. </property>
  25. <!--提供一个文件名,通过检测该文件的存在或不存在来激活profile。missing检查文件是否存在,如果不存在则激活profile。另一方面,exists则会检查文件是否存在,如果存在则激活profile。-->
  26. <file>
  27. <!--如果指定的文件存在,则激活profile。 -->
  28. <exists>${basedir}/file2.properties</exists>
  29. <!--如果指定的文件不存在,则激活profile。-->
  30. <missing>${basedir}/file1.properties</missing>
  31. </file>
  32. </activation>

Properties

  1. <!--对应profile的扩展属性列表。Maven属性和Ant中的属性一样,可以用来存放一些值。这些值可以在POM中的任何地方使用标记${X}来使用,这里X是指属性的名称。属性有五种不同的形式,并且都能在settings.xml文件中访问。
  2. 1. env.X: 在一个变量前加上"env."的前缀,会返回一个shell环境变量。例如,"env.PATH"指代了$path环境变量(在Windows上是%PATH%)。
  3. 2. project.x:指代了POM中对应的元素值。例如: <project><version>1.0</version></project>通过${project.version}获得version的值。
  4. 3. settings.x: 指代了settings.xml中对应元素的值。例如:<settings><offline>false</offline></settings>通过 ${settings.offline}获得offline的值。
  5. 4. Java System Properties: 所有可通过java.lang.System.getProperties()访问的属性都能在POM中使用该形式访问,例如 ${java.home}。
  6. 5. x: 在<properties/>元素中,或者外部文件中设置,以${someVar}的形式使用。 -->
  7. <properties>
  8. <tomcatPath>/path/to/tomcat/instance</tomcatPath>
  9. </properties>

Repositories

  1. <repository>
  2. <id>nexus</id>
  3. <name>local private nexus</name>
  4. <url>http://localhost:8081/nexus/content/groups/public</url>
  5. <releases><enabled>true</enabled></releases>
  6. <snapshots><enabled>true</enabled></snapshots>
  7. </repository>
  8. </repositories>
  9. <!--远程仓库列表,它是Maven用来填充构建系统本地仓库所使用的一组远程项目。 -->
  10. <repositories>
  11. <!--包含需要连接到远程仓库的信息 -->
  12. <repository>
  13. <!--远程仓库唯一标识-->
  14. <id>codehausSnapshots</id>
  15. <!--远程仓库名称 -->
  16. <name>Codehaus Snapshots</name>
  17. <!--如何处理远程仓库里发布版本的下载-->
  18. <releases>
  19. <!--true或者false表示该仓库是否为下载某种类型构件(发布版,快照版)开启。 -->
  20. <enabled>false</enabled>
  21. <!--该元素指定更新发生的频率。Maven会比较本地POM和远程POM的时间戳。这里的选项是:always(一直),daily(默认,每日),interval:X(这里X是以分钟为单位的时间间隔),或者never(从不)。 -->
  22. <updatePolicy>always</updatePolicy>
  23. <!--当Maven验证构件校验文件失败时该怎么做-ignore(忽略),fail(失败),或者warn(警告)。-->
  24. <checksumPolicy>warn</checksumPolicy>
  25. </releases>
  26. <!--如何处理远程仓库里快照版本的下载。有了releases和snapshots这两组配置,POM就可以在每个单独的仓库中,为每种类型的构件采取不同的策略。例如,可能有人会决定只为开发目的开启对快照版本下载的支持。参见repositories/repository/releases元素-->
  27. <snapshots>
  28. <enabled/><updatePolicy/><checksumPolicy/>
  29. </snapshots>
  30. <!--远程仓库URL,按protocol://hostname/path形式 -->
  31. <url>http://snapshots.maven.codehaus.org/maven2</url>
  32. <!--用于定位和排序构件的仓库布局类型-可以是default(默认)或者legacy(遗留)。Maven 2为其仓库提供了一个默认的布局;然而,Maven 1.x有一种不同的布局。我们可以使用该元素指定布局是default(默认)还是legacy(遗留)。 -->
  33. <layout>default</layout>
  34. </repository>
  35. </repositories>
  36. <!--发现插件的远程仓库列表。仓库是两种主要构件的家。第一种构件被用作其它构件的依赖。这是中央仓库中存储的大部分构件类型。另外一种构件类型是插件。Maven插件是一种特殊类型的构件。由于这个原因,插件仓库独立于其它仓库。pluginRepositories元素的结构和repositories元素的结构类似。每个pluginRepository元素指定一个Maven可以用来寻找新插件的远程地址。-->
  37. <pluginRepositories>
  38. <!--包含需要连接到远程插件仓库的信息.参见profiles/profile/repositories/repository元素的说明-->
  39. <pluginRepository>
  40. <releases>
  41. <enabled/><updatePolicy/><checksumPolicy/>
  42. </releases>
  43. <snapshots>
  44. <enabled/><updatePolicy/><checksumPolicy/>
  45. </snapshots>
  46. <id/><name/><url/><layout/>
  47. </pluginRepository>
  48. </pluginRepositories>
  49. </profile>
  50. </profiles>

activeProfiles

  1. 默认配置:
  2. <activeProfiles>
  3. <activeProfile>dev</activeProfile>
  4. <!-- <activeProfile>devitcast</activeProfile>-->
  5. </activeProfiles>
  6. 配置解释:
  7. <!--手动激活profiles的列表,按照profile被应用的顺序定义activeProfile 该元素包含了一组activeProfile元素,每个activeProfile都含有一个profile id。任何在activeProfile中定义的profile id,不论环境设置如何,其对应的profile都会被激活。如果没有匹配的profile,则什么都不会发生。例如,env-test是一个activeProfile,则在pom.xml(或者profile.xml)中对应idprofile会被激活。如果运行过程中找不到这样一个profileMaven则会像往常一样运行 -->
  8. <activeProfiles>
  9. <!-- -->
  10. <activeProfile>env-test</activeProfile>
  11. </activeProfiles>
  12. </settings>

例子:
我们公司nexus地址:172.16.1.40
Maven settings.xml 如下:

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <!--
  3. Licensed to the Apache Software Foundation (ASF) under one
  4. or more contributor license agreements. See the NOTICE file
  5. distributed with this work for additional information
  6. regarding copyright ownership. The ASF licenses this file
  7. to you under the Apache License, Version 2.0 (the
  8. "License"); you may not use this file except in compliance
  9. with the License. You may obtain a copy of the License at
  10. http://www.apache.org/licenses/LICENSE-2.0
  11. Unless required by applicable law or agreed to in writing,
  12. software distributed under the License is distributed on an
  13. "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  14. KIND, either express or implied. See the License for the
  15. specific language governing permissions and limitations
  16. under the License.
  17. -->
  18. <!--
  19. | This is the configuration file for Maven. It can be specified at two levels:
  20. |
  21. | 1. User Level. This settings.xml file provides configuration for a single user,
  22. | and is normally provided in ${user.home}/.m2/settings.xml.
  23. |
  24. | NOTE: This location can be overridden with the CLI option:
  25. |
  26. | -s /path/to/user/settings.xml
  27. |
  28. | 2. Global Level. This settings.xml file provides configuration for all Maven
  29. | users on a machine (assuming they're all using the same Maven
  30. | installation). It's normally provided in
  31. | ${maven.home}/conf/settings.xml.
  32. |
  33. | NOTE: This location can be overridden with the CLI option:
  34. |
  35. | -gs /path/to/global/settings.xml
  36. |
  37. | The sections in this sample file are intended to give you a running start at
  38. | getting the most out of your Maven installation. Where appropriate, the default
  39. | values (values used when the setting is not specified) are provided.
  40. |
  41. |-->
  42. <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  43. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  44. xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  45. <!-- localRepository
  46. | The path to the local repository maven will use to store artifacts.
  47. |
  48. | Default: ${user.home}/.m2/repository
  49. <localRepository>/path/to/local/repo</localRepository>
  50. -->
  51. <localRepository>/opt/repository</localRepository>
  52. <!-- interactiveMode
  53. | This will determine whether maven prompts you when it needs input. If set to false,
  54. | maven will use a sensible default value, perhaps based on some other setting, for
  55. | the parameter in question.
  56. |
  57. | Default: true
  58. <interactiveMode>true</interactiveMode>
  59. -->
  60. <!-- offline
  61. | Determines whether maven should attempt to connect to the network when executing a build.
  62. | This will have an effect on artifact downloads, artifact deployment, and others.
  63. |
  64. | Default: false
  65. <offline>false</offline>
  66. -->
  67. <!-- pluginGroups
  68. | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
  69. | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
  70. | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
  71. |-->
  72. <pluginGroups>
  73. <!-- pluginGroup
  74. | Specifies a further group identifier to use for plugin lookup.
  75. <pluginGroup>com.your.plugins</pluginGroup>
  76. -->
  77. <pluginGroup>org.apache.maven.plugins</pluginGroup>
  78. <pluginGroup>org.mortbay.jetty</pluginGroup>
  79. <pluginGroup>com.oracle.weblogic</pluginGroup>
  80. </pluginGroups>
  81. <!-- proxies
  82. | This is a list of proxies which can be used on this machine to connect to the network.
  83. | Unless otherwise specified (by system property or command-line switch), the first proxy
  84. | specification in this list marked as active will be used.
  85. |-->
  86. <proxies>
  87. <!-- proxy
  88. | Specification for one proxy, to be used in connecting to the network.
  89. |
  90. <proxy>
  91. <id>optional</id>
  92. <active>true</active>
  93. <protocol>http</protocol>
  94. <username>proxyuser</username>
  95. <password>proxypass</password>
  96. <host>proxy.host.net</host>
  97. <port>80</port>
  98. <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
  99. </proxy>
  100. -->
  101. </proxies>
  102. <!-- servers
  103. | This is a list of authentication profiles, keyed by the server-id used within the system.
  104. | Authentication profiles can be used whenever maven must make a connection to a remote server.
  105. |-->
  106. <servers>
  107. <!-- server
  108. | Specifies the authentication information to use when connecting to a particular server, identified by
  109. | a unique name within the system (referred to by the 'id' attribute below).
  110. |
  111. | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
  112. | used together.
  113. |
  114. <server>
  115. <id>deploymentRepo</id>
  116. <username>repouser</username>
  117. <password>repopwd</password>
  118. </server>
  119. -->
  120. <!-- Another sample, using keys to authenticate.
  121. <server>
  122. <id>siteServer</id>
  123. <privateKey>/path/to/private/key</privateKey>
  124. <passphrase>optional; leave empty if not used.</passphrase>
  125. </server>
  126. -->
  127. <!-- <server>
  128. <id>nexus</id>
  129. <username>admin</username>
  130. <password>20041108</password>
  131. </server>
  132. <server>
  133. <id>nexus-central</id>
  134. <username>admin</username>
  135. <password>20041108</password>
  136. </server>
  137. <server>
  138. <id>nexus-releases</id>
  139. <username>admin</username>
  140. <password>20041108</password>
  141. </server>
  142. <server>
  143. <id>nexus-snapshots</id>
  144. <username>admin</username>
  145. <password>20041108</password>
  146. </server>
  147. <server>
  148. <id>local-nexus</id>
  149. <username>admin</username>
  150. <password>20041108</password>
  151. </server>
  152. -->
  153. <server>
  154. <id>nexus</id>
  155. <username>admin</username>
  156. <password>anonymous123</password>
  157. </server>
  158. <server>
  159. <id>releases</id>
  160. <username>admin</username>
  161. <password>anonymous123</password>
  162. </server>
  163. <server>
  164. <id>snapshots</id>
  165. <username>admin</username>
  166. <password>anonymous123</password>
  167. </server>
  168. <server>
  169. <id>thirdparty</id>
  170. <username>admin</username>
  171. <password>anonymous123</password>
  172. </server>
  173. </servers>
  174. <!-- mirrors
  175. | This is a list of mirrors to be used in downloading artifacts from remote repositories.
  176. |
  177. | It works like this: a POM may declare a repository to use in resolving certain artifacts.
  178. | However, this repository may have problems with heavy traffic at times, so people have mirrored
  179. | it to several places.
  180. |
  181. | That repository definition will have a unique id, so we can create a mirror reference for that
  182. | repository, to be used as an alternate download site. The mirror site will be the preferred
  183. | server for that repository.
  184. |-->
  185. <mirrors>
  186. <!-- mirror
  187. | Specifies a repository mirror site to use instead of a given repository. The repository that
  188. | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
  189. | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
  190. | -->
  191. <!-- <mirror>
  192. <id>nexus</id>
  193. <mirrorOf>*</mirrorOf>
  194. <name>internal nexus repository</name>
  195. <url>http://wufeluli:8081/nexus/content/groups/public/</url>
  196. </mirror>
  197. -->
  198. <mirror>
  199. <id>nexus</id>
  200. <name>internal nexus repository</name>
  201. <url>http://172.16.1.40:8080/nexus/content/groups/public</url>
  202. <mirrorOf>*</mirrorOf>
  203. </mirror>
  204. </mirrors>
  205. <!-- profiles
  206. | This is a list of profiles which can be activated in a variety of ways, and which can modify
  207. | the build process. Profiles provided in the settings.xml are intended to provide local machine-
  208. | specific paths and repository locations which allow the build to work in the local environment.
  209. |
  210. | For example, if you have an integration testing plugin - like cactus - that needs to know where
  211. | your Tomcat instance is installed, you can provide a variable here such that the variable is
  212. | dereferenced during the build process to configure the cactus plugin.
  213. |
  214. | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
  215. | section of this document (settings.xml) - will be discussed later. Another way essentially
  216. | relies on the detection of a system property, either matching a particular value for the property,
  217. | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
  218. | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
  219. | Finally, the list of active profiles can be specified directly from the command line.
  220. |
  221. | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
  222. | repositories, plugin repositories, and free-form properties to be used as configuration
  223. | variables for plugins in the POM.
  224. |
  225. |-->
  226. <profiles>
  227. <!-- profile
  228. | Specifies a set of introductions to the build process, to be activated using one or more of the
  229. | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
  230. | or the command line, profiles have to have an ID that is unique.
  231. |
  232. | An encouraged best practice for profile identification is to use a consistent naming convention
  233. | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
  234. | This will make it more intuitive to understand what the set of introduced profiles is attempting
  235. | to accomplish, particularly when you only have a list of profile id's for debug.
  236. |
  237. | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
  238. <profile>
  239. <id>jdk-1.4</id>
  240. <activation>
  241. <jdk>1.4</jdk>
  242. </activation>
  243. <repositories>
  244. <repository>
  245. <id>jdk14</id>
  246. <name>Repository for JDK 1.4 builds</name>
  247. <url>http://www.myhost.com/maven/jdk14</url>
  248. <layout>default</layout>
  249. <snapshotPolicy>always</snapshotPolicy>
  250. </repository>
  251. </repositories>
  252. </profile>
  253. -->
  254. <!--
  255. | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
  256. | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
  257. | might hypothetically look like:
  258. |
  259. | ...
  260. | <plugin>
  261. | <groupId>org.myco.myplugins</groupId>
  262. | <artifactId>myplugin</artifactId>
  263. |
  264. | <configuration>
  265. | <tomcatLocation>${tomcatPath}</tomcatLocation>
  266. | </configuration>
  267. | </plugin>
  268. | ...
  269. |
  270. | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
  271. | anything, you could just leave off the <value/> inside the activation-property.
  272. |
  273. <profile>
  274. <id>env-dev</id>
  275. <activation>
  276. <property>
  277. <name>target-env</name>
  278. <value>dev</value>
  279. </property>
  280. </activation>
  281. <properties>
  282. <tomcatPath>/path/to/tomcat/instance</tomcatPath>
  283. </properties>
  284. </profile>
  285. -->
  286. <!--
  287. <profile>
  288. <id>dev</id>
  289. <repositories>
  290. <repository>
  291. <id>nexus</id>
  292. <name>local private nexus</name>
  293. <url>http://localhost:8081/nexus/content/groups/public</url>
  294. <releases><enabled>true</enabled></releases>
  295. <snapshots><enabled>true</enabled></snapshots>
  296. </repository>
  297. </repositories>
  298. <pluginRepositories>
  299. <pluginRepository>
  300. <id>nexus</id>
  301. <url>http://localhost:8081/nexus/content/groups/public</url>
  302. <releases><enabled>true</enabled></releases>
  303. <snapshots><enabled>true</enabled></snapshots>
  304. </pluginRepository>
  305. </pluginRepositories>
  306. </profile>
  307. -->
  308. <!-- 自定义开始 -->
  309. <profile>
  310. <id>apatch</id>
  311. <repositories>
  312. <repository>
  313. <id>re-apatch</id>
  314. <name>remote apatch</name>
  315. <url>http://inno.starhubdev.com/nexus/content/groups/public/</url>
  316. <releases>
  317. <enabled>true</enabled>
  318. </releases>
  319. <snapshots>
  320. <enabled>true</enabled>
  321. </snapshots>
  322. </repository>
  323. </repositories>
  324. </profile>
  325. <profile>
  326. <id>ibiblio</id>
  327. <repositories>
  328. <repository>
  329. <id>re-ibiblio</id>
  330. <name>remote ibiblio</name>
  331. <url>https://nexus.sourcesense.com/nexus/content/repositories/public/</url>
  332. <releases>
  333. <enabled>true</enabled>
  334. </releases>
  335. <snapshots>
  336. <enabled>true</enabled>
  337. </snapshots>
  338. </repository>
  339. </repositories>
  340. </profile>
  341. <profile>
  342. <id>redev</id>
  343. <repositories>
  344. <repository>
  345. <id>re-nexus</id>
  346. <name>remote nexus</name>
  347. <url>http://repository.sonatype.org/content/groups/public/</url>
  348. <releases>
  349. <enabled>true</enabled>
  350. </releases>
  351. <snapshots>
  352. <enabled>true</enabled>
  353. </snapshots>
  354. </repository>
  355. </repositories>
  356. </profile>
  357. <!-- 自定义结束 -->
  358. <profile>
  359. <id>dev</id>
  360. <repositories>
  361. <repository>
  362. <id>nexus</id>
  363. <url>http://172.16.1.40:8080/nexus/content/groups/public</url>
  364. <releases><enabled>true</enabled></releases>
  365. <snapshots><enabled>true</enabled></snapshots>
  366. </repository>
  367. </repositories>
  368. <pluginRepositories>
  369. <pluginRepository>
  370. <id>nexus</id>
  371. <url>http://172.16.1.40:8080/nexus/content/groups/public</url>
  372. <releases><enabled>true</enabled></releases>
  373. <snapshots><enabled>true</enabled></snapshots>
  374. </pluginRepository>
  375. </pluginRepositories>
  376. </profile>
  377. </profiles>
  378. <!-- activeProfiles
  379. | List of profiles that are active for all builds.
  380. |
  381. <activeProfiles>
  382. <activeProfile>alwaysActiveProfile</activeProfile>
  383. <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  384. </activeProfiles>
  385. -->
  386. <activeProfiles>
  387. <activeProfile>dev</activeProfile>
  388. <!-- <activeProfile>devitcast</activeProfile>-->
  389. </activeProfiles>
  390. </settings>


发表评论

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen: