without this change if you want to use Spring Cloud Contract Stub Runner Cloud you need to have an implementation of Service Discovery on your classpath. That's not always what you want to have - actually the tests should be possible to be run without any backing service disvoery technology.
This change provides the default NoOp Discovery Client in case where there is no bean of DiscoveryClient type.
fixes#56
there was a problem with the way property related to array size check was passed. Not only was the condition inverse, but also the properties weren't passed.
With this change those issues were fixed, we've added the missing maven plugin feature and ensured that the array check is the default option.
fixes#60
There is no need for users to know about any special contract-specific
Message object (payload and headers). Once you see that, it seems like
there is no need for it internally either. So this change removes the
message wrapper type and cleans up the interfaces it touches.
In a Spring test user can add this annotation to run stubs
rather than rely on auto configuration (which might not be
welcome outside a test).
Fixes gh-33
to org.springframework.cloud from org.springframework.cloud.contract
also stopped running an http server if the contract doesn't support it
added back stub runner modules
User can depend on spring-cloud-contract-wiremock and
spring-cloud-starter-web (or tomcat) to get tomcat to run
the wiremock server. The idea is that wiremock runs in the
"ambient" server from Sprign Boot. So far we only support
Tomcat (should be easy to extend).
See tests in spring-cloud-contract-wiremock for details.
