Maven setting配置镜像仓库

原创 2018年04月15日 19:51:46

国内Maven镜像仓库值得收藏

1.配置IDE构建的Maven存放目录(解压目录)

2.配置IDE的User setting file路径,修改setting配置文件

  配置本地仓库

   1 <!--自定义本地仓库路径-->

  2 <localRepository>E:\JAVA\Maven</localRepository> 

  配置mirrors远程镜像(一般配置一到两个镜像) 

复制代码
 1 <mirrors>
 2     <!-- mirror
 3      | Specifies a repository mirror site to use instead of a given repository. The repository that
 4      | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
 5      | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
 6      |
 7     <mirror>
 8       <id>mirrorId</id>
 9       <mirrorOf>repositoryId</mirrorOf>
10       <name>Human Readable Name for this Mirror.</name>
11       <url>http://my.repository.com/repo/path</url>
12     </mirror>
13      -->
14     <mirror>
15         <id>alimaven</id>
16         <mirrorOf>central</mirrorOf>
17         <name>aliyun maven</name>
18         <url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
19     </mirror>
20     <mirror>
21         <id>jboss-public-repository-group</id>
22         <mirrorOf>central</mirrorOf>
23         <name>JBoss Public Repository Group</name>
24         <url>http://repository.jboss.org/nexus/content/groups/public</url>
25     </mirror>
26 </mirrors>
复制代码

  配置profiles构建  

复制代码
 1 <profile>
 2     <id>jdk18</id>
 3     <activation>
 4         <jdk>1.8</jdk>
 5         <activeByDefault>true</activeByDefault>
 6     </activation>
 7     <properties>
 8         <maven.compiler.source>1.8</maven.compiler.source>
 9         <maven.compiler.target>1.8</maven.compiler.target>
10         <maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
11     </properties>
12 </profile>
复制代码

  国内Maven镜像仓库值得收藏 

复制代码
 1 <mirror>
 2     <id>alimaven</id>
 3     <name>aliyun maven</name>
 4     <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
 5     <mirrorOf>central</mirrorOf>
 6 </mirror>
 7 <mirror>
 8     <id>alimaven</id>
 9     <mirrorOf>central</mirrorOf>
10     <name>aliyun maven</name>
11     <url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
12 </mirror>
13 
14 <mirror>
15     <id>ibiblio</id>
16     <mirrorOf>central</mirrorOf>
17     <name>Human Readable Name for this Mirror.</name>
18     <url>http://mirrors.ibiblio.org/pub/mirrors/maven2/</url>
19 </mirror>
20 <mirror>
21     <id>jboss-public-repository-group</id>
22     <mirrorOf>central</mirrorOf>
23     <name>JBoss Public Repository Group</name>
24     <url>http://repository.jboss.org/nexus/content/groups/public</url>
25 </mirror>
26 
27 <mirror>
28     <id>central</id>
29     <name>Maven Repository Switchboard</name>
30     <url>http://repo1.maven.org/maven2/</url>
31     <mirrorOf>central</mirrorOf>
32 </mirror>
33 <mirror>
34     <id>repo2</id>
35     <mirrorOf>central</mirrorOf>
36     <name>Human Readable Name for this Mirror.</name>
37     <url>http://repo2.maven.org/maven2/</url>
38 </mirror>
复制代码

完整的settings.xml内容

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

