Ideas
in the prevalence of micro-services of the moment, spring boot popularity has been a household name. But at the same time, with the spring boot rapid iteration, there have been many versions, such as the current has launched 2.2.x-SNAPSHOT /, spring assemblies of different versions of spring boot for supporting the use of versions of third-party components are required.
In our usual development, when the need to integrate some spring boot function, occasionally encountered package version conflict, although we know the version of the conflict, but do not know which version to use this? At this point, if we can use their own version of spring boot, and then to query the corresponding version of the package conflict, then the problem will soon be solved.
In the Give a man a fish than giving the fishing principle, after one error investigation and found compatible version of spring boot is actually launched in each version, that they will Annotated related packages. For example, the following address:
https://docs.spring.io/spring-boot/docs/2.0.3.RELEASE/reference/htmlsingle/#appendix-dependency-versions
The address shown is spring boot 2.0.3-RELEASE compatible with the version number of each dependent.
Expand
according to the above address, I try to find other spring boot version dependencies version number in accordance with the law, we found that as long as the replacement 2.0.3-RELEASE above url in the corresponding version number, you can check the version number of the corresponding dependencies.
According to the above example, the address of each assembly 1.3.5-RELEASE version dependencies:
https://docs.spring.io/spring-boot/docs/1.3.5.RELEASE/reference/htmlsingle/#appendix-dependency-versions
Finally, https: //docs.spring.io/spring-boot/docs/ directory is the document under all versions of spring boot number.
This is indeed a very fast hardware method, the basic problem to get spring-boot version conflict
Original blog: https://blog.csdn.net/li396864285/article/details/87693633