SpringCloud Caused by: org.springframework.boot.web.server.WebServerException: Unable to start embedded

This problem occurs, there may be a spring cloud and spring boot version mismatch problems caused by, the use of version: Finchley.RC1

 

After a keyword search, find spring cloud and spring boot has a more stringent version of the match. It can not be like the development of monolithic applications, subject to change version of spring boot.

Now the corresponding version of the rules written down, cited other users blog.

Source: https: //www.cnblogs.com/it-taosir/p/9979579.html

A common version Description 

  For melon: 2.0.3 the RELEASE 

  2: major version number, when there is a large update function modules or the overall structure changes, the major version number will be updated 

  0: minor version number. Minor version changes represent just some of the local. 

  2: Modify the version number. General bug changes or small changes 

  RELEASE: Greek alphabet version number. This marked the version number of the current user version of the software which is in the development stage 

 

two, the Greek alphabet version 

  Base: design phase. Only appropriate design no specific function realization. 

  Alpha: preliminary version of the software. The basic function has been achieved, but there are more bug. 

  Bate: with respect to the Alpha has made great progress, eliminating the serious BUG, but there are still some potential BUG, also need to continue testing. 

  RELEASE: The final version, there is not much of a problem. 

 

Three, SpringCloud version 

  1) Why springcloud versions use the word rather than numbers? 

    The purpose is to design better inventory management SpringCloud each subproject, to avoid their own version and the version number of subprojects confusion. 

  2) What are the rules it? 

    (The common name of the London subway station named) after the first letter on the version number greater 

  3) with respect to the release notes? 

    BUILD-XXX development version of the development team for internal use, not very stable 

    GA compared to the stable version development version, you can basically use

    PRE (M1, M2) milestone moderator if fixes some BUG version, usually have multiple milestone version after a GA 

    RC release candidate stage of the software is similar to a final release version of the observation period, only basic repair more serious BUG 

    SR officially released version ~ ~ ~ ~ nothing to say on this matter

 

 

Guess you like

Origin www.cnblogs.com/QW-lzm/p/11946613.html