<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<!--
 | This is the configuration file for Maven. It can be specified at two levels:
 |
 |  1. User Level. This settings.xml file provides configuration for a single user,
 |                 and is normally provided in ${user.home}/.m2/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -s /path/to/user/settings.xml
 |
 |  2. Global Level. This settings.xml file provides configuration for all Maven
 |                 users on a machine (assuming they're all using the same Maven
 |                 installation). It's normally provided in
 |                 ${maven.home}/conf/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -gs /path/to/global/settings.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation. Where appropriate, the default
 | values (values used when the setting is not specified) are provided.
 |
 |-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
    <!-- localRepository
     | The path to the local repository maven will use to store artifacts.
     |
     | Default: ${user.home}/.m2/repository
    <localRepository>/path/to/local/repo</localRepository>
    -->
    <!--自定义本地仓库路径-->
    <localRepository>E:\JAVA\Maven</localRepository>
    <!-- interactiveMode
     | This will determine whether maven prompts you when it needs input. If set to false,
     | maven will use a sensible default value, perhaps based on some other setting, for
     | the parameter in question.
     |
     | Default: true
    <interactiveMode>true</interactiveMode>
    -->

    <!-- offline
     | Determines whether maven should attempt to connect to the network when executing a build.
     | This will have an effect on artifact downloads, artifact deployment, and others.
     |
     | Default: false
    <offline>false</offline>
    -->

    <!-- pluginGroups
     | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
     | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
     | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
     |-->
    <pluginGroups>
        <!-- pluginGroup
         | Specifies a further group identifier to use for plugin lookup.
        <pluginGroup>com.your.plugins</pluginGroup>
        -->
    </pluginGroups>

    <!-- proxies
     | This is a list of proxies which can be used on this machine to connect to the network.
     | Unless otherwise specified (by system property or command-line switch), the first proxy
     | specification in this list marked as active will be used.
     |-->
    <proxies>
        <!-- proxy
         | Specification for one proxy, to be used in connecting to the network.
         |
        <proxy>
          <id>optional</id>
          <active>true</active>
          <protocol>http</protocol>
          <username>proxyuser</username>
          <password>proxypass</password>
          <host>proxy.host.net</host>
          <port>80</port>
          <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
        </proxy>
        -->
    </proxies>

    <!-- servers
     | This is a list of authentication profiles, keyed by the server-id used within the system.
     | Authentication profiles can be used whenever maven must make a connection to a remote server.
     |-->
    <servers>
        <!-- server
         | Specifies the authentication information to use when connecting to a particular server, identified by
         | a unique name within the system (referred to by the 'id' attribute below).
         |
         | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
         |       used together.
         |
        <server>
          <id>deploymentRepo</id>
          <username>repouser</username>
          <password>repopwd</password>
        </server>
        -->

        <!-- Another sample, using keys to authenticate.
        <server>
          <id>siteServer</id>
          <privateKey>/path/to/private/key</privateKey>
          <passphrase>optional; leave empty if not used.</passphrase>
        </server>
        -->
    </servers>

    <!-- mirrors
     | This is a list of mirrors to be used in downloading artifacts from remote repositories.
     |
     | It works like this: a POM may declare a repository to use in resolving certain artifacts.
     | However, this repository may have problems with heavy traffic at times, so people have mirrored
     | it to several places.
     |
     | That repository definition will have a unique id, so we can create a mirror reference for that
     | repository, to be used as an alternate download site. The mirror site will be the preferred
     | server for that repository.
     |-->
    <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>
         -->

        <mirror>
            <id>alimaven-central</id>
            <mirrorOf>central</mirrorOf>
            <name>aliyun maven</name>
            <url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
        </mirror>
        <mirror>
            <id>jboss-public-repository-group</id>
            <mirrorOf>central</mirrorOf>
            <name>JBoss Public Repository Group</name>
            <url>http://repository.jboss.org/nexus/content/groups/public</url>
        </mirror>

        <!--<mirror>
            <id>alimaven</id>
            <name>aliyun maven</name>
            <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
            <mirrorOf>central</mirrorOf>
        </mirror>

        <mirror>
            <id>ibiblio</id>
            <mirrorOf>central</mirrorOf>
            <name>Human Readable Name for this Mirror.</name>
            <url>http://mirrors.ibiblio.org/pub/mirrors/maven2/</url>
        </mirror>

        <mirror>
            <id>central</id>
            <name>Maven Repository Switchboard</name>
            <url>http://repo1.maven.org/maven2/</url>
            <mirrorOf>central</mirrorOf>
        </mirror>
        <mirror>
            <id>repo2</id>
            <mirrorOf>central</mirrorOf>
            <name>Human Readable Name for this Mirror.</name>
            <url>http://repo2.maven.org/maven2/</url>
        </mirror>-->

    </mirrors>

    <!-- profiles
     | This is a list of profiles which can be activated in a variety of ways, and which can modify
     | the build process. Profiles provided in the settings.xml are intended to provide local machine-
     | specific paths and repository locations which allow the build to work in the local environment.
     |
     | For example, if you have an integration testing plugin - like cactus - that needs to know where
     | your Tomcat instance is installed, you can provide a variable here such that the variable is
     | dereferenced during the build process to configure the cactus plugin.
     |
     | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
     | section of this document (settings.xml) - will be discussed later. Another way essentially
     | relies on the detection of a system property, either matching a particular value for the property,
     | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
     | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
     | Finally, the list of active profiles can be specified directly from the command line.
     |
     | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
     |       repositories, plugin repositories, and free-form properties to be used as configuration
     |       variables for plugins in the POM.
     |
     |-->
    <profiles>
        <!-- profile
         | Specifies a set of introductions to the build process, to be activated using one or more of the
         | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
         | or the command line, profiles have to have an ID that is unique.
         |
         | An encouraged best practice for profile identification is to use a consistent naming convention
         | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
         | This will make it more intuitive to understand what the set of introduced profiles is attempting
         | to accomplish, particularly when you only have a list of profile id's for debug.
         |
         | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
        <profile>
          <id>jdk-1.4</id>

          <activation>
            <jdk>1.4</jdk>
          </activation>

          <repositories>
            <repository>
              <id>jdk14</id>
              <name>Repository for JDK 1.4 builds</name>
              <url>http://www.myhost.com/maven/jdk14</url>
              <layout>default</layout>
              <snapshotPolicy>always</snapshotPolicy>
            </repository>
          </repositories>
        </profile>
        -->
        <profile>
            <id>jdk18</id>
            <activation>
                <jdk>1.8</jdk>
                <activeByDefault>true</activeByDefault>
            </activation>
            <properties>
                <maven.compiler.source>1.8</maven.compiler.source>
                <maven.compiler.target>1.8</maven.compiler.target>
                <maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
            </properties>
        </profile>

        <!--
         | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
         | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
         | might hypothetically look like:
         |
         | ...
         | <plugin>
         |   <groupId>org.myco.myplugins</groupId>
         |   <artifactId>myplugin</artifactId>
         |
         |   <configuration>
         |     <tomcatLocation>${tomcatPath}</tomcatLocation>
         |   </configuration>
         | </plugin>
         | ...
         |
         | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
         |       anything, you could just leave off the <value/> inside the activation-property.
         |
        <profile>
          <id>env-dev</id>

          <activation>
            <property>
              <name>target-env</name>
              <value>dev</value>
            </property>
          </activation>

          <properties>
            <tomcatPath>/path/to/tomcat/instance</tomcatPath>
          </properties>
        </profile>
        -->
    </profiles>

    <!-- activeProfiles
     | List of profiles that are active for all builds.
     |
    <activeProfiles>
      <activeProfile>alwaysActiveProfile</activeProfile>
      <activeProfile>anotherAlwaysActiveProfile</activeProfile>
    </activeProfiles>
    -->
