三種Maven搭建私服的管理軟件

Artifactory搭建maven私服

1 概 述

在我們的項目開發中通常希望將很多公用的東西提成一個工具工程，然后這個工程可以以maven依賴的形式讓其他項目進行添加。這就是以使用Artifactory來建立maven私服。

2具體步驟

（1）下載Artifactory。下載地址：Artifactory

（2）直接解壓下載好的zip文件，並且點擊...\artifactory-3.9.2\bin目錄下的artifactory.bat進行安裝，當出現

###########################################################
### Artifactory successfully started (20.911 seconds) ###
###########################################################
則表示安裝完成。 

 

 

 

現在我們就可以直接點擊deploy向maven私服發包了

注意在上面deploy之前我們一定要給我們的maven授權，因此需要在我們的settings.xml文件中的services節點中加入以下節點

<server>
      <id>artifactory</id>
      <username>admin</username>
      <password>password</password>
 </server>

 

Nexus搭建maven私服

下載地址：https://www.sonatype.com/download-nexus-repo-oss

版本/收費/免費：Nexus Repository Manager 倉庫管理有2個版本，專業版和oss版，oss版是免費的，專業版是收費的，我們使用oss版。

簡介

nexus是一個強大的maven倉庫管理器,它極大的簡化了本地內部倉庫的維護和外部倉庫的訪問.

nexus是一套開箱即用的系統不需要數據庫,它使用文件系統加Lucene來組織數據

nexus使用ExtJS來開發界面,利用Restlet來提供完整的REST APIs,通過IDEA和Eclipse集成使用

nexus支持webDAV與LDAP安全身份認證.

nexus提供了強大的倉庫管理功能,構件搜索功能,它基於REST,友好的UI是一個extjs的REST客戶端,占用較少的內存,基於簡單文件系統而非數據庫.

為什么使用

• 節省外網帶寬。
• 加速Maven構建。
• 部署第三方構件。
• 提高穩定性，增強控制。
• 降低中央倉庫的負荷。
• 控制和審計
• 建立本地內部公用倉庫

私服倉庫的工作流程

Nexus倉庫類型介紹

hosted，本地倉庫，通常我們會部署自己的構件到這一類型的倉庫。比如公司的第二方庫。

proxy，代理倉庫，它們被用來代理遠程的公共倉庫，如maven中央倉庫。

group，倉庫組，用來合並多個hosted/proxy倉庫，當你的項目希望在多個repository使用資源時就不需要多次引用了，只需要引用一個group即可。

管理本地倉庫

我們前面講到類型為hosted的為本地倉庫，Nexus預定義了3個本地倉庫，分別是Releases, Snapshots, 3rd Party. 分別講一下這三個預置的倉庫都是做什么用的:

Releases: 這里存放我們自己項目中發布的構建, 通常是Release版本的, 比如我們自己做了一個FTP Server的項目, 生成的構件為ftpserver.war, 我們就可以把這個構建發布到Nexus的Releases本地倉庫. 關於符合發布后面會有介紹.

Snapshots:這個倉庫非常的有用, 它的目的是讓我們可以發布那些非release版本, 非穩定版本, 比如我們在trunk下開發一個項目,在正式release之前你可能需要臨時發布一個版本給你的同伴使用, 因為你的同伴正在依賴你的模塊開發, 那么這個時候我們就可以發布Snapshot版本到這個倉庫, 你的同伴就可以通過簡單的命令來獲取和使用這個臨時版本.

3rd Party:顧名思義, 第三方庫, 你可能會問不是有中央倉庫來管理第三方庫嘛,沒錯, 這里的是指可以讓你添加自己的第三方庫, 比如有些構件在中央倉庫是不存在的. 比如你在中央倉庫找不到Oracle 的JDBC驅動, 這個時候我們就需要自己添加到3rdparty倉庫。

Windows上安裝Nexus

鏈接：https://pan.baidu.com/s/14pJELodRvqY_XkSvwBHwjw 
提取碼：kkys 

官方安裝文檔:https://help.sonatype.com/repomanager3/installation/installation-methods

免安裝的，下載下來，解壓直接運行即可。

1.解壓

2.配置下環境變量

3.運行起來即可

