Nexus Repository Manager 3 私服搭建 —— windows版

原文來自： https://blog.csdn.net/cuncaojin/article/details/81270897

nexus3

本文安裝的是免費版：Nexus Repository OSS

---

下載

最新版本下載鏈接1 
最新版本下載鏈接2 
或到 https://my.sonatype.com/ 可以下載nexus2和3兩大版本

參考頁面： 

安裝
我下載的包爲：“nexus-3.13.0-01-win64.zip”，我的路徑：”D:\nexus\nexus-3.13.0-01-win64.zip”

1，解壓到文件夾“nexus-3.13.0-01-win64

 

1，sonatype-work目錄包含Nexus生成的配置文件，日誌文件，倉庫文件，索引文件，插件文件，緩存文件等等。
2， 默認配置文件：”D:\nexus\nexus-3.13.0-01-win64\nexus-3.13.0-01\etc\nexus-default.properties”

application-port=8081
application-host=0.0.0.0
nexus-args=${jetty.etc}/jetty.xml,${jetty.etc}/jetty-http.xml,${jetty.etc}/jetty-requestlog.xml
nexus-context-path=/


# Nexus section

nexus-edition=nexus-pro-edition
nexus-features=\
nexus-pro-feature

2， 進入到“D:\nexus\nexus-3.13.0-01-win64\nexus-3.13.0-01\bin”，cmd命令進入到該路徑，執行: nexus.exe/install

        1，此步驟會安裝nexus服務，可以到系統服務（cmd → services.msc）中查看nexus服務是否存在。
        2，注意： 該指令中間是一個斜槓，不是空格也沒有空格！

3，執行nexus.exe/run，可能會有編碼等報錯，不用關心，最後看有沒有，看到就OK了
 

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


Started Sonatype Nexus OSS 3.13.0-01

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

4， 訪問 http://localhost:8081 試試看，默認賬號和密碼爲：

admin 
admin123

參考圖片： 

創建用戶
在配置頁面（齒輪圖標），選擇Security - User，點擊create user。創建用戶後就可以退出使用新用戶登錄了。

創建maven倉庫
在配置界面，選擇Repository - repositories，點擊create repository，選擇maven2(hosted)上傳自己的jar、war到本地倉庫
 

hosted，本地倉庫，通常我們會部署自己的構件到這一類型的倉庫。如公司的第二方庫。
proxy，代理倉庫，被用來代理遠程的公共倉庫，如maven中央倉庫。
group，倉庫組，用來組合多個hosted/proxy倉庫，當你的項目希望在多個repository使用資源時就不需要多次引用了，只需要引用一個group即可。

上傳（將項目dao工程打成jar包發佈到私服）

1. 首先啓動nexus服務

2. 配置：

   1. maven配置文件 settings.xml中，設置倉庫及用戶名密碼

<!-- id:倉庫名、nexus登錄賬號及密碼 -->
<server>
  <id>cuncaojin_hosted</id>
  <username>cuncaojin</username>
  <password>root</password>
</server>

2，項目中pom.xml中配置倉庫及倉庫位置

<!-- id:倉庫名 url:倉庫url -->
<distributionManagement>
    <repository>
        <id>cuncaojin_hosted</id>
        <url>http://localhost:8081/repository/cuncaojin_hosted/</url>
    </repository>
</distributionManagement>

3，對工程執行maven命令：deploy，即可將項目打包部署到以上配置指定的倉庫

參考圖片： 

下載（從倉庫下載jar包到工程）

1. maven配置文件settings.xml配置

   • 配置1.1

<!-- profiles節點添加如下內容，部分內容自行修改 -->
<profile>   
    <!--profile的id-->
    <id>dev</id>   

    <repositories>   
      <repository>
        <!--倉庫id，repositories可以配置多個倉庫，保證id不重複-->
        <id>cuncaojin_hosted</id>   
        <!--倉庫地址，即nexus倉庫組的地址-->
        <url>http://localhost:8081/repository/cuncaojin_hosted/</url>   
        <!--是否下載releases構件-->
        <releases>   
          <enabled>true</enabled>   
        </releases>   
        <!--是否下載snapshots構件-->
        <snapshots>   
          <enabled>true</enabled>   
        </snapshots>   
      </repository>   
    </repositories>  

    <!-- 此次測試沒有使用到此配置 -->
    <pluginRepositories>  
        <!-- 插件倉庫，maven的運行依賴插件，也需要從私服下載插件 -->
        <pluginRepository>  
            <!-- 插件倉庫的id不允許重複，如果重複後邊配置會覆蓋前邊 -->
            <id>public</id>  
            <name>Public Repositories</name>  
            <url>http://localhost:8081/nexus/content/groups/public/</url>  
        </pluginRepository>  
    </pluginRepositories>  
</profile>  

2 配置1.2

<!-- 必須激活，否則profiles中相關配置不起效果 -->
<activeProfiles>
  <activeProfile>dev</activeProfile>
</activeProfiles>

2.項目pom.xml中配置

直接導入依賴即可，如圖： 

參考致謝
https://blog.csdn.net/Bleachswh/article/details/53152805
https://www.cnblogs.com/kevingrace/p/6201984.html
https://www.cnblogs.com/acm-bingzi/p/mavenNexusPath.html
https://blog.csdn.net/fygkchina/article/details/62976387

settings.xml配置參考
 

“D:\apache-maven-3.5.3\conf\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.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>D:\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>deploymentRepo</id>
      <username>repouser</username>
      <password>repopwd</password>
    </server>
    -->

    <!-- nexus倉庫 -->
    <server>
      <id>cuncaojin_hosted</id>
      <username>cuncaojin</username>
      <password>root</password>
    </server>

    <server>
      <id>cuncaojin_releases_maven_hosted</id>
      <username>cuncaojin</username>
      <password>root</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>
     -->

  </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>jdk-1.8</id>

        <activation>    
            <activeByDefault>true</activeByDefault>    
            <jdk>1.8</jdk>    
        </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>

    <profile>   
        <!--profile的id-->
        <id>dev</id>   

        <repositories>   
          <repository>
            <!--倉庫id，repositories可以配置多個倉庫，保證id不重複-->
            <id>cuncaojin_hosted</id>   
            <!--倉庫地址，即nexus倉庫組的地址-->
            <url>http://localhost:8081/repository/cuncaojin_hosted/</url>   
            <!--是否下載releases構件-->
            <releases>   
              <enabled>true</enabled>   
            </releases>   
            <!--是否下載snapshots構件-->
            <snapshots>   
              <enabled>true</enabled>   
            </snapshots>   
          </repository>   
        </repositories>  

        <pluginRepositories>  
            <!-- 插件倉庫，maven的運行依賴插件，也需要從私服下載插件 -->
            <pluginRepository>  
                <!-- 插件倉庫的id不允許重複，如果重複後邊配置會覆蓋前邊 -->
                <id>public</id>  
                <name>Public Repositories</name>  
                <url>http://localhost:8081/nexus/content/groups/public/</url>  
            </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>

  <!-- 必須激活，否則profiles中相關配置不起效果 -->
  <activeProfiles>
    <activeProfile>dev</activeProfile>
  </activeProfiles>

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