Spring Cloud Hoxton SR1 Released: New Features, Maven BOM & Bug Fixes
Spring Cloud Hoxton SR1 has been officially released, bringing Spring Boot 2.2.2 as the core dependency, updated Maven BOM, new features across Config, Commons, Sleuth, Gateway and OpenFeign, as well as numerous bug fixes and detailed release notes for developers.
Spring Cloud Hoxton SR1 (maintenance release) is officially available.
Core Dependency
Spring Boot 2.2.2Maven Dependency
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-dependencies</artifactId>
<version>Hoxton.SR1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>Release Notes
Spring Cloud Config
New feature: support for AWS S3 environment storage of plain‑text resources.
Spring Cloud Commons
New feature: support for Spring Cloud LoadBalancer with zone awareness.
Spring Cloud Sleuth
New feature: support for Spring Cloud CircuitBreaker.
Spring Cloud Gateway
New feature: ability to configure route timeout.
Spring Cloud OpenFeign
FeignBlockingLoadBalancerClientchanged to public visibility for easier extension. DefaultGzipDecoder charset changed to UTF‑8.
Bug Fixes
For detailed issue list, see the project board and release notes:
https://github.com/orgs/spring-cloud/projects/34
https://spring.io/blog/2019/12/21/spring-cloud-hoxton-service-release-1-sr1-is-available
https://github.com/spring-projects/spring-cloud/wiki/Spring-Cloud-Hoxton-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.
Java Architecture Diary
Committed to sharing original, high‑quality technical articles; no fluff or promotional content.
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.
