一、nexus仓库安装

1,http://www.sonatype.org/nexus/    下载sso版本，免费
2,tar -zxvf nexus-2.11.1-01-bundle.tar.gz
3,修改端口号    /conf/nexus.properties文件     application-port属性值设置端口号
4,默认端口8081，http://localhost:8081/nexus 访问，默认账号密码 admin,admin123
5,配置服务: nexus自带了service脚本，位于/bin目录下面的nexus文件，将其复制至/etc/init.d目录下，既可以使用service nexus start/restart/stop命令
    chkconfig --add nexus
    chkconfig --level 345 nexus     设置在345运行级别自动启动服务

6,NEXUS仓库介绍：
    6.1    nexus的仓库类型分为以下四种：group: 仓库组，hosted：宿主，proxy：代理，virtual：虚拟
    6.2    首次登陆nexus后可以看到以下一个仓库组和多个仓库：
            Public Repositories:  仓库组
            3rd party: 无法从公共仓库获得的第三方发布版本的构件仓库
            Apache Snapshots: 用了代理ApacheMaven仓库快照版本的构件仓库
            Central: 用来代理maven中央仓库中发布版本构件的仓库
            Central M1 shadow: 用于提供中央仓库中M1格式的发布版本的构件镜像仓库
            Codehaus Snapshots: 用来代理CodehausMaven 仓库的快照版本构件的仓库
            Releases: 用来部署管理内部的发布版本构件的宿主类型仓库
            Snapshots:用来部署管理内部的快照版本构件的宿主类型仓库
7，基本设置：
    7.1    设置Nexus中的Apache Snapshots、Maven Central、Codehaus Snapshots的下载远程索引：Download Remote Indexes 属性设置为true 默认为false
    7.2    Nexus预定义了“Public Repositories”和“Public Snapshot Repositories”两个仓库组：
        前者默认合并所有预定义的Release仓库，后者默认合并所有预定义的Snapshot仓库。
        点击仓库列表中的“Public Repositories”，然后选择下方的"Configuration" Tab，在配置面板中，将右边“Avaiable Repositories”中的Repository拖拽到左边的“Ordered Group Repository”中

二、linux下maven配置

1,下载 apache-maven-3.2.3-bin.tar.gz
    tar -xvf  apache-maven-3.2.3-bin.tar.gz
2,配置环境变量，编辑/etc/profile文件，添加如下代码
    export MAVEN_HOME=/usr/local/apache-maven-3.0.3
    export PATH=$PATH:$MAVEN_HOME/bin
    配置文件生效source /etc/profile
3,测试maven         mvn-v

三、项目中的maven配置内容  "http://maven.repository.com/为本地私库的域名(自定义)"

1，maven配置文件位于/conf/setting.xml	对于此配置文件的设置，就完成能让本机所有的Maven项目都使用自己的Maven私服

2，修改setting.xml文件

	2.1	设置本地仓库jar保存位置：<localRepository>d:/maven-3.1.0/.m2/repository</localRepository>

	2.2	Nexus 的仓库对于匿名用户是只读权限，为了能够部署构件，还需要在setting.xml 中配置认证信息代码如下：

		<server>

		   <id>nexus-releases</id>

		   <username>admin</username>

		   <password>admin123</password>

		</server>

		<server>

		   <id>>nexus-snapshots</id>

		   <username>admin</username>

		   <password>admin123</password>

		 </server>

	2.3	配置镜像地址：

		<mirrors>

			<mirror>

				<id>nexus-snapshots</id>

				<mirrorOf>public-snapshots</mirrorOf>

				<url>http://maven.repository.com/nexus/content/groups/public-snapshots</url>

			</mirror>

			<mirror>

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

				<id>nexus-releases</id>

				<mirrorOf>*</mirrorOf>

				<url>http://maven.repository.com/nexus/content/groups/public</url>

			</mirror>

		</mirrors>

		这里配置mirrorOf的值为*，代表maven的所有访问请求都会指向到public仓库组。

	2.4	配置仓库信息：

		<profiles>

			<profile>

				<id>public</id>

				<repositories>

					<repository>

						<id>public</id>

						<url>http://maven.repository.com/nexus/content/groups/public</url>

						<releases>

							<enabled>true</enabled>

						</releases>

						<snapshots>

							<enabled>false</enabled>

						</snapshots>

					</repository>

				</repositories>

				<pluginRepositories>

					<pluginRepository>

						<id>public</id>

						<url>http://maven.repository.com/nexus/content/groups/public</url>

						<releases>

							<enabled>true</enabled>

						</releases>

						<snapshots>

							<enabled>false</enabled>

						</snapshots>

					</pluginRepository>

				</pluginRepositories>

			</profile>

			<profile>

				<id>public-snapshots</id>

				<repositories>

					<repository>

						<id>public-snapshots</id>

						<url>http://maven.repository.com/nexus/content/groups/public-snapshots</url>

						<releases>

							<enabled>false</enabled>

						</releases>

						<snapshots>

							<enabled>true</enabled>

						</snapshots>

					</repository>

				</repositories>

				<pluginRepositories>

					<pluginRepository>

						<id>public-snapshots</id>

						<url>http://maven.repository.com/nexus/content/groups/public-snapshots</url>

						<releases>

							<enabled>false</enabled>

						</releases>

						<snapshots>

							<enabled>true</enabled>

						</snapshots>

					</pluginRepository>

				</pluginRepositories>

			</profile>

		</profiles>

	2.4	激活配置

		<activeProfiles>

			<activeProfile>public-snapshots</activeProfile>

			<activeProfile>public</activeProfile>

		</activeProfiles>

