maven私服配置国内aliyun中央仓库
Posted №.1飛翔
tags:
篇首语：本文由小常识网(cha138.com)小编为大家整理，主要介绍了maven私服配置国内aliyun中央仓库相关的知识，希望对你有一定的参考价值。
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.home}/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:\Repositories\Maven</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 <pluginGroup>org.mortbay.jetty</pluginGroup> 85 </pluginGroups> 86 87 <!-- proxies 88 | This is a list of proxies which can be used on this machine to connect to the network. 89 | Unless otherwise specified (by system property or command-line switch), the first proxy 90 | specification in this list marked as active will be used. 91 |--> 92 <proxies> 93 <!-- proxy 94 | Specification for one proxy, to be used in connecting to the network. 95 | 96 <proxy> 97 <id>optional</id> 98 <active>true</active> 99 <protocol>http</protocol> 100 <username>proxyuser</username> 101 <password>proxypass</password> 102 <host>proxy.host.net</host> 103 <port>80</port> 104 <nonProxyHosts>local.net|some.host.com</nonProxyHosts> 105 </proxy> 106 --> 107 </proxies> 108 109 <!-- servers 110 | This is a list of authentication profiles, keyed by the server-id used within the system. 111 | Authentication profiles can be used whenever maven must make a connection to a remote server. 112 |--> 113 <servers> 114 <!-- server 115 | Specifies the authentication information to use when connecting to a particular server, identified by 116 | a unique name within the system (referred to by the ‘id‘ attribute below). 117 | 118 | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are 119 | used together. 120 | 121 <server> 122 <id>deploymentRepo</id> 123 <username>repouser</username> 124 <password>repopwd</password> 125 </server> 126 --> 127 128 <!-- Another sample, using keys to authenticate. 129 <server> 130 <id>siteServer</id> 131 <privateKey>/path/to/private/key</privateKey> 132 <passphrase>optional; leave empty if not used.</passphrase> 133 </server> 134 --> 135 <server> 136 <id>releases</id> 137 <username>ali</username> 138 <password>ali</password> 139 </server> 140 <server> 141 <id>Snapshots</id> 142 <username>ali</username> 143 <password>ali</password> 144 </server> 145 </servers> 146 147 <!-- mirrors 148 | This is a list of mirrors to be used in downloading artifacts from remote repositories. 149 | 150 | It works like this: a POM may declare a repository to use in resolving certain artifacts. 151 | However, this repository may have problems with heavy traffic at times, so people have mirrored 152 | it to several places. 153 | 154 | That repository definition will have a unique id, so we can create a mirror reference for that 155 | repository, to be used as an alternate download site. The mirror site will be the preferred 156 | server for that repository. 157 |--> 158 <mirrors> 159 <!-- mirror 160 | Specifies a repository mirror site to use instead of a given repository. The repository that 161 | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used 162 | for inheritance and direct lookup purposes, and must be unique across the set of mirrors. 163 | 164 <mirror> 165 <id>mirrorId</id> 166 <mirrorOf>repositoryId</mirrorOf> 167 <name>Human Readable Name for this Mirror.</name> 168 <url>http://my.repository.com/repo/path</url> 169 </mirror> 170 --> 171 <mirror> 172 <!--This sends everything else to /public --> 173 <id>nexus</id> 174 <mirrorOf>*</mirrorOf> 175 <url>http://maven.aliyun.com/nexus/content/groups/public/</url> 176 </mirror> 177 <mirror> 178 <!--This is used to direct the public snapshots repo in the 179 profile below over to a different nexus group --> 180 <id>nexus-public-snapshots</id> 181 <mirrorOf>public-snapshots</mirrorOf> 182 <url>http://maven.aliyun.com/nexus/content/repositories/snapshots/</url> 183 </mirror> 184 </mirrors> 185 186 <!-- profiles 187 | This is a list of profiles which can be activated in a variety of ways, and which can modify 188 | the build process. Profiles provided in the settings.xml are intended to provide local machine- 189 | specific paths and repository locations which allow the build to work in the local environment. 190 | 191 | For example, if you have an integration testing plugin - like cactus - that needs to know where 192 | your Tomcat instance is installed, you can provide a variable here such that the variable is 193 | dereferenced during the build process to configure the cactus plugin. 194 | 195 | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles 196 | section of this document (settings.xml) - will be discussed later. Another way essentially 197 | relies on the detection of a system property, either matching a particular value for the property, 198 | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a 199 | value of ‘1.4‘ might activate a profile when the build is executed on a JDK version of ‘1.4.2_07‘. 200 | Finally, the list of active profiles can be specified directly from the command line. 201 | 202 | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact 203 | repositories, plugin repositories, and free-form properties to be used as configuration 204 | variables for plugins in the POM. 205 | 206 |--> 207 <profiles> 208 <profile> 209 <id>development</id> 210 <repositories> 211 <repository> 212 <id>central</id> 213 <url>http://central</url> 214 <releases><enabled>true</enabled><updatePolicy>always</updatePolicy></releases> 215 <snapshots><enabled>true</enabled><updatePolicy>always</updatePolicy></snapshots> 216 </repository> 217 </repositories> 218 <pluginRepositories> 219 <pluginRepository> 220 <id>central</id> 221 <url>http://central</url> 222 <releases><enabled>true</enabled><updatePolicy>always</updatePolicy></releases> 223 <snapshots><enabled>true</enabled><updatePolicy>always</updatePolicy></snapshots> 224 </pluginRepository> 225 </pluginRepositories> 226 </profile> 227 <profile> 228 <!--this profile will allow snapshots to be searched when activated--> 229 <id>public-snapshots</id> 230 <repositories> 231 <repository> 232 <id>public-snapshots</id> 233 <url>http://public-snapshots</url> 234 <releases><enabled>false</enabled></releases> 235 <snapshots><enabled>true</enabled><updatePolicy>always</updatePolicy></snapshots> 236 </repository> 237 </repositories> 238 <pluginRepositories> 239 <pluginRepository> 240 <id>public-snapshots</id> 241 <url>http://public-snapshots</url> 242 <releases><enabled>false</enabled></releases> 243 <snapshots><enabled>true</enabled><updatePolicy>always</updatePolicy></snapshots> 244 </pluginRepository> 245 </pluginRepositories> 246 </profile> 247 </profiles> 248 249 <activeProfiles> 250 <activeProfile>development</activeProfile> 251 <activeProfile>public-snapshots</activeProfile> 252 </activeProfiles> 253 </settings>
以上是关于maven私服配置国内aliyun中央仓库的主要内容，如果未能解决你的问题，请参考以下文章