Looking at Maven Central, it looks to me like every other Spring Cloud project publishes its own dependency management, which in turn is imported into spring-cloud-dependencies.
With Spring Cloud Dependencies 2020.0.x, Spring Cloud Stream Dependencies managedspring-cloud-schema-registry dependencies to 1.1.5. Starting with Spring Cloud Dependencies 2021.0.0 (and spring-cloud-stream dependencies 3.2.1), management of spring-cloud-schema-registry was dropped. Thus, users of spring-cloud-schema-registry need to explicitly manage this version and can't rely on Spring Cloud's dependency management.
In my opinion, spring-cloud-schema-registry should publish its own spring-cloud-schema-registry-dependencies POM, that can then be imported in the next Spring Cloud dependencies.
Looking at Maven Central, it looks to me like every other Spring Cloud project publishes its own dependency management, which in turn is imported into spring-cloud-dependencies. With Spring Cloud Dependencies 2020.0.x, Spring Cloud Stream Dependencies managed
spring-cloud-schema-registry
dependencies to1.1.5
. Starting with Spring Cloud Dependencies 2021.0.0 (and spring-cloud-stream dependencies3.2.1
), management of spring-cloud-schema-registry was dropped. Thus, users of spring-cloud-schema-registry need to explicitly manage this version and can't rely on Spring Cloud's dependency management.In my opinion, spring-cloud-schema-registry should publish its own
spring-cloud-schema-registry-dependencies
POM, that can then be imported in the next Spring Cloud dependencies.