1.私有maven仓库的搭建

下载安装包

  1. wget http://download.sonatype.com/nexus/3/nexus-3.7.1-02-unix.tar.gz

解压软件

  1. #解压软件
  2. mkdir -p /opt/nexus && tar xf nexus-3.7.1-02-unix.tar.gz -C /opt/nexus
  3. #添加系统配置文件
  4. vim /etc/profile
  5. export MAVEN_HOME=/opt/nexus/nexus-3.7.1-02
  6. export PATH=$PATH:$MAVEN_HOME/bin
  8. #刷新配置文件
  9. source /etc/profile

启动nexus

  1. nexus run
  2. #然后访问ip:port 默认的端口是8081，阿里云服务器记得要开启这个端口的访问。看到这个页面就表示，你的私有maven仓库搭建成功了。
  3. #登录进去（默认账号:admin,默认密码:admin123）可以查看repositories，配置用户啥的。

搭建Maven私有仓库 - 图1

  • 默认仓库说明

    maven-central：maven中央库，默认从https://repo1.maven.org/maven2/拉取jar
    maven-releases：私库发行版jar，初次安装请将Deployment policy设置为Allow redeploy
    maven-snapshots：私库快照（调试版本）jar
    maven-public：仓库分组，把上面三个仓库组合在一起对外提供服务，在本地maven基础配置settings.xml或项目pom.xml中使用

  • 仓库类型

    Group：这是一个仓库聚合的概念，用户仓库地址选择Group的地址，即可访问Group中配置的，用于方便开发人员自己设定的仓库。maven-public就是一个Group类型的仓库，内部设置了多个仓库，访问顺序取决于配置顺序，3.x默认Releases，Snapshots， Central，当然你也可以自己设置。
    Hosted：私有仓库，内部项目的发布仓库，专门用来存储我们自己生成的jar文件
    3rd party：未发布到公网的第三方jar (3.x去除了)
    Snapshots：本地项目的快照仓库
    Releases： 本地项目发布的正式版本
    Proxy：代理类型，从远程中央仓库中寻找数据的仓库（可以点击对应的仓库的Configuration页签下Remote Storage属性的值即被代理的远程仓库的路径），如可配置阿里云maven仓库
    Central：中央仓库
    Apache Snapshots：Apache专用快照仓库(3.x去除了)

增加新的代理源

第一步 按照步骤添加新的代理源

搭建Maven私有仓库 - 图2

第二步选择添加maven2的代理

搭建Maven私有仓库 - 图3

第三步添加代理（Cache统一设置为200天 288000）

搭建Maven私有仓库 - 图4搭建Maven私有仓库 - 图5

第四步逐个增加常用代理
  1. 1. aliyun
  2. http://maven.aliyun.com/nexus/content/groups/public
  3. 2. apache_snapshot
  4. https://repository.apache.org/content/repositories/snapshots/
  5. 3. apache_release
  6. https://repository.apache.org/content/repositories/releases/
  7. 4. atlassian
  8. https://maven.atlassian.com/content/repositories/atlassian-public/
  9. 5. central.maven.org
  10. http://central.maven.org/maven2/
  11. 6. datanucleus
  12. http://www.datanucleus.org/downloads/maven2
  13. 7. maven-central （安装后自带，仅需设置Cache有效期即可）
  14. https://repo1.maven.org/maven2/
  15. 8. nexus.axiomalaska.com
  16. http://nexus.axiomalaska.com/nexus/content/repositories/public
  17. 9. oss.sonatype.org
  18. https://oss.sonatype.org/content/repositories/snapshots
  19. 10.pentaho
  20. https://public.nexus.pentaho.org/content/groups/omni/

第五步 设置maven-public 将这些代理加入Group，最好将默认的maven库放到最底下

搭建Maven私有仓库 - 图6

搭建Maven私有仓库 - 图7

选择Configuration > Repository, 双击 maven-public, 在Group区域将aliyun移到右侧Members, 上移到maven-central的上面, 点击 Save。

第六步 设置私用仓库可重复发布

Nexus安装后自带maven-releases，maven-snapshots两个仓库，用于将生成的jar包发布在这两个仓库中，在实际开发中需要将maven-releases设置为可以重复发布
搭建Maven私有仓库 - 图8

