The most complete tutorial on building MAVEN private server, uploading and using JAR package in history

Recently, dubbo has been used as a project to make frequent RPC calls with third parties. If the other party changes the interface parameters or adds an interface, all developers in the background need to type the jar package provided by the third party into a pom file and introduce it into the local environment. Very tired!!!

Today, let's share how to build Nexus3Maven private server and upload and use private server jar package

1. Download Private Server package:

1.1. Official website download:

Address: https://fr.sonatype.com/download-oss-sonatype

Fill in the email to download:

1.2. Baidu cloud disk download (version: 3.25):

Download link: https://pan.baidu.com/s/1aOA8BVEmjDurgDfJ8EBpmQ Extraction code: x65c

2. Upload the private server software package to the server:

3. Unzip the private server package:

Decompression command:
tar -zxvf nexus-3.25.1-04-unix.tar.gz

 

After decompression (there will be 2 folders):

4. Private server configuration (can be ignored)

4.1. Change the default port of private server (8081):

//Enter the etc folder
cd  /DATA/nexus3/nexus-3.25.1-04/etc
//Modify configuration
vim nexus-default.properties
//Change port number
application-port=12001

4.2. Modify private server memory allocation:

//Enter the bin directory
cd /DATA/nexus3/nexus-3.25.1-04/bin
//Modify nexus vmoptions 
vim nexus.vmoptions 

5. Start nexus3

