Shulou(Shulou.com)06/03 Report--

Blog outline:

First, deploy Maven

II. Deploy Nexus private server

3. Maven configures nexus private server to set up Nexus private server at cost in remote warehouse.

Upload the third party maven package to the nexus private server

Preface

Maven is the next open source and free project of the apache Software Foundation. It is a cross-platform project management tool. Maven uses a concept called Project Object Model (POM) to manage the project. All the project configuration information is defined in a file called POM.xml. It mainly serves the project construction based on the Java platform, and relies on management and project information management. You can automatically solve the dependent environment of the code in the project during the deployment of the code. You need to download the dependent environment from the maven image warehouse, which is usually slow. Nexus (private server) will be built in the company, and the dependent environment in the construction project will be saved to the nexus server to improve access speed.

The POM project object model, which is the basic unit of work of the Maven project, is an XML file that contains basic information about the project, describing how the project is built, declaring project dependencies, and so on.

When performing a task or target, Maven looks for POM in the current directory. Read the POM, get the required configuration information, and then execute the target.

The following configurations can be specified in POM: project dependencies, plug-ins, execution goals, project build profile, project version, project development list, and related mailing list information.

Functions of Maven:

The JAVA project of maven model has specification and directory planning for source code, unit test code, resources, jar packages, etc., solves the problems of dependency, version inconsistency and version conflict between projects, and a reasonable jar management mechanism.

Maven usage scenarios (from the perspective of operation and maintenance personnel):

The jar package in the original project must be manually copied and pasted to the WEB-INF/lib project, and with the help of maven, the jar package can only be saved in the warehouse, and the project that needs to be used only needs to refer to this file, and there is no need to copy it repeatedly into the project; the jar package needed in the original project is downloaded in advance, and maven will automatically download the required jar package in the networked state. First of all, find it in the local warehouse and download it online if you can't find it; in the original project, other jar packages that a jar package depends on must be imported manually, and maven will automatically import the dependent jar packages; the original project a project is a project, and with the help of maven, a project can be split into multiple projects.

The project construction process includes: [clean up project] → [compile project] → [test project] → [generate test report] → [packaging project] → [deployment project]. These six steps are the complete construction process of a project.

Maven warehouse

In the technical terms of Maven, a warehouse refers to a location, and the Maven repository is the third-party library that the project depends on, which is called the warehouse. In Maven, the output of any dependency, plug-in, or project build can be called a component.

The Maven repository helps us manage artifacts (mainly Jar), which is where all the JAR files (WAR, ZIP, POM, etc.) are placed.

There are three types of Maven repositories: local, central, and remote.

Local warehouse

Maven's local repository is not created after Maven is installed, it is created the first time the maven command is executed.

When running Maven, any artifacts required by Maven are obtained directly from the local repository. If the local warehouse does not, it will first try to download the artifacts from the remote warehouse to the local warehouse, and then use the artifacts from the local warehouse.

By default, regardless of Linux or Windows, each user has a repository directory with a path name of .m2 / respository/ under his or her own user directory.

Central warehouse

The Maven Central Warehouse is a repository provided by the Maven community that contains a large number of commonly used libraries.

Maven has built-in remote public repositories: http://repo1.maven.org/maven2.

The central repository contains most of the popular open source Java artifacts, as well as source code, author information, SCM, information, license information, and so on. In general, simple Java projects rely on artifacts that can be downloaded here.

The core concept of a central warehouse:

This repository is managed by the Maven community; it does not need to be configured to use; it needs to be accessed through the network. Remote warehouse (third-party warehouse)

The third-party warehouse is also known as the internal central warehouse, also known as private service.

Private service: it is generally set up by the company itself and is only shared within the company. It can be used either as an internal component for collaboration and archiving, or as a public class library mirror cache, reducing the frequency of external access and downloads (using private servers to reduce access to the central repository).

To learn more, you can move on to this document: Maven tutorial

First, deploy Maven

You need to rely on the jdk1.8 version to install Maven.

Note: all the source packages used in this blog can be downloaded from the link to the network disk provided by me. The following nexus source code package is always requested to time out on the official website and cannot be downloaded, which wastes a lot of my time.