命令集:  start， stop，  restart，  force-reload

4.校驗

打開 http://localhost:8081/

出現如下界面即可，默認賬號密碼：admin/admin123

Maven用到的Repositories說明：

maven-central：maven中央庫，默認從https://repo1.maven.org/maven2/拉取jar

maven-releases：私庫發行版jar

maven-snapshots：私庫快照（調試版本）jar

maven-public：倉庫分組，把上面三個倉庫組合在一起對外提供服務，在本地maven基礎配置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>D:\Maven\repository</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>release</id>
      <username>admin</username>
      <password>admin123</password>
    </server>
    
    <server>
      <id>snapshots</id>
      <username>admin</username>
      <password>admin123</password>
    </server>
    
    

    <!-- Another sample, using keys to authenticate.
    <server>
      <id>release</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>
     -->
  </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>
    -->

    <!--
     | 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>

    </profile>
    -->
    
     <profile>
      <id>default_profile</id>
      <repositories>
        <!--包含需要連接到遠程倉庫的信息 -->
        <repository>
          <!--遠程倉庫唯一標識 -->
          <id>zhanglonghao_repo</id>
          <!--遠程倉庫名稱 -->
          <name>zhanglonghao_repo</name>
          <!--如何處理遠程倉庫里發布版本的下載 -->
          <releases>
            <!--true或者false表示該倉庫是否為下載某種類型構件（發布版，快照版）開啟。 -->
            <enabled>true</enabled>
            <!--該元素指定更新發生的頻率。Maven會比較本地POM和遠程POM的時間戳。這里的選項是：always（一直），daily（默認，每日），interval：X（這里X是以分鍾為單位的時間間隔），或者never（從不）。 -->
            <updatePolicy>never</updatePolicy>
            <!--當Maven驗證構件校驗文件失敗時該怎么做-ignore（忽略），fail（失敗），或者warn（警告）。 -->
            <checksumPolicy>warn</checksumPolicy>
          </releases>
          <!--如何處理遠程倉庫里快照版本的下載。有了releases和snapshots這兩組配置，POM就可以在每個單獨的倉庫中，為每種類型的構件采取不同的策略。例如，可能有人會決定只為開發目的開啟對快照版本下載的支持。參見repositories/repository/releases元素 -->
          <snapshots>
            <!--true或者false表示該倉庫是否為下載某種類型構件（發布版，快照版）開啟。 -->
            <enabled>true</enabled>
            <!--該元素指定更新發生的頻率。Maven會比較本地POM和遠程POM的時間戳。這里的選項是：always（一直），daily（默認，每日），interval：X（這里X是以分鍾為單位的時間間隔），或者never（從不）。 -->
            <updatePolicy>always</updatePolicy>
            <!--當Maven驗證構件校驗文件失敗時該怎么做-ignore（忽略），fail（失敗），或者warn（警告）。 -->
            <checksumPolicy>warn</checksumPolicy>
          </snapshots>
          <!--遠程倉庫URL，按protocol://hostname/path形式 -->
          <url>http://maven.zhanglonghao.work:8081/nexus/content/groups/public</url>
          <!--用於定位和排序構件的倉庫布局類型-可以是default（默認）或者legacy（遺留）。Maven 2為其倉庫提供了一個默認的布局；然而，Maven 1.x有一種不同的布局。我們可以使用該元素指定布局是default（默認）還是legacy（遺留）。 -->
          <layout>default</layout>
        </repository>
      </repositories>
      
      <pluginRepositories>  
        <pluginRepository>  
          <id>maven-net-cn</id>  
          <name>Maven China Mirror</name>  
          <url>http://maven.zhanglonghao.work:8081/nexus/content/groups/public</url>  
          <releases>  
            <enabled>true</enabled>  
          </releases>  
          <snapshots>  
            <enabled>true</enabled>  
          </snapshots>      
        </pluginRepository>  
      </pluginRepositories> 
  
    </profile>
  </profiles>
 


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

</settings>

Apache Ar-chiva搭建maven私服（不常用）

一、環境准備

安裝JDK

步驟略

二、安裝Archiva服務器