(there must be a jdk environment. If jdk is not installed, please move to: https://blog.cnbuilder.cn/archives/linuxinstalljdk )

Start command &Start for background:
./nexus run & It can also be changed to./nexus start &

Successful startup:

6. Access Nexus3 ip + port

7. Login

7.1. Find the login password of admin

Enter the directory he told you, and then look for the password (the admin password is in the file):

7.2. Get the password to log in:

7.3. Change the new password:

This is the successful login system:

7.4. You can create private server users and roles:

8. Create warehouse:

At present, four warehouses (local snapshot warehouse, local formal warehouse, agent warehouse and comprehensive warehouse) are created

For example, the snapshot is the jar package published locally

Local official warehouse: it is the jar package provided to us by the third party, and there is no need to modify the jar package.

Agent warehouse: agent Huawei cloud, Alibaba cloud or mavne general warehouse

Comprehensive warehouse: synthesize the above into a warehouse, which can be used.

8.1. Create a local snapshot warehouse - that is, the warehouse where the test jar package is stored.

1.8 local warehouse selection:

8.1.2. Create a local snapshot warehouse:

8.1.3 successful creation:

8.2. Create a local Release warehouse:

8.2.1. Create release version warehouse:

8.2.2. Successfully created:

8.3. Create an agent warehouse (such as Alibaba cloud, Huawei cloud...)

8.3.1. Create agent warehouse:

8.3.2. Create an agent warehouse:

8.3.3 successful creation:

8.4. Create a combined warehouse:

8.4.1. Select other warehouse addresses of the combined warehouse

8.4.2 successful creation:

9. Publish jar to private server:

9.1. First decompress a new mavne environment locally

9.2. Modify setting file:

9.2.1. Modify local warehouse address:

 <!--custom maven Local warehouse address-->
  <localRepository>D:\hcr\dev\apps\test_nexus3\apache-maven-3.6.3-bin\apache-maven-3.6.3\resp</localRepository>

9.2.2. Configure the new servers and specify the account and password of the release version

<servers>
	<server>  
		<id>kingyifan-releases</id>  
		<username>admin</username>  
		<password>admin123</password>  
	</server>
	<server>  
		<id>kingyifan-snapshots</id>  
		<username>admin</username>  
		<password>admin123</password>  
	</server>   
  </servers>

9.3. Address of release warehouse and snapshot warehouse:

9.4. Addition of code pom file:

  <!--Package upload maven Private service-->
    <distributionManagement>
        <repository>
            <!--id You can take any name, but in setting Properties in file<server>of ID Consistent with here-->
            <id>kingyifan-releases</id>
            <!--Point to warehouse type host(The storage type of the host warehouse is Release Warehouse of-->
            <url>http://192.168.189.129:12001/repository/kingyifan-hosted-release/</url>
        </repository>
        <snapshotRepository>
            <id>kingyifan-snapshots</id>
            <url>http://192.168.189.129:12001/repository/kingyifan-hosted-snapshot/</url>
        </snapshotRepository>
    </distributionManagement>

9.4. Change maven warehouse address of idea:

9.4. Publish to private server.

Command: mvn deploy

Or use idea's packaging tool:

Automatically call the snapshot version.

Q: Why automatically to the snapshot version instead of the release version?

A: Because the version number specified when we create the project is the snapshot version.

9.5. How to upload private servers if there are only jar packages?? Don't worry. Listen to me~

9.5.1. Select the warehouse address to upload (only the release version can be selected)

9.5.2. Upload jar package and name it

9.5.3 successful upload:

9.5.4. View

10. Use the private server environment locally and download the jar package from the private server.

10.1. Configure maven's setting profile:

10.1.1. Add server configuration of comprehensive warehouse

<server>
	  <id>nexus-kingyifan</id>
	  <username>admin</username>
	  <password>admin123</password>
	</server>	

10.1.2. Add the comprehensive warehouse address of private server:

<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-kingyifan</id>
        <name>internal nexus repository</name>
        <!--The mirror uses the address of the configured group-->
        <url>http://192.168.189.129:12001/repository/kingyifan-group/</url>
        <mirrorOf>!internal.repo,*</mirrorOf>
    </mirror>
  </mirrors>

10.1.3 list of configured warehouses:

<profiles>
	<profile>
		<id>jdk-1.8</id>
		<activation>
			<activeByDefault>true</activeByDefault>
			<jdk>1.8</jdk>
		</activation>
		<properties>
			<maven.compiler.source>1.8</maven.compiler.source>
			<maven.compiler.target>1.8</maven.compiler.target>
			<maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
		</properties>
   </profile>
   <profile>
		  <id>nexus-kingyifan</id>
		   <!-- Remote warehouse list -->
		  <repositories>
			<repository>
			  <id>nexus-kingyifan</id>
			  <name>Nexus Central</name>
			 <!-- Virtual URL form,Point to mirrored URL-->
			  <url>http://192.168.189.129:12001/repository/kingyifan-group/</url>
			  <layout>default</layout>
			 <!-- Indicates that it can be downloaded from this warehouse releases Components of version--> 
			  <releases>
				<enabled>true</enabled>
			  </releases>
			 <!-- Indicates that it can be downloaded from this warehouse snapshot Components of version --> 
			  <snapshots>
				<enabled>true</enabled>
			  </snapshots>
			</repository>
		  </repositories>
		   <!-- List of plug-in warehouses -->
		  <pluginRepositories>
			<pluginRepository>
			  <id>nexus-kingyifan</id>
			  <name>Nexus Central</name>
			  <url>http://192.168.189.129:12001/repository/kingyifan-group/</url>
			  <layout>default</layout>
			  <snapshots>
				<enabled>true</enabled>
			  </snapshots>
			  <releases>
				 <enabled>true</enabled>
			  </releases>
			</pluginRepository>
		  </pluginRepositories>
	</profile>
  </profiles>
  <activeProfiles>
     <!--Activation required <profile>Medium ID To take effect--> 
    <activeProfile>nexus-kingyifan</activeProfile>
    <activeProfile>jdk-1.8</activeProfile>
  </activeProfiles>

Let's give you a complete maven setting configuration file:

<?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>
  -->
  
   <!--custom maven Local warehouse address-->
  <localRepository>D:\hcr\dev\apps\test_nexus3\apache-maven-3.6.3-bin\apache-maven-3.6.3\resp</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>  
		<id>kingyifan-releases</id>  
		<username>admin</username>  
		<password>admin123</password>  
	</server>
	<server>  
		<id>kingyifan-snapshots</id>  
		<username>admin</username>  
		<password>admin123</password>  
	</server>
	<server>
	  <id>nexus-kingyifan</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-kingyifan</id>
        <name>internal nexus repository</name>
        <!--The mirror uses the address of the configured group-->
        <url>http://192.168.189.129:12001/repository/kingyifan-group/</url>
        <mirrorOf>!internal.repo,*</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>
		<id>jdk-1.8</id>
		<activation>
			<activeByDefault>true</activeByDefault>
			<jdk>1.8</jdk>
		</activation>
		<properties>
			<maven.compiler.source>1.8</maven.compiler.source>
			<maven.compiler.target>1.8</maven.compiler.target>
			<maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
		</properties>
   </profile>
   <profile>
		  <id>nexus-kingyifan</id>
		   <!-- Remote warehouse list -->
		  <repositories>
			<repository>
			  <id>nexus-kingyifan</id>
			  <name>Nexus Central</name>
			 <!-- Virtual URL form,Point to mirrored URL-->
			  <url>http://192.168.189.129:12001/repository/kingyifan-group/</url>
			  <layout>default</layout>
			 <!-- Indicates that it can be downloaded from this warehouse releases Components of version--> 
			  <releases>
				<enabled>true</enabled>
			  </releases>
			 <!-- Indicates that it can be downloaded from this warehouse snapshot Components of version --> 
			  <snapshots>
				<enabled>true</enabled>
			  </snapshots>
			</repository>
		  </repositories>
		   <!-- List of plug-in warehouses -->
		  <pluginRepositories>
			<pluginRepository>
			  <id>nexus-kingyifan</id>
			  <name>Nexus Central</name>
			  <url>http://192.168.189.129:12001/repository/kingyifan-group/</url>
			  <layout>default</layout>
			  <snapshots>
				<enabled>true</enabled>
			  </snapshots>
			  <releases>
				 <enabled>true</enabled>
			  </releases>
			</pluginRepository>
		  </pluginRepositories>
	</profile>
  </profiles>
  <activeProfiles>
     <!--Activation required <profile>Medium ID To take effect--> 
    <activeProfile>nexus-kingyifan</activeProfile>
    <activeProfile>jdk-1.8</activeProfile>
  </activeProfiles>

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

10.1.4. Knock on the blackboard: the environment of IDEAmaven must be changed to the setting configuration file just modified!!!

10.1.5 introduction of pom package:

I will go to the private server to download the jar package

Let's see that the local maven warehouse also has corresponding jar packages:

11. Private server - Download jar package path:

Local warehouse = = = "private server release version = = =" private server official version = = = "private server agent warehouse = = =" until the end of search.

Finally, centos7 builds private servers, uploads and uses private server jar packages.

Encourage the author to write better technical documents and buy me a bottle of Wahaha.. Your sponsorship determines the speed of my update!

WeChat:

Alipay:

Thank you for supporting me all the way.....

Love me and hold me
QQ:69673804(16 (old)
EMAIL:itw@tom.com
 Friend chain exchange
 If you are interested in exchanging links with this blog, please comment in the comment area according to the following format, and I will add your link as soon as possible.
Website name: ape code Youchuang
 Website address: http://blog.cnbuilder.cn
 Website description: youth is your dream that you don't wake up, and Fenghua is the other shore flower that burns out.
website Logo/head portrait: [Avatar address](https://blog.cnbuilder.cn/upload/2018/7/avatar20180720144536200.jpg)

Welcome to pay attention to ape code Youchuang (contact xiaoyouyou to enter the internal group, and fresh technology will be updated first):

 

Tags: Java

Posted by agent007 on Tue, 24 May 2022 15:23:45 +0300