1 、 Configure jdk environment [root@maven ~] # rpm-qa | grep jdk # to view the installed jdk package java-1.8.0-openjdk-headless-1.8.0.161-2.b14.el7.x86_64copy-jdk-configs-3.3-2.el7.noarchjava-1.8.0-openjdk-1.8.0.161-2.b14.el7.x86_64java-1.7.0-openjdk-headless-1.7.0.171-2. 6.13.2.el7.x86_64java-1.7.0-openjdk-1.7.0.171-2.6.13.2.el7.x86_64# uninstalls the following two packages [root@maven ~] # rpm-e java-1.8.0-openjdk-headless-1.8.0.161-2.b14.el7.x86_64-- nodeps [root@maven ~] # rpm-e java-1.7.0-openjdk-headless-1.7.0. 171-2.6.13.2.el7.x86_64-- nodeps# deploy the jdk package I provided [root@maven ~] # tar zxf jdk-8u211-linux-x64.tar.gz-C / usr/local/ [root@maven ~] # vim / etc/profile # write the following lines of export JAVA_HOME=/usr/local/jdk1.8.0_211export JRE_HOME=/usr/local/jdk1.8.0_211/jreexport CLASSPATH=$JAVA_HOME/lib at the end of the file / tools.jar:$JAVA_HOME/lib/dt.jarexport PATH=$JAVA_HOME/bin:$JRE_HOME/bin:$ path [root @ maven ~] #. / etc/profile # Refresh environment variable [root@maven ~] # java-version # confirm that the following JAVA version information can be viewed: java version "1.8.0x211" Java (TM) SE Runtime Environment (build 1.8.0_211-b12) Java HotSpot (TM) 64-Bit Server VM (build 25.211-b12) Mixed mode) 2. Deploy Maven# to unpack [root@maven] # tar zxf apache-maven-3.6.1-bin.tar.gz-C / usr/src [root@maven ~] # mv / usr/src/apache-maven-3.6.1 / usr/local/maven# configuration environment variable [root@maven] # vim / etc/profile # write the following lines of export MAVEN_HOME=/usr/local/mavenexport PATH=$PATH:$MAVEN_HOME/ at the end of the file [root @ maven] #. / etc/profile [root@maven ~] # mvn-v # execute the command, as long as the following appears, the deployment is successful (because this is a binary deployment) Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555 2019-04-05T03:00:29+08:00) Maven home: / usr/local/mavenJava version: 1.8.0211,vendor: Oracle Corporation, runtime: / usr/local/jdk1.8.0_211/jreDefault locale: zh_CN, platform encoding: UTF-8OS name: "linux", version: "3.10.0-862.el7.x86_64", arch: "amd64" Family: "unix" 1) build the project for testing [root@maven ~] # mkdir / tmp/testdir [root@maven ~] # cd / tmp/testdir/# execute the following command to test [root@maven testdir] # mvn archetype:generate-DgroupId=com.ljz.maven.quickstart-DartifactIdk=testapp-DarchetypeArtifactId=maven-archetype-quickstartDefine value for property 'artifactId': testapp # enter the project name specified when executing the command Press enter directly to keep the default. # omit part of the content [INFO] BUILD SUCCESS # when this prompt appears Indicates that [INFO]-[INFO] Total time: 05:33 min [INFO] Finished at: 2019-11-19T21:29:08+08:00# to create a maven project (Java type) Enter to confirm if there is an interaction, and you can add-DinteractiveMode=false to cancel the interaction process # the above command is explained as follows: # archetype:generate: create a simple java project # archetype, or prototype, is a Maven plug-in, specifically a project template whose task is to create a project structure based on the template. # create a simple java application using the quickstart prototype plug-in #-DgroupId: organization name, reverse of the company URL (reverse domain name) + project name; #-DartifactIdk: project name or module name; #-DarchetypeArtifactId: specify ArchetypeId,maven-archetype-quickstart to create a simple Java application; #-DinteractiveMode: whether to use interactive mode.

Test interpretation of generated files