3，日常开发生成的快照版本构件可以直接部署到Nexus中策略为Snapshot的宿主仓库中，项目正式发布的构件则应该部署到Nexus中策略为Release的宿主仓库中。

	POM.XML配置如下：

	<project>

		<distributionManagement>

			<repository>

				<id>nexus-releases</id>

				<name>Nexus Releases Repository</name>

				<url>http://maven.repository.com/nexus/content/repositories/releases</url>

			</repository>

			<snapshotRepository>

				<id>nexus-snapshots</id>

				<name>Nexus Snapshots Repository</name>

				<url>http://maven.repository.com/nexus/content/repositories/snapshots</url>

			</snapshotRepository>

		</distributionManagement>

	</project>

	执行mvn clean deploy  下载部署所需的构件

　　

四、附：maven配置文件

<?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>/path/to/local/repo</localRepository>

  -->

  <localRepository>d:/maven-3.1.0/.m2/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>

  -->

  <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>nexus-releases</id>

       <username>admin</username>

       <password>admin123</password>

    </server>

  <server>

       <id>nexus-snapshots</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>nexus-snapshots</id>

          <mirrorOf>public-snapshots</mirrorOf>

          <url>http://maven.repository.com/content/groups/public-snapshots</url>

     </mirror>

     <mirror>

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

          <id>nexus-releases</id>

          <mirrorOf>*</mirrorOf>

          <url>http://maven.repository.com/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.

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

            <repositories>

                <repository>

                    <id>public</id>

                    <url>http://maven.repository.com/nexus/content/groups/public</url>

                    <releases>

                        <enabled>true</enabled>

                    </releases>

                    <snapshots>

                        <enabled>false</enabled>

                    </snapshots>

                </repository>

            </repositories>

            <pluginRepositories>

                <pluginRepository>

                    <id>public</id>

                    <url>http://maven.repository.com/nexus/content/groups/public</url>

                    <releases>

                        <enabled>true</enabled>

                    </releases>

                    <snapshots>

                        <enabled>false</enabled>

                    </snapshots>

                </pluginRepository>

            </pluginRepositories>

        </profile>

     <profile>

            <id>public-snapshots</id>

            <repositories>

                <repository>

                    <id>public-snapshots</id>

                    <url>http://maven.repository.com/nexus/content/groups/public-snapshots</url>

                    <releases>

                        <enabled>false</enabled>

                    </releases>

                    <snapshots>

                        <enabled>true</enabled>

                    </snapshots>

                </repository>

            </repositories>

            <pluginRepositories>

                <pluginRepository>

                    <id>public-snapshots</id>

                    <url>http://maven.repository.com/nexus/content/groups/public-snapshots</url>

                    <releases>

                        <enabled>false</enabled>

                    </releases>

                    <snapshots>

                        <enabled>true</enabled>

                    </snapshots>

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

  <activeProfiles>

    <activeProfile>public-snapshots</activeProfile>

    <activeProfile>public</activeProfile>

  </activeProfiles>

  <!-- activeProfiles

   | List of profiles that are active for all builds.

   |

  <activeProfiles>

    <activeProfile>alwaysActiveProfile</activeProfile>

    <activeProfile>anotherAlwaysActiveProfile</activeProfile>

  </activeProfiles>

  -->

</settings>

　　

　　

