收集的国内Maven镜像地址和使用

虽然 Maven 提供了一个免费中央仓,让开发者可以方便地找到全球大部分需要的第三方库。但是国内开发者由于网络原因,直接从中央仓下载第三包速度较慢或不稳定,科学上网或使用国内镜像站可以很好解决该问题。下面就介绍下如何将开源镜像站配置为maven的默认第三方库下载源。

什么是maven

Maven是一个项目管理工具,它包含了一个项目对象模型 (Project Object Model),一组标准集合,一个项目生命周期(Project Lifecycle),一个依赖管理系统(Dependency Management System),和用来运行定义在生命周期阶段(phase)中插件(plugin)目标(goal)的逻辑。当你使用Maven的时候,你用一个明确定义的项目对象模型来描述你的项目,然后Maven可以应用横切的逻辑,这些逻辑来自一组共享的(或者自定义的)插件。

Maven 有一个生命周期,当你运行 mvn install 的时候被调用。这条命令告诉 Maven 执行一系列的有序的步骤,直到到达你指定的生命周期。遍历生命周期旅途中的一个影响就是,Maven 运行了许多默认的插件目标,这些目标完成了像编译和创建一个 JAR 文件这样的工作。此外,Maven能够很方便的帮你管理项目报告,生成站点,管理JAR文件,等等。

maven常用命令

  • mvn archetype:create 创建Maven项目
  • mvn compile 编译源代码
  • mvn deploy 发布项目
  • mvn test-compile 编译测试源代码
  • mvn test 运行应用程序中的单元测试
  • mvn site 生成项目相关信息的网站
  • mvn clean 清除项目目录中的生成结果
  • mvn package 根据项目生成的jar
  • mvn install 在本地Repository中安装jar
  • mvn eclipse:eclipse 生成eclipse项目文件
  • mvnjetty:run 启动jetty服务
  • mvntomcat:run 启动tomcat服务
  • mvn clean package -Dmaven.test.skip=true:清除以前的包后重新打包,跳过测试类

maven可用仓库URL

配置maven仓库

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
<!-- 配置maven仓库地址 -->
<repositories>
<repository>
<id>oschina Releases</id>
<name>oschina Releases</name>
<url>http://maven.oschina.net/content/groups/public</url>
</repository>
<repository>
<id>mvnrepository</id>
<name>mvnrepository</name>
<url>http://mvnrepository.com/</url>
</repository>
<repository>
<id>apache-repo</id>
<name>apache Repository</name>
<url>https://repository.apache.org/content/groups/public/</url>
</repository>
<repository>
<id>java-repo</id>
<name>java Repository</name>
<url>http://download.java.net/maven/2/</url>
</repository>
<repository>
<id>springsource-repo</id>
<name>SpringSource Repository</name>
<url>http://repo.spring.io/release/</url>
</repository>
<repository>
<id>springsource-repo-snapshot</id>
<name>SpringSource Repository</name>
<url>http://repo.spring.io/snapshot/</url>
</repository>
<repository>
<id>jboss-repo-releases</id>
<name>Jboss Repository</name>
<url>https://repository.jboss.org/nexus/content/repositories/releases/</url>
</repository>
<repository>
<id>central</id>
<name>Maven Repository Switchboard</name>
<layout>default</layout>
<url>http://repo.maven.apache.org/maven2</url>
</repository>
<repository>
<id>maven-repo1</id>
<name>maven-repo1</name>
<layout>default</layout>
<url>http://repo1.maven.org/maven2/</url>
</repository>
<repository>
<id>sourceforge-releases</id>
<name>Sourceforge Releases</name>
<url>https://oss.sonatype.org/content/repositories/sourceforge-releases</url>
</repository>
</repositories>

使用方法:

  • 下面的代码,修改里面的仓库地址,保存为settings.xml,放到用户目录的.m2目录中(C:\Users\用户名.m2)
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    68
    69
    70
    71
    72
    73
    74
    75
    76
    77
    78
    79
    80
    81
    82
    83
    84
    85
    86
    87
    88
    89
    90
    91
    92
    93
    94
    95
    96
    97
    98
    99
    100
    101
    102
    103
    104
    105
    106
    107
    108
    109
    110
    111
    112
    113
    114
    115
    116
    117
    118
    119
    120
    121
    122
    123
    124
    125
    126
    127
    128
    129
    130
    131
    132
    133
    134
    135
    136
    137
    138
    139
    140
    141
    142
    143
    144
    145
    146
    147
    148
    149
    150
    151
    152
    153
    154
    155
    156
    157
    158
    159
    160
    161
    162
    163
    164
    165
    166
    167
    168
    169
    170
    171
    172
    173
    174
    175
    176
    177
    178
    179
    180
    181
    182
    <?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>D:/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>
    <id>optional</id>
    <active>true</active>
    <protocol>http</protocol>
    <host>127.0.0.1</host>
    <port>8087</port>
    </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>nexus-osc</id>
    <mirrorOf>*</mirrorOf>
    <name>Nexus osc</name>
    <url>http://mvnrepo.tae.taobao.com/content/groups/public/</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>
    <repositories>
    <repository>
    <id>nexus</id>
    <name>local private nexus</name>
    <url>http://mvnrepo.tae.taobao.com/content/groups/public/</url>
    <releases>
    <enabled>true</enabled>
    </releases>
    <snapshots>
    <enabled>false</enabled>
    </snapshots>
    </repository>
    </repositories>
    <pluginRepositories>
    <pluginRepository>
    <id>nexus</id>
    <name>local private nexus</name>
    <url>http://mvnrepo.tae.taobao.com/content/groups/public/</url>
    <releases>
    <enabled>true</enabled>
    </releases>
    <snapshots>
    <enabled>false</enabled>
    </snapshots>
    </pluginRepository>
    </pluginRepositories>
    </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://mirrors.huaweicloud.com/

  • 设置方法,打开maven的设置文件settings.xml,在servers节点中添加如下用户信息:
1
2
3
4
5
<server>
<id>huaweicloud</id>
<username>anonymous</username>
<password>devcloud</password>
</server>
  • 在mirrors节点中添加如下镜像仓地址:
1
2
3
4
5
<mirror>
<id>huaweicloud</id>
<mirrorOf>*</mirrorOf>
<url>https://mirrors.huaweicloud.com/repository/maven/</url>
</mirror>
个人微信公众号技术交流QQ群
文章目录
  1. 1. 什么是maven
  2. 2. maven常用命令
  3. 3. maven可用仓库URL
    1. 3.1. 地址二:
  4. 4. 配置maven仓库
  5. 5. 使用方法:
  6. 6. 华为镜像