[root@maven testdir] # ls # after the above command is executed successfully, a directory named by the project name testapp [root@maven testdir] # cd testapp/ # will be generated under the current directory. Enter the generated directory [root@maven testapp] # ls # to view the generated files under the directory pom.xml src [root@maven testapp] # cat pom.xml # pom file parameter interpretation project: root This is the constraint information to add some root elements to Project: modelversion: specify the version number of the current maven model grouopId: should be the name of the company or organization. Generally speaking, groupID consists of three parts, each of which is divided by "." Separation, the first part is the purpose of the project, such as com for business, org for non-commercial for-profit organizations, the second part is the company name, such as tentxun/baidu/alibaba, and the third part is your project name artifactId: it can be thought of as the project name built by maven, for example, your project has subprojects. You can use "project name-subproject naming method packaging: specify the generated format (jar/war/rar/pom/ear) version: version number, SNAPSHOT means snapshot, indicating that the project is still under development and is an unstable version of name: the name of the project, the documentation generated by Maven uses url: the url,Maven of the project home page produces documents with dependencies tags: specify that the development build (jar package) JUnit is a unit test framework for the Java language.

After the project is successfully built, the local repository will also be generated under the current user's host directory.

# View the local warehouse directory structure [root@maven testapp] # ls ~ / .m2/repository/antlr commons-codec commons-io jdom orgasm commons-collections commons-lang net [root@maven testapp] # ls ~ / .m2/repository/antlr/antlr/2.7.7/antlr-2.7.7.pom _ remote.repositoriesantlr-2.7.7.pom.sha12) Maven configuration file

The configuration file name for Maven is: setting.xml. It is stored in two places:

/ usr/local/maven/conf/settings.xml # installation directory ~ / .m2/settings.xml # user's home directory

Among them, the installation directory configuration is the global configuration, and the user directory configuration is called user configuration. If both exist, their content will be merged, and user-wide settings.xml will take precedence.

There is no configuration file in the default user directory, so you can copy maven the settings.xml in the installation directory to the user directory.

The common configuration modifications for settings.xml files are as follows:

1. Modify the storage path of the local warehouse. The default value is ~ / .m2/repository can be changed to the desired directory in localrepository in settings.xml.

2. If the build server cannot be connected to the remote warehouse due to network failure or security problems, you need to set the offline attribute to true in offline mode. Default is false.

3. Modify the central warehouse server, modify the notes in the configuration file, add or modify the image address.

4. Set the proxy address, modify the proxy tag in the configuration file, define the proxy server, and realize the proxy of maven.

As the central warehouse server is foreign, if it is used in China, the download is relatively slow, so it is recommended for domestic users to use the Aliyun warehouse address.

3) configure to use Aliyun warehouse address # edit the main configuration file [root@maven .m2] # cd / usr/local/maven/conf/ [root@maven conf] # vim settings.xml. # omit part of the content http://my.repository.com/repo/path-> # navigate to the line (158line) Write the following content aliyun central aliyun maven https://maven.aliyun.com/nexus/content/groups/public/ # written on this tag # mirror is the mirror, which mainly provides a convenient way to switch remote warehouse addresses. # central is the id of the warehouse to be replaced. Maven common command [root@maven testapp] # pwd # confirm that the current directory is compiled under / tmp/testdir/testapp [root@maven testapp] # mvn compile # (in the process of compilation, you can see that Aliyun's warehouse is used) [INFO] BUILD SUCCESS # as long as you see the line in the last few lines of the output message All commands are the same after successful execution. As long as the last few lines have the above information, you will see that a new directory targetpom.xml src target# target will be generated under the directory [root@maven testapp] # ls #: a packaged output directory, such as packaged jar or war files # target/classes: compile output directory [root@maven testapp] # mvn test # test command [root@maven testapp] # ls target/test-classes/com# target/test-classes: test compilation output directory [root@maven testapp] # mvn clean # cleanup command (that is, delete the compilation and test generated directories) [root@maven testapp] # ls # target directory is no longer in pom.xml src [root@maven testapp] # mvn package # package The command [root@maven testapp] # ls target/ # generates a jar package classes surefire-reportsmaven-archiver testapp-1.0-SNAPSHOT.jarmaven-status test-classes [root@maven testapp] # mvn install # installation command (used to upload the compressed file jar package or war package to the local warehouse) [root@maven testapp] # ls ~ / .m2/repository/com/ljz/maven/quickstart/testapp/1.0-SNAPSHOT/ # View the uploaded package maven-metadata-local.xml testapp-1.0-SNAPSHOT.jar_remote.repositories testapp-1.0-SNAPSHOT.pom# directly use the maven install command to upload the project to the local warehouse # then all the previous steps will be performed automatically, such as compiling and packaging the source code, etc. [root@maven testapp] # mvn deploy # release (upload the package to the private server, which I do not have here, so it will fail) 5) the life cycle of the mvn command

