What’s New in Spring Cloud 2022.0.0-M1? A Quick Overview
This article reviews the Spring Cloud 2022.0.0-M1 milestone release, highlighting its compatibility with Spring Boot 3, key component removals, OAuth integration updates, annotation changes, and future plans for Spring Cloud Netflix, while directing readers to the official release notes for full details.
On the first day back to work, the author wishes Happy New Year and reviews recent Spring updates, focusing on Spring Cloud 2022.0.0-M1, the first milestone compatible with Spring Boot 3.
Spring Cloud 2022.0.0-M1 (Kilburn) was announced on January 27 as the first Spring Cloud milestone that aligns with Spring Boot 3.0.0-M1, which itself uses Spring Framework 6.0.0-M2, requires Java 17, and adopts Jakarta EE.
Key changes in the Spring Cloud family include:
Removal of Spring Cloud CloudFoundry and CLI from the release series.
Spring Cloud Commons: OAuth integration migrated from the deprecated Spring Security OAuth to OAuth2 support in Spring Security.
Spring Cloud Kubernetes: the annotation @ConditionalOnKubernetesEnabled is removed and replaced by @ConditionalOnCloudPlatform.
Spring Cloud Task: version 3.0.0-M1 aligns with Spring Boot 3.0.0-M1.
Spring Cloud Contract remains part of the 2022.0.0-M1 release and will be included in the upcoming M2.
Spring Cloud Netflix is not yet part of 2022.0.0-M1; it will be added when Eureka becomes Jakarta EE compatible.
Further details can be found in the official release notes at https://github.com/spring-cloud/spring-cloud-release/wiki/Spring-Cloud-2022.0-Release-Notes.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Programmer DD
A tinkering programmer and author of "Spring Cloud Microservices in Action"
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
