Reputation: 1241
All, I'm having an issue using Spring Cloud 1.0.1 that I'm not having in Spring Cloud 1.0.0. Specifically, clients are no longer able to reach the config server.
I have a Spring Cloud Config Server up and running using 1.0.1.RELEASE. In building the client, I'm referring to the documentation here: http://projects.spring.io/spring-cloud/docs/1.0.1/spring-cloud.html#_client_side_usage. This refers to a parent with version 1.0.0.BUILD-SNAPSHOT, which is not released. So my first question is, is the documentation incorrect here when referring to this version? I would expect the version to be 1.0.1.RELEASE.
Assuming it is, I find that my client connects to the config server perfectly when using version 1.0.0.RELEASE of spring-cloud-starter-parent. But if I switch this to 1.0.1.RELEASE, the client no longer finds the config server (keep in mind, the config server is using 1.0.1.RELEASE). There is no error, the console logging simply does not emit any references to the CompositePropertySource that one ordinarily sees when the client finds the server.
Is there a change from 1.0.0.RELEASE to 1.0.1.RELEASE that requires some extra setting that isn't described?
Upvotes: 0
Views: 167
Reputation: 359
1.0.1.RELEASE
version of the parent.spring-cloud-starter
does not include the config client, so you need to specify the spring-cloud-starter-config
dependency explicitly.Upvotes: 1