Maven is based on the central concept of the build lifecycle, which means that the process of building and distributing a specific project is clearly defined as follows:

6) build a web project and type out the war package And deploy to Tomcat [root @ maven testdir] # mvn archetype:generate-DgroupId=cn.test.testweb-DartifactId=testweb-DarchetypeArtifactId=maven-archetype-webapp-DinteractiveMode=false# to build the web project # the generated directory structure is as follows: [root@maven testdir] # ls testweb/pom.xml src [root@maven testdir] # cat testweb/src/main/webapp/index.jsp Hello World! [root@maven testdir] # cd testweb/ # enter [root@maven testweb] # mvn package # under the project directory Package as war package [root@maven testweb] # ls target/ # will generate a war package under this directory classes maven-archiver testweb testweb.war# will move the generated war package to the web page root (webapps) of Tomcat It will automatically extract, # and then access the war package generated by the Tomcat test # deploy Tomcat (see blog post: https://blog.51cto.com/14154700/2446054) [root@maven testweb] # mv target/testweb.war / usr/local/tomcat/webapps/ # move to the root directory of the Tomcat page [root@maven testweb] # / usr/local/tomcat/bin/startup.sh # start Tomcat [r oot@maven testweb] # ls / usr/local/tomcat/webapps/ # to view The war package is automatically decompressed, docs host-manager ROOT testweb.warexamples manager testweb.

The client accesses the war package moved to the root of the Tomcat web page:

II. Deploy Nexus private server

Nexus introduction

Nexus is the Maven warehouse manager, if we use Maven, we can download the required components (artifact) from the Maven central warehouse, but this is usually not done by the company. Generally, we set up a Maven warehouse server locally to agent the remote warehouse while maintaining the local warehouse to save bandwidth and time. Nexus can meet this need. In addition, it also provides a powerful warehouse management function, component search function, it is based on REST, friendly UI is an extjs REST client, it takes up less memory, based on a simple file system rather than a database. These advantages make it increasingly the most popular Maven warehouse manager.

Nexus is not the core concept of Maven, it is just a special Maven repository derived from it. For Maven, there are only two types of repositories: local and remote.

The local warehouse is the local warehouse address that we configured in the setting.xml of maven. Since the original local repository is empty, Maven must know at least one available remote repository in order to download the required artifacts when executing the Maven command. The central warehouse is the default remote warehouse for maven.

When there is a private service in the company structure, the workflow is as follows:

Private server is a special remote warehouse set up in the local area network, which aims to represent the remote warehouse and deploy third-party components. After having the private server, when the Maven needs to download the components, it directly requests the private server, and if it exists on the private server, it downloads it to the local warehouse; otherwise, the private server requests an external remote warehouse to download the components to the private server, and then provides it to the local warehouse for download.

The functions of Nexus are as follows:

1. Save the bandwidth of external network. A large number of repeated requests for external repositories will consume bandwidth. Using private servers to proxy external repositories can eliminate external repeated component downloads and reduce the pressure on bandwidth.

2. Accelerate the construction of Maven. Speed up Maven build. Constantly connecting to the external repository is time-consuming, and Maven constantly checks the data in the remote warehouse while performing the build. With private servers, Maven only checks the data of the local area network to improve the speed of construction.

3. Deploy third-party components. Deploy third-party components. When a component is not available from any external remote warehouse. Once the private server is established, these artifacts can be deployed to the private server for use by internal Maven projects.

4. Improve the stability and strengthen the control. Improve stability and enhance control. Maven builds are highly dependent on remote repositories, so when the network is unstable, Maven builds can become unstable or even impossible to build. Private server caches a large number of builds, and Maven can run normally even if there is no public network for the time being.

5. Reduce the load of the central warehouse. Reduce the load of the central warehouse. The use of private services can avoid many repeated downloads to the central warehouse and reduce the pressure on the central warehouse.

1. Start deploying Nexus

This thing always fails to download on the official website. It is prompted to time out and can be downloaded and used from the link to the network disk provided by me.

