Is your feature request related to a problem? Please describe.
The recent release of Spring Boot 3.2.0 has created a hole for consumers. At the present time, Spring Cloud 2022.x only supports Spring Boot 3.0.x and 3.1.x, and does not work (fails at runtime) if used with Spring Boot 3.2.x - this appears to be "as designed". Meanwhile, the next-gen Spring Cloud 2023.x is only released as an RC meaning it is not available at places like Maven Central.
Describe the solution you'd like
For early-adopters like myself, I'd like to see a 2023.0.0 on maven-central just so I could move forward. Lack of a public 'cloud' dependency means I cannot use anything from Spring Boot at all. Even if cloud is still tying up loose ends, let there be a (good-enough) 2023.0.0 and follow it up with a 2023.0.1 shortly thereafter that cleans up whatever is left. Or, alternatively, push the 2023 RC version to maven central.
Any version of spring-cloud 2023.x in Maven Central will satisfy this issue.
Describe alternatives you've considered
Consumers can add the spring snapshots repo to their config, but this then has to be undone later when you do release. I also encounter the belief that because something is not on maven-central, then it must be not-good or not intended for public consumption.
Additional context
Add any other context or screenshots about the feature request here.
spencergibb
commented
9 months ago
Is your feature request related to a problem? Please describe. The recent release of Spring Boot 3.2.0 has created a hole for consumers. At the present time, Spring Cloud 2022.x only supports Spring Boot 3.0.x and 3.1.x, and does not work (fails at runtime) if used with Spring Boot 3.2.x - this appears to be "as designed". Meanwhile, the next-gen Spring Cloud 2023.x is only released as an RC meaning it is not available at places like Maven Central.
Describe the solution you'd like For early-adopters like myself, I'd like to see a 2023.0.0 on maven-central just so I could move forward. Lack of a public 'cloud' dependency means I cannot use anything from Spring Boot at all. Even if cloud is still tying up loose ends, let there be a (good-enough) 2023.0.0 and follow it up with a 2023.0.1 shortly thereafter that cleans up whatever is left. Or, alternatively, push the 2023 RC version to maven central. Any version of spring-cloud 2023.x in Maven Central will satisfy this issue.
Describe alternatives you've considered Consumers can add the spring snapshots repo to their config, but this then has to be undone later when you do release. I also encounter the belief that because something is not on maven-central, then it must be not-good or not intended for public consumption.
Additional context Add any other context or screenshots about the feature request here.