你的位置:首页 > ASP.net教程

[ASP.net教程]解决maven下载jar慢的问题


 

修改 配置文件

maven 安装 路径

F:\apache-maven-3.3.9\conf

修改 settings.


<mirrors>
<!-- mirror
| Specifies a repository mirror site to use instead of a given repository. The repository that
| this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
| for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
|
<mirror>
<id>mirrorId</id>
<mirrorOf>repositoryId</mirrorOf>
<name>Human Readable Name for this Mirror.</name>
<url>http://my.repository.com/repo/path</url>
</mirror>
-->
</mirrors>

添加 如下 内容 访问 开源中国的jar 下载源

 


<mirror>
<id>CN</id>
<name>OSChina Central</name>
<url>http://maven.oschina.net/content/groups/public/</url>
<mirrorOf>central</mirrorOf>
</mirror>

 ---------------------------------------------------------------------------------------------------------------------------

以下是完整的:settings.

 1 <??> 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. 26  |         and is normally provided in ${user.home}/.m2/settings. 27  | 28  |         NOTE: This location can be overridden with the CLI option: 29  | 30  |         -s /path/to/user/settings. 31  | 32  | 2. Global Level. This settings. 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. 36  | 37  |         NOTE: This location can be overridden with the CLI option: 38  | 39  |         -gs /path/to/global/settings. 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 ="http://maven.apache.org/SETTINGS/1.0.0" 47      ="http://www.w3.org/2001/ 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  56  <!-- interactiveMode 57   | This will determine whether maven prompts you when it needs input. If set to false, 58   | maven will use a sensible default value, perhaps based on some other setting, for 59   | the parameter in question. 60   | 61   | Default: true 62  <interactiveMode>true</interactiveMode> 63  --> 64  65  <!-- offline 66   | Determines whether maven should attempt to connect to the network when executing a build. 67   | This will have an effect on artifact downloads, artifact deployment, and others. 68   | 69   | Default: false 70  <offline>false</offline> 71  --> 72  73  <!-- pluginGroups 74   | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e. 75   | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers 76   | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list. 77   |--> 78  <pluginGroups> 79   <!-- pluginGroup 80    | Specifies a further group identifier to use for plugin lookup. 81   <pluginGroup>com.your.plugins</pluginGroup> 82   --> 83  </pluginGroups> 84  85  <!-- proxies 86   | This is a list of proxies which can be used on this machine to connect to the network. 87   | Unless otherwise specified (by system property or command-line switch), the first proxy 88   | specification in this list marked as active will be used. 89   |--> 90  <proxies> 91   <!-- proxy 92    | Specification for one proxy, to be used in connecting to the network. 93    | 94   <proxy> 95    <id>optional</id> 96    <active>true</active> 97    <protocol>http</protocol> 98    <username>proxyuser</username> 99    <password>proxypass</password>100    <host>proxy.host.net</host>101    <port>80</port>102    <nonProxyHosts>local.net|some.host.com</nonProxyHosts>103   </proxy>104   -->105  </proxies>106 107  <!-- servers108   | This is a list of authentication profiles, keyed by the server-id used within the system.109   | Authentication profiles can be used whenever maven must make a connection to a remote server.110   |-->111  <servers>112   <!-- server113    | Specifies the authentication information to use when connecting to a particular server, identified by114    | a unique name within the system (referred to by the 'id' attribute below).115    |116    | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are117    |    used together.118    |119   <server>120    <id>deploymentRepo</id>121    <username>repouser</username>122    <password>repopwd</password>123   </server>124   -->125 126   <!-- Another sample, using keys to authenticate.127   <server>128    <id>siteServer</id>129    <privateKey>/path/to/private/key</privateKey>130    <passphrase>optional; leave empty if not used.</passphrase>131   </server>132   -->133  </servers>134 135  <!-- mirrors136   | This is a list of mirrors to be used in downloading artifacts from remote repositories.137   |138   | It works like this: a POM may declare a repository to use in resolving certain artifacts.139   | However, this repository may have problems with heavy traffic at times, so people have mirrored140   | it to several places.141   |142   | That repository definition will have a unique id, so we can create a mirror reference for that143   | repository, to be used as an alternate download site. The mirror site will be the preferred144   | server for that repository.145   |-->146  <mirrors>147   <mirror>148      <id>repo2</id>149      <mirrorOf>central</mirrorOf>150      <name>Human Readable Name for this Mirror.</name>151      <url>http://repo2.maven.org/maven2/</url>152   </mirror>153   <mirror>154      <id>net-cn</id>155      <mirrorOf>central</mirrorOf>156      <name>Human Readable Name for this Mirror.</name>157      <url>http://maven.net.cn/content/groups/public/</url>158   </mirror>159   <mirror>160      <id>ui</id>161      <mirrorOf>central</mirrorOf>162      <name>Human Readable Name for this Mirror.</name>163     <url>http://uk.maven.org/maven2/</url>164   </mirror>165   <mirror>166      <id>ibiblio</id>167      <mirrorOf>central</mirrorOf>168      <name>Human Readable Name for this Mirror.</name>169     <url>http://mirrors.ibiblio.org/pub/mirrors/maven2/</url>170   </mirror>171   <mirror>172      <id>jboss-public-repository-group</id>173      <mirrorOf>central</mirrorOf>174      <name>JBoss Public Repository Group</name>175     <url>http://repository.jboss.org/nexus/content/groups/public</url>176   </mirror>177   <mirror>178    <id>CN</id>179    <name>OSChina Central</name>180    <url>http://maven.oschina.net/content/groups/public/</url>181    <mirrorOf>central</mirrorOf>182   </mirror>183 184  </mirrors>185 186  <!-- profiles187   | This is a list of profiles which can be activated in a variety of ways, and which can modify188   | the build process. Profiles provided in the settings.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 where192   | your Tomcat instance is installed, you can provide a variable here such that the variable is193   | 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 activeProfiles196   | section of this document (settings.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 a199   | 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.203   |    repositories, plugin repositories, and free-form properties to be used as configuration204   |    variables for plugins in the POM.205   |206   |-->207  <profiles>208   <!-- profile209    | Specifies a set of introductions to the build process, to be activated using one or more of the210    | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>211    | or the command line, profiles have to have an ID that is unique.212    |213    | An encouraged best practice for profile identification is to use a consistent naming convention214    | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.215    | This will make it more intuitive to understand what the set of introduced profiles is attempting216    | to accomplish, particularly when you only have a list of profile id's for debug.217    |218    | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.219   <profile>220    <id>jdk-1.4</id>221 222    <activation>223     <jdk>1.4</jdk>224    </activation>225 226    <repositories>227     <repository>228      <id>jdk14</id>229      <name>Repository for JDK 1.4 builds</name>230      <url>http://www.myhost.com/maven/jdk14</url>231      <layout>default</layout>232      <snapshotPolicy>always</snapshotPolicy>233     </repository>234    </repositories>235   </profile>236   -->237 238   <!--239    | Here is another profile, activated by the system property 'target-env' with a value of 'dev',240    | which provides a specific path to the Tomcat instance. To use this, your plugin configuration241    | might hypothetically look like:242    |243    | ...244    | <plugin>245    |  <groupId>org.myco.myplugins</groupId>246    |  <artifactId>myplugin</artifactId>247    |248    |  <configuration>249    |   <tomcatLocation>${tomcatPath}</tomcatLocation>250    |  </configuration>251    | </plugin>252    | ...253    |254    | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to255    |    anything, you could just leave off the <value/> inside the activation-property.256    |257   <profile>258    <id>env-dev</id>259 260    <activation>261     <property>262      <name>target-env</name>263      <value>dev</value>264     </property>265    </activation>266 267    <properties>268     <tomcatPath>/path/to/tomcat/instance</tomcatPath>269    </properties>270   </profile>271   -->272  </profiles>273 274  <!-- activeProfiles275   | List of profiles that are active for all builds.276   |277  <activeProfiles>278   <activeProfile>alwaysActiveProfile</activeProfile>279   <activeProfile>anotherAlwaysActiveProfile</activeProfile>280  </activeProfiles>281  -->282 </settings>

 

转载请注明出处!

感谢您的阅读。如果文章对您有用,那么请轻轻点个赞,以资鼓励。