On spring’s BOM for solving jar package dependency

Explanation of terms:

Bill of materials: Bill of materials, which is a good method to solve jar package dependency.

Spring IO Platform

Origin: spring only focused on IOC and AOP at first, but now it has developed into a huge system. Such as security, MVC, etc. In this way, when different modules or external integration, dependency processing requires their corresponding version numbers. For example, the integration of newer spring and older quartz will encounter problems, which will bring inconvenience to the construction and upgrading. Therefore, the spring IO platform came into being. As long as it is introduced into the project, the dependency during external integration does not need a version number. The original text of the official website is as follows: "when you do declare a dependency on something that's part of the platform, you will now be able to omit the version number." Examples are as follows:

The spring IO platform is just a POM file that records the corresponding versions of spring and other open source projects. The version number is omitted, which eliminates the problem of dealing with dependencies, because there is an optimal version configuration in the spring IO platform.

Spring related BOM

Of course, in order to solve these jar conflicts, springsource has launched various BOMs. Of course, the most famous is spring platform IO BOM, of which the three core are spring framework BOM, spring boot dependencies and platform BOM.

For the spring project, directly in POM Add the following configuration code to the XML file to avoid the problem of managing version conflicts.

Reference articles

Introduction to spring io platform