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

最新推荐文章于 2024-07-12 16:12:56 发布

Ynzo

最新推荐文章于 2024-07-12 16:12:56 发布

阅读量535

点赞数 1

分类专栏： Nexus Repository Manager 3 文章标签： Nexus Repository Manager 3

Nexus Repository Manager 3 专栏收录该内容

1 篇文章 0 订阅

订阅专栏

原文来自： 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包发布到私服）

首先启动nexus服务
配置：
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包到工程）

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>