Spring Cloud version version named specification (Edgware)

Spring Cloud version version named specification (Edgware)

Copyright: guofangsky Copyright, reproduced impunity. https://blog.csdn.net/guofangsky/article/details/82868564

spring boot / cloud projects, see the following configuration:

  1.  
    <parent>
  2.  
    <groupId>org.springframework.cloud</groupId>
  3.  
    <artifactId>spring-cloud-starter-parent</artifactId>
  4.  
    <version>Edgware.SR3</version>
  5.  
    <relativePath/>
  6.  
    </parent>

After the inspection, its version follows, Spring Cloud Imprint

Spring Cloud is a large-scale integrated project comprising of a number of independent sub-projects, each subproject has a different rhythm issue, maintains its own release number. Spring Cloud through a resource list of BOM (Bill of Materials) to manage each version of the sub-project list. To avoid confusion with the release number of sub-projects, so there is no way the use of version numbers, but by naming the way.

These versions naming names using the name of the London Underground station, but according to the order of the alphabet to the corresponding version of chronological order, such as: the first Release version: Angel, Second Release version: Brixton, followed by Camden, Dalston, Edgware , the latest version is Finchley.

When publishing content after a version of the Spring Cloud projects accumulated to a critical point or to solve a serious bug, it will publish a "service releases" version, referred to as the SRX version, where X is an incrementing number. The current official online the latest stable version is Edgware.SR3, a milestone version is Finchley.M9. The following table lists the version numbers of both versions contain subprojects and each subproject.

Component Edgware.SR3 Finchley.M9 Finchley.BUILD-SNAPSHOT
spring-cloud-aws 1.2.2.RELEASE 2.0.0.M4 2.0.0.BUILD-SNAPSHOT
spring-cloud-bus 1.3.2.RELEASE 2.0.0.M7 2.0.0.BUILD-SNAPSHOT
spring-cloud-cli 1.4.1.RELEASE 2.0.0.M1 2.0.0.BUILD-SNAPSHOT
spring-cloud-commons 1.3.3.RELEASE 2.0.0.M9 2.0.0.BUILD-SNAPSHOT
spring-cloud-contract 1.2.4.RELEASE 2.0.0.M8 2.0.0.BUILD-SNAPSHOT
spring-cloud-config 1.4.3.RELEASE 2.0.0.M9 2.0.0.BUILD-SNAPSHOT
spring-cloud-netflix 1.4.4.RELEASE 2.0.0.M8 2.0.0.BUILD-SNAPSHOT
spring-cloud-security 1.2.2.RELEASE 2.0.0.M3 2.0.0.BUILD-SNAPSHOT
spring-cloud-cloudfoundry 1.1.1.RELEASE 2.0.0.M3 2.0.0.BUILD-SNAPSHOT
spring-cloud-consul 1.3.3.RELEASE 2.0.0.M7 2.0.0.BUILD-SNAPSHOT
spring-cloud-sleuth 1.3.3.RELEASE 2.0.0.M9 2.0.0.BUILD-SNAPSHOT
spring-cloud-stream Ditmars.SR3 Elmhurst.RC3 Elmhurst.BUILD-SNAPSHOT
spring-cloud-zookeeper 1.2.1.RELEASE 2.0.0.M7 2.0.0.BUILD-SNAPSHOT  
spring-boot 1.5.10.RELEASE 2.0.0.RELEASE 2.0.0.BUILD-SNAPSHOT
spring-cloud-task 1.2.2.RELEASE 2.0.0.M3 2.0.0.RELEASE
spring-cloud-vault 1.1.0.RELEASE 2.0.0.M6 2.0.0.BUILD-SNAPSHOT
spring-cloud-gateway 1.0.1.RELEASE 2.0.0.M9 2.0.0.BUILD-SNAPSHOT
spring-cloud-openfeign   2.0.0.M2 2.0.0.BUILD-SNAPSHOT

Finchley and Spring Boot 2.0.x, compatible and does not support the Boot 1.5.x. the Spring
Dalston and Edgware and Spring Boot 1.5.x, compatible and does not support the Boot 2.0.x. the Spring
Camden is built on Spring Boot 1.4.x, above but also supports 1.5.x.
Brixton is built on Spring Boot 1.3.x, above, but also supports 1.4.x.
Angel is built in, on top of Spring Boot 1.2.x, but is also compatible with Spring Boot 1.3.x.
Note: Angel and two versions of Brixton was terminated in July 2017 is no longer maintained.
Note: Angel and two versions of Brixton was terminated in July 2017 is no longer maintained.

Codenamed seemingly no law, but in fact the first letter is in order, such as: Dalston version, we referred to as D version, Edgware corresponding version we referred to as E version.

The difference between D and E versions version

Both are based on the 1.5.x version SpringBoot. But support different versions of other components, such as the Dalston.SR4 and Edgware.RELEASE to compare:

spring-cloud-config and correspond 1.3.3 1.4.0;
Spring-Cloud-1.3.5 and 1.4.0, respectively, corresponding to Netflix;
Spring-Cloud-Consul and 1.2.1 respectively 1.3.0;
Spring-Gateway-Cloud The former is not supported, the latter 1.0.0.

Different versions of each small, there will be nuances.

F version

F version is definitely the big version, almost all of the components, all synchronized to change the version number is 2.x.

Small version

Spring Cloud small version is divided into:

SNAPSHOT: snapshot version, subject to modification

M: MileStone, M1 represents a milestone version, while generally marked PRE, expressed preview version.

SR: Service Release, SR1 represents an official version, while the general labeling GA: (GenerallyAvailable), represents a stable version.

Select Version

idea inside the RC version

idea inside the RC version English version called Release Candidate (release candidate)

Large version

First, small changes in the components between the various versions, but the details are slightly different, such as configuration item name, or the new version adds new configuration.
From this point of view, to choose which version is not a big problem, but a reminder, the face of the pit, the best query depending on the version, otherwise you will find that you find a way of not. It is actually a version mismatch.

If you need to project and other projects cross-old, to be compatible for the cause.

If the new project, you can consider a newer version, such as the E version. If you are interested in stepping pit, F take.

Small version

Small version of nothing to say, early adopters: SNAPSHOT, production: GA.

 

Guess you like

Origin www.cnblogs.com/lykbk/p/fedfed43t5345435445.html