一、使用Docker安装Nexus
Docker search nexus
docker pull docker.io/sonatype/nexus3
mkdir -p /usr/local/nexus3/nexus-data
chown -R 200 /usr/local/nexus3/nexus-data
docker run -tid -p 8081:8081 --name nexus -e NEXUS_CONTEXT=nexus -v /usr/local/nexus3/nexus-data:/nexus-data docker.io/sonatype/nexus3
现在已经安装完成了 nexus。
二、登录Nexus进行配置
1、登录nexus
访问：http://ip:8081/nexus使用默认管理员身份登录，帐号：admin，密码：admin123
2、进入管理界面
Browse可以查看当前有多少仓库，搭建好的Nexus，默认会带有一些maven仓库，一般使用这些仓库就足够了。
默认仓库说明
maven-central：maven中央库，默认从https://repo1.maven.org/maven2/拉取jar
maven-releases：私库发行版jar，初次安装请将Deployment policy设置为Allow redeploy
maven-snapshots：私库快照（调试版本）jar
maven-public：仓库分组，把上面三个仓库组合在一起对外提供服务，在本地maven基础配置settings.xml或项目pom.xml中使用
仓库类型
Group：这是一个仓库聚合的概念，用户仓库地址选择Group的地址，即可访问Group中配置的，用于方便开发人员自己设定的仓库。maven-public就是一个Group类型的仓库，内部设置了多个仓库，访问顺序取决于配置顺序，3.x默认Releases，Snapshots， Central，当然你也可以自己设置。
Hosted：私有仓库，内部项目的发布仓库，专门用来存储我们自己生成的jar文件
3rd party：未发布到公网的第三方jar (3.x去除了)
Snapshots：本地项目的快照仓库
Releases： 本地项目发布的正式版本
Proxy：代理类型，从远程中央仓库中寻找数据的仓库（可以点击对应的仓库的Configuration页签下Remote Storage属性的值即被代理的远程仓库的路径），如可配置阿里云maven仓库
Central：中央仓库
Apache Snapshots：Apache专用快照仓库(3.x去除了)
3、增加新的代理源
第一步 按照步骤添加新的代理源
第二步选择添加maven2的代理
第三步添加代理（Cache统一设置为200天 288000）
第四步逐个增加常用代理
1. aliyun
http:
//maven.aliyun.com/nexus/content/groups/public
2. apache_snapshot
https:
//repository.apache.org/content/repositories/snapshots/
3. apache_release
https://repository.apache.org/content/repositories/releases/
4. atlassian
https://maven.atlassian.com/content/repositories/atlassian-public/
5. central.maven.org
http://central.maven.org/maven2/
6. datanucleus
http://www.datanucleus.org/downloads/maven2
7. maven-central （安装后自带，仅需设置Cache有效期即可）
https://repo1.maven.org/maven2/
8. nexus.axiomalaska.com
http://nexus.axiomalaska.com/nexus/content/repositories/public
9. oss.sonatype.org
https://oss.sonatype.org/content/repositories/snapshots
10.pentaho
https://public.nexus.pentaho.org/content/groups/omni/
第五步 设置maven-public 将这些代理加入Group，最好将默认的maven库放到最底下
第六步 设置私用仓库可重复发布
Nexus安装后自带maven-releases，maven-snapshots两个仓库，用于将生成的jar包发布在这两个仓库中，在实际开发中需要将maven-releases设置为可以重复发布
4、Maven配置使用Nexus
修改.m2下面的setting.xml文件配置
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with
thisworkforadditional information
regarding copyright ownership. The ASF licenses
thisfile
to you under the Apache License, Version
2.0(the
"License"); you may not usethisfile exceptincompliance
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.
-->
| Thisisthe configuration fileforMaven. It can be specified at two levels:
|
|1. User Level. This settings.xml file provides configurationfora single user,
| andisnormally providedin${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 configurationforall 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 sectionsinthissample file are intended to give you a running start at
| getting the mostoutof your Maven installation. Where appropriate, thedefault
| values (values used when the settingisnot specified) are provided.
|
|-->
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">
|The path to the local repository maven will use to store artifacts.
|
| Default: ${user.home}/.m2/repository
-->
${user.home}/.m2/repository
| This will determine whether maven prompts you when it needs input. Ifsettofalse,
| maven will use a sensibledefaultvalue, perhaps based on some other setting,for
| the parameterinquestion.
|
| Default:true
true
-->
|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
false
-->
| Thisisa 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"ifthese are not already containedinthe list.
|-->
| Specifies a further group identifier to useforplugin lookup.
com.your.plugins
-->
| Thisisa list of proxies which can be used onthismachine to connect to the network.
| Unless otherwise specified (by system property or command-lineswitch), the first proxy
| specificationinthislist markedasactive will be used.
|-->
| Specificationforone proxy, to be usedinconnecting to the network.
|
optional
true
http
proxyuser
proxypass
proxy.host.net
80
local.net|some.host.com
-->
| Thisisa 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.
|-->
|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.
|
-->
releases
admin
admin23
snapshots
admin
admin123
siteServer
/path/to/private/key
optional; leave emptyifnot used.
-->
| Thisisa list of mirrors to be usedindownloading artifactsfromremote repositories.
|
| It works likethis: a POM may declare a repository to useinresolving certain artifacts.
| However,thisrepository 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 referenceforthat
| repository, to be usedasan alternate download site. The mirror site will be the preferred
| serverforthat repository.
|-->
|Specifies a repository mirror site to use instead of a given repository. The repository that
|thismirror serves has an ID that matches the mirrorOf element ofthismirror. IDs are used
|forinheritance and direct lookup purposes, and must be unique across thesetof mirrors.
|
-->
HolliParkMirror
*
HolliPark Repository Mirror.
http://localhost:8082/nexus/repository/maven-public/
| Thisisa list of profiles which can be activatedina variety of ways, and which can modify
| the build process. Profiles providedinthe settings.xml are intended to provide local machine-
| specific paths and repository locations which allow the build to workinthe local environment.
|
| For example,ifyou have an integration testing plugin - like cactus - that needs to knowwhere
| your Tomcat instanceisinstalled, you can provide a variable here such that the variableis
|dereferenced during the build process to configure the cactus plugin.
|
| As noted above, profiles can be activatedina variety of ways. One way -the activeProfiles
| section ofthisdocument (settings.xml) -will be discussed later. Another way essentially
| relies on the detection of a system property, either matching a particular valueforthe property,
| or merely testing its existence. Profiles can also be activated by JDK version prefix,wherea
| value of'1.4'might activate a profile when the buildisexecuted on a JDK version of'1.4.2_07'.
| Finally, the list of active profiles can be specified directlyfromthe command line.
|
| NOTE: For profiles definedinthe settings.xml, you are restricted to specifying only artifact
| repositories, plugin repositories, and free-form properties to be usedasconfiguration
| variablesforpluginsinthe POM.
|
|-->
HolliPark
nexus
Public Repositories
http://localhost:8082/nexus/repository/maven-public/
true
central
Central Repositories
http://localhost:8082/nexus/repository/maven-central/
true
false
release
Release Repositories
http://localhost:8082/nexus/repository/maven-releases/
true
false
snapshots
Snapshot Repositories
http://localhost:8082/nexus/repository/maven-snapshots/
true
true
plugins
Plugin Repositories
http://localhost:8082/nexus/repository/maven-public/
| Specifies asetof introductions to the build process, to be activatedusingone or more of the
| mechanisms described above. For inheritance purposes, and to activate profiles via
| or the command line, profiles have to have an ID thatisunique.
|
| An encouraged best practiceforprofile identificationisto use a consistent naming convention
|forprofiles, suchas'env-dev','env-test','env-production','user-jdcasey','user-brett', etc.
| This will make it more intuitive to understand what thesetof introduced profilesisattempting
| 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.
jdk-1.4
1.4
jdk14
RepositoryforJDK1.4builds
http://www.myhost.com/maven/jdk14
default
always
-->
| Hereisanother profile, activated by the system property'target-env'with a value of'dev',
| which provides a specific path to the Tomcat instance. To usethis, your plugin configuration
|might hypothetically look like:
|
|...
|
| org.myco.myplugins
| myplugin
|
|
| ${tomcatPath}
|
|
|...
|
| NOTE: If you just wanted to injectthisconfiguration whenever someoneset'target-env'to
| anything, you could just leave off the inside the activation-property.
|
env-dev
target-env
dev
/path/to/tomcat/instance
-->
| List of profiles that are activeforall builds.
|
alwaysActiveProfile
anotherAlwaysActiveProfile
-->
HolliPark
三、创建私有公库
1、创建普通的maven项目
2、修改项目的pom.xml
在pom文件中加入distributionManagement节点，注意：pom.xml中repository里的id需要和.m2中setting.xml里的server id名称保持一致
releases
Nexus Release Repository
http://localhost:8082/nexus/repository/maven-releases/
snapshots
Nexus Snapshot Repository
http://localhost:8082/nexus/repository/maven-snapshots/
3、发布私有公库
执行部署命令即可发布。
mvn deploy
登录Nexus，查看对应的仓库已经有相关的依赖包了
注意以下几点：
若项目版本号末尾带有 -SNAPSHOT，则会发布到snapshots快照版本仓库
若项目版本号末尾带有 -RELEASES 或什么都不带，则会发布到releases正式版本仓库