私有Maven仓库安装和使用

安装

这里选择安装的是windows平台，linux安装类似，下载可能要梯子

 

官网下载页

https://help.sonatype.com/repomanager2/download

下载链接

https://download.sonatype.com/nexus/oss/nexus-latest-bundle.zip

  

这里下载2.X的最新版本 捆绑包，内置jetty容器，可作为独立服务运行，jdk 要求1.8

（个人觉得 2.x版本更好用）

下载解压后，可以看到两个目录

 

安装： （这里以本机安装作为示例）

管理员身份进入解压后的bin目录下，执行 nexus 命令可以看到 提示命令

 

 

执行 nexus install ,等待安装完成

执行 nexus start 启动 nexus

访问  http://127.0.0.1:8081/nexus ,看到该页面即表示正常启动

 

 

基础使用

登录

右上角点击登录 admin/admin123 （初始默认账号密码）

创建 my-maven-release 和 my-maven-snapshot

（名字自定义）,作为稳定版和快照版私有仓库

 

两个仓库type都是 hosted 类型

 

 

my-maven-release

 

创建 my-maven-snapshot ,把 Repository Policy 改为Snapshot

 

至此，仓库已经创建完毕

nexus中所有仓库的实际位置都存储在

nexus-2.14.19-01-bundle\sonatype-work\nexus\storage 目录下

 

部署项目到私有库

打开一个maven项目

在pom.xml添加以下内容

<distributionManagement>

    <repository>

        <id>my-maven-releases</id>

        <url>http://127.0.0.1:8081/nexus/content/repositories/my-maven-releases</url>

    </repository>

    <snapshotRepository>

        <id>my-maven-snapshot</id>

        <url>http://127.0.0.1:8081/nexus/content/repositories/my-maven-snapshot</url>

    </snapshotRepository>

</distributionManagement>

 

内容来源于刚才创建的仓库

 

maven的setting.xml中配置 server,因为访问仓库需要账号密码

<server>  

    <id>my-maven-releases</id>  

    <username>admin</username>  

    <password>admin123</password>  

</server>  

<server>  

    <id>my-maven-snapshot</id>  

    <username>admin</username>  

    <password>admin123</password>  

</server>

　　

maven项目下执行 mvn deploy

 

或者使用IDE 的maven插件执行clean deploy

deploy成功之后可以看到nexus远程仓库有了相关的jar包信息，本地maven仓库 org.example 文件夹下也会出现相关jar包

 

直接上传jar包到私有maven库

配置完成后，选择文件，点击 Add Artifact , 最后点击上传

 

更改nexus 仓库平台 账号密码

或者点击 User ,选中右键

 

Nexus OSS 修改 端口号

打开 conf 文件夹下的 nexus.properties 文件

 

 

从私有仓库拉取依赖

配置公共库

将右边配置的仓库移动到左边并保存 ，就可以在公共库下看到之前deploy的项目的相关信息

 

这边也可以添加aliyun代理仓库并把它移动到公共库下，

这样个人的setting.xml 阿里云 镜像配置都可以省略了

但是如果不是公司网络，就会下不了依赖，个人可去可不去

setting.xml配置

servers部分  （这边如果不需要上传项目到私有仓库，可以不需要配置）

	</servers>		
                <server>   
			<id>my-maven-releases</id>   
			<username>admin</username>   
			<password>admin123</password>   
		</server>   
		<server>   
			<id>my-maven-snapshot</id>   
			<username>admin</username>   
			<password>admin123</password>   
		</server>
	</servers>

Mirrors部分 用aliyun的maven仓库，可以不用变

私有仓库配置部分

<profiles>
    <profile>
		<id>my-maven</id>
		<repositories>
			<repository>
				<id>public</id>
				<name>public Repository</name>
				<url>http://127.0.0.1:8081/nexus/content/groups/public/</url>
				<releases>
					<enabled>true</enabled>
				</releases>
				<snapshots>
					<enabled>true</enabled>
				</snapshots>
			</repository>
		</repositories>
		<pluginRepositories>
			<pluginRepository>
				<id>public</id>
				<name>Public Repositories</name>
				<url>http://127.0.0.1:8081/nexus/content/groups/public/</url>
			</pluginRepository>
		</pluginRepositories>
	</profile>
	
  </profiles>　

记得激活配置

	<activeProfiles>
		<activeProfile>my-maven</activeProfile>
	</activeProfiles>

完整的配置如下：

<?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:\Program Files\Apache Software Foundation\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>
		-->

		<!-- 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>my-maven-releases</id>   
			<username>admin</username>   
			<password>admin123</password>   
		</server>   
		<server>   
			<id>my-maven-snapshot</id>   
			<username>admin</username>   
			<password>admin123</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>
      <id>mirrorId</id>
      <mirrorOf>repositoryId</mirrorOf>
      <name>Human Readable Name for this Mirror.</name>
      <url>http://my.repository.com/repo/path</url>
    </mirror>
     -->
	

	
<!-- 	<mirror>
		<id>mynexus</id>
		<name>mynexus maven</name>
		<url>http://localhost:8081/nexus/content/groups/public/</url>
		<mirrorOf>*</mirrorOf>        
	</mirror> -->
	
	<mirror>
		<id>alimaven</id>
		<name>aliyun maven</name>
		<url>http://maven.aliyun.com/nexus/content/groups/public/</url>
		<mirrorOf>central</mirrorOf>        
	</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>

      <properties>
        <tomcatPath>/path/to/tomcat/instance</tomcatPath>
      </properties>
    </profile>
    -->
	<profile>
		<id>my-maven</id>
		<repositories>
			<repository>
				<id>public</id>
				<name>public Repository</name>
				<url>http://127.0.0.1:8081/nexus/content/groups/public/</url>
				<releases>
					<enabled>true</enabled>
				</releases>
				<snapshots>
					<enabled>true</enabled>
				</snapshots>
			</repository>
		</repositories>
		<pluginRepositories>
			<pluginRepository>
				<id>public</id>
				<name>Public Repositories</name>
				<url>http://127.0.0.1:8081/nexus/content/groups/public/</url>
			</pluginRepository>
		</pluginRepositories>
	</profile>
	
  </profiles>

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