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

原文地址:https://www.cnblogs.com/arthurLance/p/10541112.html

时间: 2024-10-28 23:40:31

maven settings.xml 配置 --阿里源的相关文章

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

文件存放位置 全局配置: ${M2_HOME}/conf/settings.xml 用户配置: ${user.home}/.m2/settings.xml note:用户配置优先于全局配置.${user.home} 和和所有其他系统属性只能在3.0+版本上使用.请注意windows和Linux使用变量的区别. settings.xml详解 声明规范 <?xml version="1.0" encoding="UTF-8"?> <settings x

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

POM的全称是“ProjectObjectModel(项目对象模型)”. pom.xml详解 声明规范 <projectxmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0http://maven.apach

centos8 配置阿里源

CentOS 8更改了安装程序,改而使用了dnf 作为安装程序.虽然新增了软件包的安装方式,但是 yum命令还是可以正常使用.centos8 配置阿里源 1.备份CentOS-Base.repo文件 cd /etc/yum.repos.d cp CentOS-Base.repo CentOS-Base.repo.bak 2.配置文件vim tOS- CentOS-Base.repo # CentOS-Base.repo The mirror system uses the connecting

Maven - settings.xml简易配置Demo

前言 这里贴一下settings.xml的一个简易配置demo,就是简单配置了:本地的仓库地址.阿里云镜像.指定使用jdk1.8进行编译. 这里使用的Maven是3.5.0版本的. 配置文件demo <?xml version="1.0" encoding="UTF-8"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor lic

Maven的相关问题(一)——settings.xml配置详解

工作中第一次正式接触maven,虽然之前在学习时有遇到过,但是对于maven的认识和理解确实太浅薄,仅仅局限于机械式的操,纸上得来终觉浅,绝知此事要躬行···古人诚不欺我也~ 下面先贴一个找到的一个非常详细的注解,链接:http://blog.csdn.net/mypop/article/details/6146686 1 <?xml version="1.0" encoding="UTF-8"?> 2 <settings xmlns="

idea下修改maven的setting.xml配置阿里云镜像

1.打开idea中自带的maven插件或者自己安装的maven,将存放配置参数的conf文件夹找到,并编辑settings.xml 配置文件. 2.找到 mirror 标签,修改为以下信息: <mirror> <id>alimaven</id> <name>aliyun maven</name> <url>http://maven.aliyun.com/nexus/content/groups/public/</url>

Maven pom.xml 配置详解

什么是pom?    pom作为项目对象模型.通过xml表示maven项目,使用pom.xml来实现.主要描述了项目:包括配置文件:开发者需要遵循的规则,缺陷管理系统,组织和licenses,项目的url,项目的依赖性,以及其他所有的项目相关因素. pom.xml 配置文件 <project> <parent> ... </parent> <modelVersion>4.0.0</modelVersion> <!-- The Basics

【转】Maven pom.xml 配置详解

原文链接:https://yq.aliyun.com/articles/38271 pom.xml文件配置详解 --声明规范 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http:/

[Maven]Settings.xml文件详解

概要 settings.xml有什么用? 如果在Eclipse中使用过Maven插件,想必会有这个经验:配置settings.xml文件的路径. l  settings.xml文件是干什么的,为什么要配置它呢? 从settings.xml的文件名就可以看出,它是用来设置Maven参数的配置文件.并且,settings.xml是Maven的全局配置文件.而pom.xml文件是所在项目的局部配置. Settings.xml中包含类似本地仓储位置.修改远程仓储服务器.认证信息等配置. settings