maven&nexus_repository 私库搭建与使用的更多相关文章

  1. maevn的nexus私库搭建

    使用nexus搭建maven仓库(本地私服) 前言:我们在使用maven的时候,对于项目所依赖的jar包,maven默认会在中央仓库下载jar包,到本地的磁盘目录(如果没有配置则是用户目录下/.m2/ ...

  2. 第三方jar上传至公司maven仓库(私库)解决办法

    在实际开发过程中,我们经常会遇到需要引用的jar依赖,在我们公司的maven仓库不存在,这个时候我们就需要把jar上传上去,在项目中添加对应依赖就OK了. 步骤1:下载jar 在http://mvnr ...

  3. maven私库nexus2.11.4迁移升级到nexus3.12.0

    nexus简介 nexus是一个强大的maven仓库管理器,它极大的简化了本地内部仓库的维护和外部仓库的访问. nexus是一套开箱即用的系统不需要数据库,它使用文件系统加Lucene来组织数据 .n ...

  4. Docker4-docker私库的搭建及常用方法-docker-registry方式

    一.简单介绍 前面已经介绍,可以使用Docker Hub公共仓库,但是大多数情况企业都需要创建一个本地仓库供自己使用.这里介绍几种搭建私库的方法 私库的好处有几点 1.节约带宽 2.可以自己定制系统 ...

  5. nexus3.14.0版本linux环境安装、启动、搭建私库

    本文介绍的是nexus3.14.0版本在linux环境下安装.启动.搭建私库. nexus3以上的版本太新了,网上很少介绍安装细节的.据了解和2.X版本有所不同了. 1.前提 linux机器上需先安装 ...

  6. maven私库nexus2.3.0-04迁移升级到nexus-3.16.1-02（异机迁移备份）

    环境信息: nexus2.3.0-04安装在32位Windows server 2003系统上 安装位置信息如下: 仓库迁移 Nexus的构件仓库都保存在sonatype-work目录中,nexus2 ...

  7. Maven 如何发布 jar 包到 Nexus 私库

    Nexus2可以通过管理界面来上传jar包到私库中,而最新的Nexus3却找不到了上传界面,只能通过以下方式来发布到私库. 发布第三方jar包 这种情况是maven远程仓库没有,本地有的第三方jar包 ...

  8. Maven如何发布jar包到Nexus私库

    Nexus2可以通过管理界面来上传jar包到私库中,而最新的Nexus3却找不到了上传界面,只能通过以下方式来发布到私库. 发布第三方jar包 这种情况是maven远程仓库没有,本地有的第三方jar包 ...

  9. docker私库harbor的搭建

    1.文件下载 # wget https://storage.googleapis.com/harbor-releases/harbor-online-installer-v1.5.1.tgz 安装官网 ...

随机推荐

  1. 找到了两个联想的OEM　XP镜像文件

    今天在收拾移动硬盘的时候发现了两个XP镜像 还都是联想的,一个有OOBE,另一个无OOBE,全传网盘里了,需要的自取 有个疑问 2020年还有多少家庭电脑和ATM机器还在用XP??? link:htt ...

  2. 【Python爬虫】HTTP基础和urllib库、requests库的使用

    引言: 一个网络爬虫的编写主要可以分为三个部分: 1.获取网页 2.提取信息 3.分析信息 本文主要介绍第一部分,如何用Python内置的库urllib和第三方库requests库来完成网页的获取.阅 ...

  3. 手机U盘制作成系统启动盘后在手机端无法识别

    本人最近用手机U盘做了个系统启动盘,突然发现U盘再次插到手机的时候,手机无法识别出U盘了,于是百度了一下,百度结果大概是跟U盘的格式有关.结果我想起了之前用的DiskGenius可以看到u盘的隐藏盘符 ...

  4. 手机商品分享样式（纯html+css）

    效果图: html: <!DOCTYPE html> <html lang="en"> <head>     <meta charset= ...

  5. 计算机网络之tcp三次握手

    客户端与服务器之间数据的发送和返回的过程当中需要创建一个叫TCP connection的东西:由于TCP不存在连接的概念,只存在请求和响应,请求和响应都是数据包,它们之间都是经过由TCP创建的一个从客 ...

  6. 作为一个Java开发你用过Jib吗

    1. 前言 Jib是Google开发的可以直接构建 Java应用的Docker和OCI镜像的类库,以Maven和Gradle插件形式提供.它最骚操作的是可以在没有Docker守护程序的情况下构建,也就 ...

  7. 【错误】fatal: destination path already exists and is not an empty directory. 错误及解决办法

    今天在使用Git for Windows clone代码时,遇到了题目所示的错误,简单来说就是目标路径‘.’已经存在并且不是一个空目录. 可是在我在文件夹下并没有看到任何文件,显示“该文件夹为空”,然 ...

  8. scrapy框架结构与工作原理

    组件: ENGINE:引擎,框架的核心,其他组件在其控制下协同工作. SCHEDULER:调度器,负责对SPIDER提交的下载请求进行调度 DOWNLOADER:下载器,负责下载页面,发送HTTP请求 ...

  9. 【SpringCloud】Gateway 配置全局过滤器获取请求参数和响应值

    [SpringCloud]Gateway 配置全局过滤器获取请求参数和响应值 实现Ordered接口getOrder()方法,数值越小越靠前执行,记得这一点就OK了. 获取请求参数RequestBod ...

  10. day03组件

    1.text   编写文本信息,等价于span 2.view 等价于div 3.image ============================wxml====================== ...