1.下载maven解压到指定目录，并配置环境变量 M2_HOME为maven解压目录

2.path中增加 %M2_HOME%\bin， 并确认 mvn -v 正确

3.下载nexus http://www.sonatype.org/nexus/archived/ 解压到指定目录

4.根据部署系统，执行D:\soft\nexus-2.12.0-01-bundle\nexus-2.12.0-01\bin\jsw\windows-x86-64\console-nexus.bat  【我用的是win7 64位】

5.确认http://localhost:8081/nexus/ 能正常访问

6.用admin/admin123登录（为了安全，请及时修改密码）

7.打开 repositories 并选中 central 下 configuration选项卡，设置Download Remote Indexes 为true并保存

8.选中 central 并右键，点击 repair index （过段时间在browse index中查看）

9.根据需要就可以选中 3rd party下的artifact upload上传私有的jar包了，完毕可以看到对应的artifact xml

<dependency>

  <groupId>com.xiaochangwei</groupId>

  <artifactId>nexus-demo</artifactId>

  <version>0.01</version>

</dependency>

10.修改maven的setting.xml

  <mirrors>

    <mirror>

      <id>nexus-public-snapshots</id>

      <mirrorOf>public-snapshots</mirrorOf>

      <url>http://localhost:8081/nexus/content/groups/public-snapshots</url>

    </mirror>

    <mirror>

      <!--This sends everything else to /public -->

      <id>nexus</id>

      <mirrorOf>*</mirrorOf>

      <url>http://localhost:8081/nexus/content/groups/public</url>

    </mirror>

  </mirrors>

11.然后就可以在项目中使用搭建好的私服了。

下面讲发布公司项目jar包到私服供团队成员使用

1.在项目pom中增加发布地址

<distributionManagement>

        <repository>

            <id>user-release</id>

            <name>user release version</name>

            <url>http://localhost:8081/nexus/content/repositories/releases/</url>

        </repository>

        <snapshotRepository>

            <id>user-snapshots</id>

            <name>user snapshots version</name>

            <url>http://localhost:8081/nexus/content/repositories/snapshots/</url>

        </snapshotRepository>

    </distributionManagement>

2.修改maven的settings.xml

#定义profile并制定默认激活项

  <profiles>

    <profile>

      <id>development</id>

      <repositories>

        <repository>

          <id>central</id>

          <url>http://central</url>

          <releases><enabled>true</enabled></releases>

          <snapshots><enabled>true</enabled></snapshots>

        </repository>

      </repositories>

     <pluginRepositories>

        <pluginRepository>

          <id>central</id>

          <url>http://central</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>alwaysActiveProfile</activeProfile>

    <activeProfile>anotherAlwaysActiveProfile</activeProfile>

  </activeProfiles>

  -->

  <activeProfiles>

    <activeProfile>development</activeProfile>

  </activeProfiles>

#定义用户认证

  <servers>

   <server>

      <id>user-release</id>

      <username>deployment</username>

      <password>deployment123</password>

    </server>

    <server>

      <id>user-snapshots</id>

      <username>deployment</username>

      <password>deployment123</password>

    </server>

  </servers>

需要注意的是，这里的id和 第1步的id要完全一致

完整的settins文件如下

 <?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:\soft\apache-maven-3.3.9\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>adxNexus</id>

       <username>admin</username>

       <password>123456</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>

     -->

     <server>

       <id>user-release</id>

       <username>deployment</username>

       <password>deployment123</password>

     </server>

     <server>

       <id>user-snapshots</id>

       <username>deployment</username>

       <password>deployment123</password>

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

       <!--This is used to direct the public snapshots repo in the

           profile below over to a different nexus group -->

       <id>nexus-public-snapshots</id>

       <mirrorOf>public-snapshots</mirrorOf>

       <url>http://localhost:8081/nexus/content/groups/public-snapshots</url>

     </mirror>

     <mirror>

       <!--This sends everything else to /public -->

       <id>nexus</id>

       <mirrorOf>*</mirrorOf>

       <url>http://localhost:8081/nexus/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.

     -->

     <!--

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

     -->

     <profile>

       <id>development</id>

       <repositories>

         <repository>

           <id>central</id>

           <url>http://central</url>

           <releases><enabled>true</enabled></releases>

           <snapshots><enabled>true</enabled></snapshots>

         </repository>

       </repositories>

      <pluginRepositories>

         <pluginRepository>

           <id>central</id>

           <url>http://central</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>alwaysActiveProfile</activeProfile>

     <activeProfile>anotherAlwaysActiveProfile</activeProfile>

   </activeProfiles>

   -->

   <activeProfiles>

     <activeProfile>development</activeProfile>

   </activeProfiles>

 </settings>

验证发布：

pom如下

<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>com.xiaochangwei</groupId>

    <artifactId>nexus-deploy-demo</artifactId>

    <version>0.0.9527-SNAPSHOT</version>

    <packaging>jar</packaging>

    <name>nexus</name>

    <url>http://maven.apache.org</url>

    <properties>

        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

    </properties>

    <dependencies>

        <dependency>

            <groupId>junit</groupId>

            <artifactId>junit</artifactId>

            <version>3.8.1</version>

            <scope>test</scope>

        </dependency>

    </dependencies>

    <!-- 发布项目的配置 -->

    <distributionManagement>

        <repository>

            <id>user-release</id>

            <name>user release version</name>

            <url>http://localhost:8081/nexus/content/repositories/releases/</url>

        </repository>

        <snapshotRepository>

            <id>user-snapshots</id>

            <name>user snapshots version</name>

            <url>http://localhost:8081/nexus/content/repositories/snapshots/</url>

        </snapshotRepository>

    </distributionManagement>