Maven配置使用Nexus

  1. <?xml version="1.0" encoding="UTF-8"?>
  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
  12.     http://www.apache.org/licenses/LICENSE-2.0
  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. -->
  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.   -->
  54.   <localRepository>${user.home}/.m2/repository</localRepository>
  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.   -->
  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.   -->
  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>
  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>
  107.   <!-- servers
  108.    | 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.     <!-- server
  113.      | Specifies the authentication information to use when connecting to a particular server, identified by
  114.      | 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 are
  117.      |       used together.
  118.      |
  119.     -->
  121.     <server>
  122.       <id>releases</id>
  123.       <username>admin</username>
  124.       <password>admin23</password>
  125.     </server>
  127.     <server>
  128.       <id>snapshots</id>
  129.       <username>admin</username>
  130.       <password>admin123</password>
  131.     </server>
  133.     <!-- Another sample, using keys to authenticate.
  134.     <server>
  135.       <id>siteServer</id>
  136.       <privateKey>/path/to/private/key</privateKey>
  137.       <passphrase>optional; leave empty if not used.</passphrase>
  138.     </server>
  139.     -->
  140.   </servers>
  142.   <!-- mirrors
  143.    | This is a list of mirrors to be used in downloading artifacts from remote repositories.
  144.    |
  145.    | It works like this: a POM may declare a repository to use in resolving certain artifacts.
  146.    | However, this repository may have problems with heavy traffic at times, so people have mirrored
  147.    | it to several places.
  148.    |
  149.    | That repository definition will have a unique id, so we can create a mirror reference for that
  150.    | repository, to be used as an alternate download site. The mirror site will be the preferred
  151.    | server for that repository.
  152.    |-->
  153.   <mirrors>
  154.     <!-- mirror
  155.      | Specifies a repository mirror site to use instead of a given repository. The repository that
  156.      | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
  157.      | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
  158.      |
  159.     -->
  160.     <mirror>
  161.       <id>HolliParkMirror</id>
  162.       <mirrorOf>*</mirrorOf>
  163.       <name>HolliPark Repository Mirror.</name>
  164.       <url>http://localhost:8082/nexus/repository/maven-public/</url>
  165.     </mirror>
  167.   </mirrors>
  169.   <!-- profiles
  170.    | This is a list of profiles which can be activated in a variety of ways, and which can modify
  171.    | the build process. Profiles provided in the settings.xml are intended to provide local machine-
  172.    | specific paths and repository locations which allow the build to work in the local environment.
  173.    |
  174.    | For example, if you have an integration testing plugin - like cactus - that needs to know where
  175.    | your Tomcat instance is installed, you can provide a variable here such that the variable is
  176.    | dereferenced during the build process to configure the cactus plugin.
  177.    |
  178.    | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
  179.    | section of this document (settings.xml) - will be discussed later. Another way essentially
  180.    | relies on the detection of a system property, either matching a particular value for the property,
  181.    | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
  182.    | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
  183.    | Finally, the list of active profiles can be specified directly from the command line.
  184.    |
  185.    | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
  186.    |       repositories, plugin repositories, and free-form properties to be used as configuration
  187.    |       variables for plugins in the POM.
  188.    |
  189.    |-->
  190.   <profiles>
  191.     <profile>
  192.       <id>HolliPark</id>
  193.       <repositories>
  194.         <repository>
  195.           <id>nexus</id>
  196.           <name>Public Repositories</name>
  197.           <url>http://localhost:8082/nexus/repository/maven-public/</url>
  198.           <releases>
  199.             <enabled>true</enabled>
  200.           </releases>
  201.         </repository>
  203.         <repository>
  204.           <id>central</id>
  205.           <name>Central Repositories</name>
  206.           <url>http://localhost:8082/nexus/repository/maven-central/</url>
  207.           <releases>
  208.             <enabled>true</enabled>
  209.           </releases>
  210.           <snapshots>
  211.             <enabled>false</enabled>
  212.           </snapshots>
  213.         </repository>
  215.         <repository>
  216.           <id>release</id>
  217.           <name>Release Repositories</name>
  218.           <url>http://localhost:8082/nexus/repository/maven-releases/</url>
  219.           <releases>
  220.             <enabled>true</enabled>
  221.           </releases>
  222.           <snapshots>
  223.             <enabled>false</enabled>
  224.           </snapshots>
  225.         </repository>
  227.         <repository>
  228.           <id>snapshots</id>
  229.           <name>Snapshot Repositories</name>
  230.           <url>http://localhost:8082/nexus/repository/maven-snapshots/</url>
  231.           <releases>
  232.             <enabled>true</enabled>
  233.           </releases>
  234.           <snapshots>
  235.             <enabled>true</enabled>
  236.           </snapshots>
  237.         </repository>
  238.       </repositories>
  240.       <pluginRepositories>
  241.         <pluginRepository>
  242.           <id>plugins</id>
  243.           <name>Plugin Repositories</name>
  244.           <url>http://localhost:8082/nexus/repository/maven-public/</url>
  245.         </pluginRepository>
  246.       </pluginRepositories>
  247.     </profile>
  248.     <!-- profile
  249.      | Specifies a set of introductions to the build process, to be activated using one or more of the
  250.      | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
  251.      | or the command line, profiles have to have an ID that is unique.
  252.      |
  253.      | An encouraged best practice for profile identification is to use a consistent naming convention
  254.      | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
  255.      | This will make it more intuitive to understand what the set of introduced profiles is attempting
  256.      | to accomplish, particularly when you only have a list of profile id's for debug.
  257.      |
  258.      | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
  259.     <profile>
  260.       <id>jdk-1.4</id>
  262.       <activation>
  263.         <jdk>1.4</jdk>
  264.       </activation>
  266.       <repositories>
  267.         <repository>
  268.           <id>jdk14</id>
  269.           <name>Repository for JDK 1.4 builds</name>
  270.           <url>http://www.myhost.com/maven/jdk14</url>
  271.           <layout>default</layout>
  272.           <snapshotPolicy>always</snapshotPolicy>
  273.         </repository>
  274.       </repositories>
  275.     </profile>
  276.     -->
  278.     <!--
  279.      | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
  280.      | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
  281.      | might hypothetically look like:
  282.      |
  283.      | ...
  284.      | <plugin>
  285.      |   <groupId>org.myco.myplugins</groupId>
  286.      |   <artifactId>myplugin</artifactId>
  287.      |
  288.      |   <configuration>
  289.      |     <tomcatLocation>${tomcatPath}</tomcatLocation>
  290.      |   </configuration>
  291.      | </plugin>
  292.      | ...
  293.      |
  294.      | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
  295.      |       anything, you could just leave off the <value/> inside the activation-property.
  296.      |
  297.     <profile>
  298.       <id>env-dev</id>
  300.       <activation>
  301.         <property>
  302.           <name>target-env</name>
  303.           <value>dev</value>
  304.         </property>
  305.       </activation>
  307.       <properties>
  308.         <tomcatPath>/path/to/tomcat/instance</tomcatPath>
  309.       </properties>
  310.     </profile>
  311.     -->
  312.   </profiles>
  314.   <!-- activeProfiles
  315.    | List of profiles that are active for all builds.
  316.    |
  317.   <activeProfiles>
  318.     <activeProfile>alwaysActiveProfile</activeProfile>
  319.     <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  320.   </activeProfiles>
  321.   -->
  323.   <activeProfiles>
  324.     <activeProfile>HolliPark</activeProfile>
  325.   </activeProfiles>
  327. </settings>

