一、安裝JDK

JDK官網下載：https://www.oracle.com
JDK8下載地址:https://www.oracle.com/java/technologies/javase/javase-jdk8-downloads.html

# 1.建立軟體存放目錄
[root@nex-dev ~]$ mkdir /data/software/
[root@nex-dev ~]$ cd /data/software/

# 2.上傳jdk安裝包
[root@nex-dev /data/software]$ rz
[root@nex-dev /data/software]$ ll
total 206884
-rw-r--r--. 1 root root 185540433 2021-07-12 09:42 jdk-8u131-linux-x64.tar.gz

# 3.解壓安裝包
[root@nex-dev /data/software]$ tar xf jdk-8u131-linux-x64.tar.gz  -C /opt
[root@nex-dev /data/software]$ cd /opt/
[root@jindada ~]$ ll
total 0
drwxr-xr-x. 8   10  143 255 2017-03-15 16:35 jdk1.8.0_131

# 4.做軟連線
[root@jindada ~]$ ln -s jdk1.8.0_131 jdk
[root@jindada ~]$ ll
total 0
lrwxrwxrwx. 1 root root  12 2021-07-12 09:43 jdk -> jdk1.8.0_131
drwxr-xr-x. 8   10  143 255 2017-03-15 16:35 jdk1.8.0_131

# 5.配置環境變數
[root@jindada ~]$ vim /etc/profile.d/java.sh 
export PATH=/opt/jdk/bin:$PATH

# 6.重新整理環境變數
[root@jindada ~]$ source /etc/profile.d/java.sh 

# 7.驗證jdk
[root@jindada ~]$ java -version
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
 

二、安裝Maven

Maven官網下載地址：http://maven.apache.org

# 1.建立軟體存放目錄
[root@jindada ~]$ cd /data/software/

# 2.下載Maven安裝包
[root@jindada /data/software]$ wget https://mirrors.tuna.tsinghua.edu.cn/apache/maven/maven-3/3.8.1/binaries/apache-maven-3.8.1-bin.tar.gz
[root@jindada /data/software]$ ll
總用量 22700
-rw-r--r--. 1 root root  9536838 3月  31 01:41 apache-maven-3.8.1-bin.tar.gz

# 3.解壓安裝包
[root@jindada /data/software]$ tar xf apache-maven-3.8.1-bin.tar.gz  -C /opt/
[root@jindada /data/software]$ cd /opt/
[root@jindada /opt]$ ll
總用量 32
drwxr-xr-x.  6 root root 4096 8月  11 14:38 apache-maven-3.8.1

# 4.做軟連線
[root@jindada /opt]$ ln -s apache-maven-3.8.1/ maven
[root@jindada /opt]$ ll
總用量 32
drwxr-xr-x.  6 root root 4096 8月  11 14:38 apache-maven-3.8.1
lrwxrwxrwx.  1 root root   19 8月  11 14:39 maven -> apache-maven-3.8.1

# 5.配置環境變數
[root@jindada /opt]$ vim /etc/profile.d/maven.sh
export PATH=/opt/maven/bin:$PATH  

# 6.重新整理環境變數
[root@jindada /opt]$ source  /etc/profile.d/maven.sh

# 7.驗證Maven
[root@jindada /opt]$ mvn -version
Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Maven home: /opt/maven
Java version: 1.8.0_131, vendor: Oracle Corporation, runtime: /opt/jdk1.8.0_131
Default locale: zh_CN, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1160.31.1.el7.x86_64", arch: "amd64", family: "unix"
 

三、安裝nexus

nexus下載地址： https://help.sonatype.com/repomanager3/download/

# 1.官網下載安裝包，上傳nexus安裝包
[root@jindada /data/software]$ rz
[root@jindada /data/software]$ ll
總用量 217M
-rw-r--r--. 1 root root 194M 8月  12 16:45 nexus-3.33.0-01-unix.tar.gz

# 2.解壓nexus安裝包
[root@jindada /data/software]$ tar xf nexus-3.33.0-01-unix.tar.gz  -C /opt/

# 3.進入opt目錄下檢視解壓檔案
[root@jindada /data/software]$ cd /opt/

[root@jindada /opt]$ ll
總用量 40
drwxr-xr-x. 10 root root 4096 8月  12 16:50 nexus-3.33.0-01

# 4.建立軟連線
[root@jindada /opt]$ ln -s nexus-3.33.0-01 nexus
[root@jindada /opt]$ ll
總用量 40
lrwxrwxrwx.  1 root root   15 8月  12 16:51 nexus -> nexus-3.33.0-01
drwxr-xr-x. 10 root root 4096 8月  12 16:50 nexus-3.33.0-01

# 5.配置環境變數
[root@jindada /opt]$ vim /etc/profile.d/nexus.sh
export PATH=/opt/nexus/bin:$PATH   

# 6.重新整理環境變數
[root@jindada /opt]$ source  /etc/profile.d/nexus.sh

# 7.nexus預設是不能用root使用者啟動的，修改啟動使用者
[root@jindada /opt/nexus]$ cd /opt/nexus/bin/
[root@jindada /opt/nexus/bin]$ vim nexus.rc 
run_as_user="root"
 
# 8.修改jdka安裝目錄
[root@jindada /opt/nexus]$ cd /opt/nexus/bin/
[root@jindada /opt/nexus/bin]$ vim nexus
INSTALL4J_JAVA_HOME_OVERRIDE=/opt/jdk 

