Ryan Baxter
Ryan Baxter
Yes we would need to keep the existing public APIs intact and unchanged and mark them all as `@Deprecated` then introduce the new ones (as you already have in this...
Can you provide a [complete, minimal, verifiable sample](https://stackoverflow.com/help/mcve) that reproduces the problem? It should be available as a GitHub (or similar) project or attached to this issue as a zip...
Can you provide a [complete, minimal, verifiable sample](https://stackoverflow.com/help/mcve) that reproduces the problem? It should be available as a GitHub (or similar) project or attached to this issue as a zip...
Spring Cloud Loadbalancer is the replacement for Spring Cloud Netflix Ribbon https://docs.spring.io/spring-cloud-commons/reference/spring-cloud-commons/loadbalancer.html
@snicoll do you mean `https://cloud.spring.io/spring-cloud-static/current/spring-cloud.html` `https://cloud.spring.io/spring-cloud-static/current/multi/multi__spring_cloud_context_application_context_services.html#_the_bootstrap_application_context`? I don't understand why you would expect `Greenwich.SR1/current` to work and your second URL works fine for me.
See https://github.com/spring-cloud/spring-cloud-release-tools/issues/165
@snicoll according to @marcingrzejszczak it does. @marcingrzejszczak can you explain?
Looks like actuator is missing, what exactly are you running?
As long as the API in the Spring Cloud project is stable we wouldnt mind using something that is incubating but if that Spring Cloud API could change as well...