创建私有公库

创建普通的maven项目

搭建Maven私有仓库 - 图9

修改项目的pom.xml

在pom文件中加入distributionManagement节点，注意：pom.xml中repository里的id需要和.m2中setting.xml里的server id名称保持一致

  1. <distributionManagement>
  2.     <repository>
  3.         <id>releases</id>
  4.         <name>Nexus Release Repository</name>
  5.         <url>http://localhost:8082/nexus/repository/maven-releases/</url>
  6.     </repository>
  7.     <snapshotRepository>
  8.         <id>snapshots</id>
  9.         <name>Nexus Snapshot Repository</name>
  10.         <url>http://localhost:8082/nexus/repository/maven-snapshots/</url>
  11.     </snapshotRepository>
  12. </distributionManagement>

发布私有公库

执行部署命令即可发布。

  1. mvn deploy

登录Nexus，查看对应的仓库已经有相关的依赖包了
搭建Maven私有仓库 - 图10

注意以下几点：

  • 若项目版本号末尾带有 -SNAPSHOT，则会发布到snapshots快照版本仓库
  • 若项目版本号末尾带有 -RELEASES 或什么都不带，则会发布到releases正式版本仓库

项目中配置连接

启动完成了，那怎么配置本地（你的开发环境）和 这个私有库的连接呢？
Step1: 找到你本地的maven安装目录，我的在F:\ProgramFiles\apache-maven-3.5.0。 然后呢，到conf目录下，打开setting.xml。 找到这个标签，在里面添加两个配置。

  1. <server>
  2.         <id>nexus</id>
  3.         <username>admin</username>
  4.         <password>admin123</password>
  5.     </server>
  7.     <server>
  8.         <id>nexus</id>
  9.         <username>admin</username>
  10.         <password>admin123</password>
  11.     </server>

完了之后呢，打开你的Maven项目，在pom.xml里面加两段.

  1. #a.先看配置远程仓库地址
  2. <repositories>
  3.         <!-- 配置nexus远程仓库 -->
  4.         <repository>
  5.             <id>nexus</id>
  6.             <name>Nexus Snapshot Repository</name>
  7.             <url>http://192.168.0.1:8081/repository/maven-public/</url>
  8.             <releases>
  9.                 <enabled>true</enabled>
  10.             </releases>
  11.             <snapshots>
  12.                 <enabled>false</enabled>
  13.             </snapshots>
  14.         </repository>
  15.     </repositories>
  17. b.打包时发布jar包到私有仓库   
  18. <distributionManagement>
  19.         <repository>
  20.             <id>nexus</id>
  21.             <name>Releases</name>
  22.             <url>http://192.168.0.1:8081/repository/maven-releases</url>
  23.         </repository>
  24.         <snapshotRepository>
  25.             <id>nexus</id>
  26.             <name>Snapshot</name>
  27.             <url>http://192.168.0.1:8081/repository/maven-snapshots</url>
  28.         </snapshotRepository>
  29.     </distributionManagement>