</project>

进入项目根目录，执行mvn clean deploy

执行成功后打开nexus查看

Nexus私服搭建使用及发布jar包到私服上供团队其他成员使用的更多相关文章

  1. maven发布jar包到私服

    1.setting.xml配置 <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi=&quo ...

  2. Maven入门：使用Nexus搭建Maven私服及上传下载jar包

    一. 私服搭建及配置 1 . 私服简介 私服是架设在局域网的一种特殊的远程仓库,目的是代理远程仓库及部署第三方构件.有了私服之后,当 Maven 需要下载构件时,直接请求私服,私服上存在则下载到本地仓 ...

  3. 使用Sonatype Nexus搭建Maven私服后,如何添加第三方JAR包

    使用Sonatype Nexus搭建Maven私服后如何添加第三方JAR包 步骤如下 1.打开nexus地址,进行登录 2.登录Nexus后,点击右侧的“Repositories”,显示当前Nexus ...

  4. Nexus-在项目中使用Maven私服，Deploy到私服、上传第三方jar包、在项目中使用私服jar包

    场景 Ubuntu Server 上使用Docker Compose 部署Nexus(图文教程): https://blog.csdn.net/BADAO_LIUMANG_QIZHI/article/ ...

  5. 实测Maven上传jar包到私服的方法归纳

    Hello,各位小伙伴大家好,我是小栈君.好久不见,最近因为工作的缘故,导致了更新变慢,但是小栈君也在积极的做素材的规划,毕竟学习知识点的归纳和提炼需要一定的时间. 所以还请大家多多见谅,下一期的分享 ...

  6. 如何发布jar包到maven中央仓库

    自使用maven以来,没少使用maven中央仓库中的各种jar包,方便有效,但是咱们也不能总是只取不予,也应该懂得奉献,当你写好了一个十分好用的jar包,想贡献出去给大家使用的时候,应该怎么做呢?当然 ...

  7. maven上传本地jar包到私服

    场景 1. 本地jar包上传到私服 思路: 1. maven的settting.xml配置私服的帐号密码 2. pom.xml配置上传的地址 3. 执行 mvn deploy 部署jar包到私服 步骤 ...

  8. Maven上传jar包到私服

    1.认证,在M2_HOME/conf/settings.xml配置用户名密码 <server> <id>releases</id> <username> ...

  9. 发布jar包到远端github仓库使用(将github仓库当作maven仓库)

    今天把单点登陆的core模块搬到了github仓库 并且利用github仓库作为maven仓库 在项目中进行了引用 1. 起初看技术博客没有完全引入进来,调整了一下OK了 2. 还可以将其他模块或者工 ...

随机推荐

  1. A----奇怪的玩意

      题目: 我们的化学生物学家发明了一种新的叫stripies非常神奇的生命.该stripies是透明的无定形变形虫似的生物,生活在果冻状的营养培养基平板菌落.大部分的时间stripies在移动.当他 ...

  2. git - 远程分支

    对于用户来说,git给人提交到本地的机会.我们可以在自己的机器上创建不同的branch,来测试和存放不同的代码. 对于代码管理员而言,git有许多优良的特性.管理着不同的分支,同一套源代码可以出不一样 ...

  3. Serv-U权限设置规则

    Serv-U有服务器--域--组--用户四级账号管理规则,每一级都有相应的根目录,目录访问规则和虚拟路径的设置. 同样其他一些重复设置还有很多,如此很容易给人造成混乱--如果我哪里都设置的话会不会造成 ...

  4. jQuery请求后台接口

    function test() { console.log("请求准备发送"); $.ajax({ type : "POST", url : "/ap ...

  5. juquery 中 size()和length的区别 以及优缺点

    size()是jQuery提供的函数,而length是属性(不带括号).jQuery提供的源代码是这样的:size: function() {return this.length;}其实也就是说,在j ...

  6. node.js fs.open 和 fs.write 读取文件和改写文件

    Node.js的文件系统的Api //公共引用 var fs = require('fs'), path = require('path'); 1.读取文件readFile函数 //readFile( ...

  7. Web聊天应用中的表情插件

    聊天应用中的表情插件 用于即时聊天应用的图片表情插件,具有展示表情.插入表情和表情编解码的功能 项目地址 看代码 看demo 原理介绍 web端的即时聊天中看到的表情,其实就是一张张表情图片,通过im ...

  8. Go语言学习笔记（六）net

    加 Golang学习 QQ群共同学习进步成家立业工作 ^-^ 群号:96933959 net import "net" net包提供了可移植的网络I/O接口,包括TCP/IP.UD ...

  9. nodeJS之域名DNS

    前面的话 本文将详细介绍域名解析模块DNS 工作原理 打开浏览器,在上方地址栏输入网址的那一刻,这个回车按了之后,发生了很多事情.首先,计算机只懂0和1,也就是说人类的字母网址计算机是不懂的,它只认识 ...

  10. 实例甜点 Unreal Engine 4迷你教程(6)之三个重要基础操作SpawnActor、TArray的Add和Remove

    本小节的教程需要完成前置教程:建议阅读<实例甜点 Unreal Engine 4迷你教程(5)>,因为5里面提到了本节的工程,不过也可以在不看5的前提下直接阅读本教程. 第一步:Empty ...