One 、 Configure authentication information

stay Maven Of conf Catalog settings.xml  Add Nexus Authentication information (servers  Under the node )：

 <!-- Configure the user name and password to access the private server  -->
	   <server>
            <id>releases</id><!-- Official library    issue -->
			<username>admin</username>
			<password>admin123</password>
		</server>
		<server>

			<id>snapshots</id><!-- Test library   snapshot -->
			<username>admin</username>
			<password>admin123</password>
			</server>
			
	    <server>
			<id>thirdparty</id>
			<username>admin</username>
			<password>admin123</password>
		</server>

1、Snapshots And Releases The difference between

• nexus-releases: For publishing Release edition
• nexus-snapshots: For publishing Snapshot edition （ Snapshot version ）

Release Version and Snapshot The definition is as follows ：

Release: 1.0.0/1.0.0-RELEASE
Snapshot: 1.0.0-SNAPSHOT

• In the project  pom.xml  Add... To the version number set in  SNAPSHOT  The logo will be published as  SNAPSHOT  edition , No,  SNAPSHOT  The logo will be published as  RELEASE  edition .
• SNAPSHOT  The version will be automatically marked with a time , Such as ：1.0.0-SNAPSHOT  After release, it becomes  1.0.0-SNAPSHOT-20180522.123456-1.jar

Two 、 Configure automated deployment ( Automatic transmission jar To private server )

1、 add to POM rely on

stay  pom.xml  Add the following code to ：

<distributionManagement>  
  <repository>  
    <id>nexus-releases</id>  
    <name>Nexus Release Repository</name>  
    <url>http:// Private service warehouse IP:8081/repository/maven-releases/</url>  
  </repository>  
  <snapshotRepository>  
    <id>nexus-snapshots</id>  
    <name>Nexus Snapshot Repository</name>  
    <url>http:// Private service warehouse IP:8081/repository/maven-snapshots/</url>  
  </snapshotRepository>  
</distributionManagement> 

2、 Pull snapshot dependency

stay idea Set in maven You can pull the snapshot version to rely on

In this way, when team collaborative development , Or multiple companies jointly develop , In order to prevent the source code that the public module depends on from being leaked due to open source , You can upload the code of the public module to the private server , Team members pull it in time OK 了 .

3、 ... and 、 Deploy to warehouse

The command will depend on jar Package deployment only in private server

mvn deploy

  In order not to let the test file execute , Select skip test file

mvn deploy -Dmaven.test.skip=true

stay Nexus You can see jar Packet dependency

snapshots It's a snapshot version ( The beta ), Sometimes it's released many times , however Nexus The version number in the private server has been determined , Can't you upload ？

Of course not. ,Nexus The private server will generate a timestamp according to the time + Number of Uploads Generate a second version , Keep the first .

Continue the second deployment upload

mvn deploy -Dmaven.test.skip=true

A second version will be generated

 

Four 、 Upload third party JAR package

Nexus 3.0 Page upload is not supported , You can use maven command ：

Google com.google.code.kaptcha jar For example, bag , Google's jar The bag needs to climb over the wall , All must be uploaded to the private server first , To successfully pull .

mvn deploy:deploy-file 
   # Organization name 
  -DgroupId=com.google.code.kaptcha
   #jar Package name 
  -DartifactId=kaptcha 
   #  Version number 
  -Dversion=2.3.2
   # file type 
  -Dpackaging=jar 
   # File address 
  -Dfile=D:\kaptcha-2.3.2.jar 
   # Upload destination 
  -Durl=http://192.168.153.142:8081/repository/maven-releases/
   #settings In profile releases Corresponding ID
  -DrepositoryId=nexus-releases

In order to avoid the influence of Chinese comments, remove the comments

mvn deploy:deploy-file 
  -DgroupId=com.google.code.kaptcha
  -DartifactId=kaptcha 
  -Dversion=2.3.2
  -Dpackaging=jar 
  -Dfile=D:\kaptcha-2.3.2.jar 
  -Durl=http://192.168.153.142:8081/repository/maven-releases/
  -DrepositoryId=nexus-releases

open CMD Command line tools or idea The terminal changes the above instruction to one line , Copy in , Enter to execute

You can see that the build was successful

open Nexus The private server can see the uploaded Jar package .

 

5、 ... and 、 Configure agent warehouse

maven seek Jar Order of packages :

Find the corresponding... In the central warehouse Jar Download and store the package later ：

Store it in the private server warehouse first , The project is then downloaded from the private server , Pull like this Jar Your efficiency will be greatly improved , also , Once downloaded, it will be stored permanently . Reusable

<!-- Configure agent warehouse   Specify the private server location to download dependency -->
    <repositories>
        <repository>
            <id>nexus</id>
            <name>Nexus Repository</name>
            <url>http://192.168.153.142:8081/repository/maven-public/</url>
            <!-- Whether it is allowed to rely on the snapshot version -->
            <snapshots>
                <enabled>true</enabled>
            </snapshots>
            <!-- Whether dependency on distribution is allowed -->
            <releases>
                <enabled>true</enabled>
            </releases>
        </repository>
    </repositories>
    <!-- Plug-in repository -->
    <pluginRepositories>
        <pluginRepository>
            <id>nexus</id>
            <name>Nexus Plugin Repository</name>
            <url>http://192.168.153.142:8081/repository/maven-public/</url>
            <snapshots>
                <enabled>true</enabled>
            </snapshots>
            <releases>
                <enabled>true</enabled>
            </releases>
        </pluginRepository>
    </pluginRepositories>

Delete the original Jar package

Refresh dependency

Dependence is pulled back