</settings>

版权声明:本文为博主原创文章,未经博主允许不得转载。 https://blog.csdn.net/GavinLi2588/article/details/79952344

【maven】在setting文件配置中央仓库的镜像

原文链接
  • crazylzxlzx
  • crazylzxlzx
  • 2016-12-22 10:44:15
  • 1030

maven配置多仓库镜像

maven配置多个仓库 maven配置多个镜像 maven如何同时使用多个远程仓库镜像
  • haohaizijhz
  • haohaizijhz
  • 2017-06-02 11:12:58
  • 15283

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

一、settings.xml文件会在两个目录下存在:1、Maven安装目录(全局):%MAVEN_HOME%\conf\settings.xml2、用户安装目录(用户):${user.home}\.m...
  • AmaniZ
  • AmaniZ
  • 2018-02-08 00:42:06
  • 1618

Maven 仓库阿里云镜像配置

阿里云Maven国内仓库镜像 http://maven.aliyun.com/,简单粗暴,造福广大maven爱好者。...
  • Cwenyifan
  • Cwenyifan
  • 2017-02-04 17:22:25
  • 25092

Maven settings 开源中国 镜像并下载本地仓库

如果还没配置好Maven的朋友请先配置好Maven,配置Maven点击:http://blog.csdn.net/icoudsoft_saas/article/details/50390873 Mav...
  • icoudsoft_saas
  • icoudsoft_saas
  • 2015-12-24 01:07:28
  • 1182

maven settings.xml 包含多个镜像库

settings.xml配置文件
  • fu0110
  • fu0110
  • 2016-07-28 17:36:19
  • 5714

Maven 设置镜像库--阿里云

修改maven根目录下的conf文件夹中的setting.xml文件 mirrors> mirror> id>alimavenid> name>aliyun mav...
  • zx1323
  • zx1323
  • 2017-02-23 23:04:53
  • 408

maven本地仓库和国内镜像的配置

在maven的setting文件中设置 maven本地仓库配置 国内镜像的配置 下载的速度比较快 ...
  • XUEER88888888888888
  • XUEER88888888888888
  • 2018-02-19 18:23:34
  • 48

配置maven里settings.xml以及阿里云镜像服务器的方法

配置阿里云镜像服务器-----下面有apache-maven-3.5.2下载地址 -----其主要修改settings.xml配置文件 (其中主要修改三个地方)1.在settings标签下,加入这一段...
  • qq_37832927
  • qq_37832927
  • 2018-02-27 14:28:45
  • 529

maven setting为什么需要配置镜像

为什么需要配置maven国内镜像? 1、在不配置镜像的情况下,maven默认会使用中央库. 2、maven中央库在国外,有时候访问会很慢,尤其是下载较大的依赖的时候,有时候速度会很慢,甚至会出现无...
  • zhouzhiwengang
  • zhouzhiwengang
  • 2017-02-27 02:20:23
  • 1692
收藏助手
不良信息举报
您举报文章:Maven setting配置镜像仓库
举报原因:
原因补充:

(最多只允许输入30个字)