從https://archiva.apache.org下載Archiva。
進入bin目錄執行archiva start即可啟動Archiva。
Nexus 默認的端口是8080，如果要更改端口可以修改conf/jetty文件。
啟動Archiva會要求設置管理員賬戶admin的密碼，我設置密碼為admin123。

三、Maven 和 Gradle 客戶端配置

現在使用Maven和Gradle做構建工具都很普遍，下面分別說明兩個工具的使用。

1、Maven配置

修改settings.xml 文件

Maven配置文件更改，修改<Maven安裝目錄>/conf/settings.xml文件，可以參考下面的文件：

<?xml version="1.0" encoding="UTF-8"?>
<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">
  <pluginGroups>
  </pluginGroups>
  <proxies>
  </proxies>
  <servers>
    <server>
      <id>archiva-releases</id>
      <username>admin</username>
      <password>admin123</password>
    </server>
    <server>
      <id>archiva-snapshots</id>
      <username>admin</username>
      <password>admin123</password>
    </server>
  </servers>
  <mirrors>
    <mirror> 
      <id>archiva-releases</id> 
      <mirrorOf>internal</mirrorOf> 
      <url>http://localhost:8080/repository/internal</url> 
    </mirror>
    <mirror> 
      <id>archiva-snapshots</id>
      <mirrorOf>snapshots</mirrorOf> 
      <url>http://localhost:8080/repository/snapshots</url> 
    </mirror>
  </mirrors>
  <profiles>
    <profile>
      <activation>
        <activeByDefault>true</activeByDefault>
      </activation>
      <repositories>
        <repository>
          <id>internal</id>
          <name>Archiva Managed Internal Repository</name>
          <url>http://localhost:8080/repository/internal</url>
          <releases>
            <enabled>true</enabled>
          </releases>
          <snapshots>
            <enabled>false</enabled>
          </snapshots>
        </repository>
        <repository>
          <id>snapshots</id>
          <name>Archiva Managed Snapshots Repository</name>
          <url>http://localhost:8080/repository/snapshots</url>
          <releases>
            <enabled>false</enabled>
          </releases>
          <snapshots>
            <enabled>true</enabled>
          </snapshots>
        </repository>
      </repositories>
    </profile>
  </profiles>
</settings>

Maven項目的pom.xml配置

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <groupId>io.github.redexpress</groupId>
  <artifactId>demo</artifactId>
  <version>1.0</version>
  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <maven.compiler.source>1.8</maven.compiler.source>
    <maven.compiler.target>1.8</maven.compiler.target>
  </properties>
  <dependencies>
    <dependency>
        <groupId>junit</groupId>
        <artifactId>junit</artifactId>
        <version>4.12</version>
        <scope>test</scope>
    </dependency>
  </dependencies>
  <distributionManagement>
      <repository>
          <id>archiva-releases</id>
          <url>http://localhost:8080/repository/internal</url>
          <uniqueVersion>true</uniqueVersion>
      </repository>
      <snapshotRepository>
          <id>archiva-snapshots</id>
          <url>http://localhost:8080/repository/snapshots</url>
      </snapshotRepository>
  </distributionManagement>
</project>

使用mvn deploy命令即可發布jar到Nexus 私服。

2、Gradle 配置

build.gradle

apply plugin: 'java'
apply plugin: 'maven-publish'

group = 'io.github.redexpress'
version = '1.0'

sourceCompatibility = 1.8
targetCompatibility = 1.8

tasks.withType(JavaCompile) {
    options.encoding = 'UTF-8'
}

repositories {
     maven { url "http://repo.maven.apache.org/maven2" }
     maven { url "http://localhost:8080/repository/internal" }
     maven { url "http://localhost:8080/repository/snapshots" }
}

publishing {
    repositories {
        maven {
            credentials {
                username 'admin'
                password 'admin123'
            }
            def releasesRepoUrl = 'http://localhost:8080/repository/internal'
            def snapshotsRepoUrl = 'http://localhost:8080/repository/snapshots'
            url = version.endsWith('SNAPSHOT') ? snapshotsRepoUrl : releasesRepoUrl
        }
    }
    publications {
        maven(MavenPublication) {
            from components.java
        }
    }
}

dependencies {
    testCompile 'junit:junit:4.12'
}

settings.gradle

rootProject.name = 'demo'