Navigating Spring Cloud Version Compatibility: Tips & Common Pitfalls

Opening: Version Dependency Relationships

In a previous post titled “Talking About Spring Cloud Versions”, the origins of Spring Cloud version naming and the version‑numbering rules were explained, along with a table of each release’s dependency set to help developers choose the appropriate version for microservice projects.

Because Spring Cloud evolves rapidly and comprehensive Chinese documentation is scarce, many beginners encounter problems when they overlook version compatibility. A frequent issue appears when using Feign, producing the following error:

org.springframework.core.annotation.AnnotationConfigurationException: Attribute 'value' in annotation [org.springframework.cloud.netflix.feign.FeignClient] must be declared as an @AliasFor [serviceId], not [name].

This error often occurs when code written for the Brixton release (which depends on Spring Boot 1.3.x) is run with a newer Spring Boot version such as 1.4.x, or when developers prefer to stay up‑to‑date.

Recommended Spring Cloud–Spring Boot Pairings

Angel → Spring Boot 1.2.x

Brixton → Spring Boot 1.3.x

Camden → Spring Boot 1.4.x

For most projects, the latest Camden release paired with Spring Boot 1.4.x is recommended. Beyond the core Spring Boot improvements, Camden upgrades Spring Cloud component versions (e.g., Spring Cloud Netflix moves from 1.1.x in Brixton to 1.2.x in Camden). The newer 1.2.x line adds useful features such as RestTemplate request retry (previously covered in the “Configuring Spring Cloud Ribbon Retry (Camden.SR2+)” article) and various Zuul header optimizations.

The upcoming “Spring Cloud Practical Tips” series will concentrate on three areas: analysis of common problems, practical construction tricks, and design considerations for real‑world implementations.

This article is licensed under CC BY 3.0 CN, allowing free redistribution with proper attribution.