[root@maven ~] # mkdir / usr/local/nexus [root@maven ~] # tar zxf nexus-3.17.0-01-unix.tar.gz-C / usr/local/nexus/# to launch nexus must use nexus users, not users with excessive privileges, such as root Otherwise, it will fail to launch [root@maven ~] # useradd nexus [root@maven ~] # chown-R nexus:nexus / usr/local/nexus/ [root@maven ~] # cd / usr/local/nexus/ [root@maven nexus] # lsnexus-3.17.0-01 # this is the application directory sonatype-work # this is the working directory Store image repository # running memory and working directory nexus-3.17.0-01/bin/nexus.vmoptions (modify the corresponding field) # run listening address and port nexus-3.17.0-01/etc/nexus-default.properties [root@maven nexus] # ln-s / usr/local/nexus/nexus-3.17.0-01/bin/nexus / usr/local/bin/# create command soft connection # switch to nexus user and start the nexus service If you use a root user, you will fail to start because of high privileges [root@maven nexus] # su nexus [nexus@maven nexus] $nexus start # launch nexusStarting nexus [root@maven nexus] # netstat-anpt | grep 8081 # default listens to port 8081 tcp 00 0.0.0.00. Tcp 8081 0.0.0.0 * LISTEN 61881/java

After starting nexus, you can access the server IP+8081 port:

View the password according to the path prompted below:

[root@maven nexus] # cat / usr/local/nexus/sonatype-work/nexus3/admin.passworddb543002-f651-4785-b778-d158a5d3ea52 # copy the viewed password

To log in, the default user name is admin, and the password is what we found above:

Change the password for admin:

Create a role

Click create:

Create a user

View the default warehouse type

Warehouse type description:

Group (Warehouse Group Type): also known as Group Warehouse, which is used for the convenience of developers. Hosted (host type): release warehouse of internal project (warehouse released by internal developers) proxy (agent type): warehouse that looks for data from remote central warehouse (you can click on the Configuration page of the corresponding warehouse to sign the value of Remote Storage Location attribute) That is, the path to the remote warehouse being proxied) virtual (virtual type): virtual warehouse (this is basically unnecessary)

Warehouse type 3rd party under Public Repositories: component repositories for third-party released versions that are not available from public repositories, that is, third-party dependent repositories. This data is usually downloaded and released by insiders. Apache Snapshots: component repository that uses the snapshot version of the proxy ApacheMaven repository Central: the repository entral M1 shadow used to proxy the released version components in the central maven repository: the component image repository used to provide the released version in M1 format in the central warehouse Codehaus Snapshots: the repository Releases used to proxy the snapshot version artifacts of the CodehausMaven repository: the release repository of the release module in the internal module A repository of host types used to deploy and manage internal release artifacts Release is the release version; Snapshots: the repository for releasing internal SNAPSHOT modules, which is used to deploy and manage the host type repository for internal snapshot version artifacts; snapshots is the snapshot version, that is, the unstable version enables the repeat release permission of release.

If you need to distribute the version repeatedly in the development, you need to open the corresponding permission setting allow redeploy of the release type repository. As follows:

Set up agent warehouse (Aliyun maven warehouse)

URL: https://maven.aliyun.com/nexus/content/groups/public/ of Aliyun Warehouse

After filling in the above two contents, click the create repository at the bottom of the page to complete the creation, and you can see that Ali Cloud Library has been added.

Add the added Aliyun Proxy to the default group:

After saving, refresh the page again to see the current Nexus address:

Common usage scenarios for the above configurations are described as follows:

