[Nexus of Maven Private Server]

Companies generally have their own private server to manage various jar packages. There are about three reasons, namely:

1. Some companies cannot access the external network, and can only manage jar packages and plug-ins through private servers;

2. The company's network speed is relatively slow, and it is faster to obtain the jar package through the company's private server;

3. Some internal jar packages are placed on the private server, which is more convenient for everyone to use.



 

There is a public maven warehouse server, why build a maven private server? After building locally, there are several advantages as follows:

1. Speed ​​up the construction;

2. Save bandwidth;

3. Save the bandwidth of the central maven warehouse;

4. Stable (should act in the event of a problem with the central server);

5. Control and audit;

6. Ability to deploy third-party components;

7. Local internal warehouse can be established;

8. A public warehouse can be established.

 

 

 

Why use Nexus

If there is no private server, all the components we need need to be downloaded to the local through maven's central warehouse and third-party Maven warehouse, and everyone in a team repeatedly downloads components from the maven warehouse, which undoubtedly increases the load of the warehouse and The extra network bandwidth is wasted, and if the network speed is slow, it will also affect the progress of the project. In many cases, the development of the project is carried out on the intranet, what should I do if I cannot connect to the maven warehouse? How can the developed public components be used by other projects? At this time, we have to build our own maven private server for our team, which not only saves network bandwidth but also speeds up the project construction process. Of course, the prerequisite is that your private server has all the components required for the project.

 



 

There are four types of warehouses in nexus:

group: warehouse group

hosted: host

proxy: proxy

virtual: virtual

 

Hosted repository: It is mainly used to deploy components that cannot be obtained from public repositories (such as Oracle's JDBC driver) and its own or third-party project components;

proxy proxy warehouse: proxy public remote warehouse;

virtual virtual warehouse: used to adapt to Maven 1;

group warehouse group: Nexus manages multiple warehouses uniformly through the concept of warehouse group, so that we can request multiple warehouses managed by the warehouse group directly by requesting the warehouse group in the project.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326306628&siteId=291194637