# 9.修改nexus埠
[root@jindada /opt/nexus/bin]$ cd /opt/nexus/etc/
[root@jindada /opt/nexus/etc]$ vim nexus-default.properties 
application-port=524

# 10.啟動nexus
[root@jindada /opt/nexus]$ cd /opt/nexus/bin/
[root@jindada /opt/nexus]$ ./nexus start
 

四、配置Nexus

1.瀏覽器Nexus

訪問：http://ip:port/nexus，這裡為：http://192.168.1.18:524/nexus

2.登入Nexus

# 1.使用預設管理員身份登入，帳號：admin，密碼通過命令：cat /data1/nexus-data/admin.password 檢視相關密碼

# 2.輸入正確的使用者名稱和密碼，登入成功如下:

3.配置相關引導

# 1.進入引導介面，點選下一步，重置初始密碼:

# 2.選擇禁止匿名訪問，點選下一步:

# 3.點選結束，結束設定引導:

五、管理Nexus

# 1.進入管理介面

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去除）

六、增加新的代理源

# 1.進入代理配置介面，點選新建映象代理

# 2.選擇新增maven2的代理

# 3.新增代理（Cache統一設定為：288000)

Name 填寫 aliyun, URL輸入：http://maven.aliyun.com/nexus/content/groups/public/，其他值預設：

# 4.增加常用代理
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/

# 5.選擇Configuration > Repository, 雙擊 maven-public, 在Group區域將常用代理移到右側Members, 上移到maven-central的上面的maven庫放到最底下，點選save。

七、設定私用倉庫可重複釋出

Nexus安裝後自帶maven-releases，maven-snapshots兩個倉庫，用於將生成的jar包釋出在這兩個倉庫中，在實際開發中需要將maven-releases設定為可以重複釋出

八、Maven配置使用Nexus

# 1.進入本地的maven安裝目錄
[root@staging maven]# cd /opt/maven/conf/
[root@staging conf]# ll
total 28
drwxr-xr-x 2 root root    37 Nov  7  2019 logging
-rw-r--r-- 1 root root 10796 Jun 24 18:20 settings.xml
-rw-r--r-- 1 root root 10741 Jun 24 18:19 settings.xml.bak
-rw-r--r-- 1 root root  3747 Nov  7  2019 toolchains.xml

# 2.備份配置檔案
[root@staging conf]# cp settings.xml settings.xml.bak02

# 3.配置maven配置檔案
[root@staging conf]# vim 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>/data/software/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>releases</id>
      <username>admin</username>
      <password>Jinhuino1</password>
    </server>
    
    <server>
      <id>snapshots</id>
      <username>admin</username>
      <password>Jinhuino1</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>releases</id>
      <mirrorOf>*</mirrorOf>
      <name>HolliPark Repository Mirror</name>
      <url>http://localhost:524/nexus/repository/maven-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>
      <id>HolliPark</id>
      <repositories>
        <repository>
          <id>nexus</id>
          <name>Public Repositories</name>
          <url>http://localhost:524/nexus/repository/maven-public/</url>
          <releases>
            <enabled>true</enabled>
          </releases>
        </repository>
      
        <repository>
          <id>central</id>
          <name>Central Repositories</name>
          <url>http://localhost:524/nexus/repository/maven-central/</url>
          <releases>
            <enabled>true</enabled>
          </releases>
          <snapshots>
            <enabled>false</enabled>
          </snapshots>
        </repository>
        
        <repository>
          <id>release</id>
          <name>Release Repositories</name>
          <url>http://localhost:524/nexus/repository/maven-releases/</url>
          <releases>
            <enabled>true</enabled>
          </releases>
          <snapshots>
            <enabled>false</enabled>
          </snapshots>
        </repository>
        
        <repository>
          <id>snapshots</id>
          <name>Snapshot Repositories</name>
          <url>http://localhost:524/nexus/repository/maven-snapshots/</url>
          <releases>
            <enabled>true</enabled>
          </releases>
          <snapshots>
            <enabled>true</enabled>
          </snapshots>
        </repository>
      </repositories>
      
      <pluginRepositories>
        <pluginRepository>
          <id>plugins</id>
          <name>Plugin Repositories</name>
          <url>http://localhost:524/nexus/repository/maven-public/</url>
        </pluginRepository>
      </pluginRepositories>
    </profile>
    <!-- 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>
    -->
  </profiles>

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

九、建立私有公庫

1.建立普通的maven專案

2.修改專案的pom.xml

在pom檔案中加入distributionManagement節點，注意：pom.xml中repository裡的id需要和.m2中setting.xml裡的server id名稱保持一致
<distributionManagement>
    <repository>
        <id>releases</id>
        <name>Nexus Release Repository</name>
        <url>http://192.168.1.18:524/nexus/repository/maven-releases/</url>
    </repository>
    <snapshotRepository>
        <id>snapshots</id>
        <name>Nexus Snapshot Repository</name>
        <url>http://192.168.1.18:524/nexus/repository/maven-snapshots/</url>
    </snapshotRepository>
</distributionManagement>

3.釋出私有公庫

# 1.執行部署命令即可釋出:
mvn deploy
# 2.登入Nexus，檢視對應的倉庫已經有相關的依賴包了

ps:       
 若專案版本號末尾帶有 -SNAPSHOT，則會發布到snapshots快照版本倉庫
 若專案版本號末尾帶有 -RELEASES 或什麼都不帶，則會發布到releases正式版本倉庫