Release release Repository (nexus default established: maven-releasees) snapshot Test Center Snapshot Warehouse (nexus default established: maven-snapshots) central Central Warehouse (nexus default established: maven-central) about groups: groups can be established in nexus to gather different types of repositories together (nexus default established: maven-public) scenario 1: custom new proxy type warehouse, configure different call addresses in maven configuration Or join the custom newly created proxy repository into a group, and call an address scenario 2 in the maven configuration: use the proxy repository that has been established by maven, and configure the maven call address with the established group (maven-public). There is essentially no change in scenario 1 and scenario 2. Configure nexus private server according to the company's development habits and requirements. 3. Modify the settings configuration file [root@maven conf] # pwd/usr/local/maven/conf [root@maven conf] # vim settings.xml # add the following content nexus-testconf * nexus testconf http://192.168.20.2:8081/repository/maven-public/ # under the configuration of Ali Cloud Warehouse specified earlier. The URL above is in the The URL.. # omitted part of the content found on nexus # jumps to around 260 lines. Write the following content: testconf nexus http://192.168.20.2:8081/repository/maven-public/ true true nexus http://192.168.20.2: 8081/repository/maven-public/ true true # add the above to this line This line is about 260. omit part of the content testconf # the value here must correspond to the ID of the above profile before you can activate # write the field on top of the settings field # after adding, save and exit. 1. Create a maven project to test [root@maven ljzweb] # rm-rf ~ / .m2/ # first delete the cache of the local repository [root@maven testdir] # mvn archetype:generate-DgroupId=cn.ljz.ljzweb-DartifactId=ljzweb-DarchetypeArtifactId=maven-archetype-webapp-DinteractiveMode=false# construction project. You can see that the nexus private server address is used in the construction process. [root@maven testdir] # ls # View the built project ljzweb [root@maven testdir] # cd ljzweb/ [root@maven ljzweb] # ls pom.xml src [root@maven ljzweb] # mvn package # after packaging the project [root@maven ljzweb] # ls # package, it will generate the target directory pom.xml src target to view the cached files in nexus (if there are no cache files, here is a solution)

If you do not see the cached file on the above page because you currently do not have permission to write to nexus, you can do the following:

After making the above settings, delete the cache file in the local host directory again, rebuild the project, and package it, and you can see the cache file on nexus.

2. Configure authentication, upload the packaged project to nexus [root@maven ljzweb] # vim / usr/local/maven/conf/settings.xml# search for "server" field deploymentRepo repouser repopwd-> # navigate to the line, and write the following content: test-nexus # Custom ID testdev # the user name jianzhao87 that has just been added to the web page of nexus. # user name password

Modify the pod.xml file of the project:

[root@maven ljzweb] # pwd/tmp/testdir/ljzweb [root@maven ljzweb] # lspom.xml src target [root@maven ljzweb] # vim pom.xml # Edit configuration file. # omit part of the content The following is the manual addition of test-nexus # the ID here must be consistent with the ID configured in the above settings file, Nexus Snapshot http://192.168.20.2:8081/repository/maven-snapshots/ # above is the revised version of URL You can view test-nexus Nexus releases http://192.168.20.2:8081/repository/maven-releases/ # in the web interface of nexus, which is the release version of URL, and also in the Repositories of the web interface, you can see # add the above above on the last line # after the change Save and exit, then [root@maven ljzweb] # mvn deploy # upload to nexus private server

Confirm that the upload is successful on the web interface:

Expand all the content, and you can see the following:

If an error occurs during deployment, first check whether the account password of the configuration file setting.xml is the same as the user password created by nexus, and then check whether the id tag in setting.xml is the same as the id tag in pom.xml file.

3. Upload to [root@maven ljzweb] # pwd/tmp/testdir/ljzweb [root@maven ljzweb] # vim pom.xml 1.0-SNAPSHOT # to remove the "SNAPSHOT" in the above line, and change it as follows: 1. Save and exit after modification, and then [root@maven ljzweb] # mvn deploy # upload again

View it in the web interface as follows:

Expand all nodes and you can see the following:

Upload the third party maven package to the nexus private server

Configure it as follows (define the name and activate it), then drag it to the bottom of the page and click add.

Maven add third-party warehouse address (global configuration)

# Edit the main configuration file [root@maven ljzweb] # vim / usr/local/maven/conf/settings.xml# in the previous profiles Fill in the following content: 3rdnexus http://192.168.20.2:8081/repository/3rd/ true true # add to the Profiles tag # in the previous authentication field, and then add an authentication test-nexus testdev jianzhao87. # just under the server authentication added earlier, fill in the following content: 3rdnexus # this ID corresponds to the testdev jianzhao87 in the profile. # after the changes are completed, save and exit [root@maven testdir] # ls # upload the jar package aliyun-sdk-oss-2.6.1.jar [root@maven testdir] # mvn deploy:deploy-file-DgroupId=com.aliyun.oss-DartifactId=aliyun-sdk-oss-Dversion=2.6.1-Dpackaging=jar-Dfile=/tmp/testdir/aliyun-sdk-oss-2.6.1.jar-Durl= http://192.168.20.2:8081/repository/3rd/-DrepositoryId=3rdnexus# build the project based on the local jar package

Check the locally uploaded jar package:

-this is the end of this article. Thank you for reading-

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.