From a5091249766193fb95a028dfb606995e6c592b22 Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Fri, 23 Dec 2016 14:38:46 +0100 Subject: [PATCH] Added info about WireMock exclusions to the docs without this change if someone used the Spring Cloud BOM one could have some dependency related issues coming from exclusions of WireMock dependencies in SPring CLoud COntract with this change we're informing the user about this fixes #146 --- docs/src/main/asciidoc/spring-cloud-wiremock.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/src/main/asciidoc/spring-cloud-wiremock.adoc b/docs/src/main/asciidoc/spring-cloud-wiremock.adoc index ef5375200a..9f1b2630d1 100644 --- a/docs/src/main/asciidoc/spring-cloud-wiremock.adoc +++ b/docs/src/main/asciidoc/spring-cloud-wiremock.adoc @@ -7,6 +7,11 @@ http://wiremock.org[WireMock] with different servers by using the https://github.com/spring-cloud/spring-cloud-contract/tree/master/samples[samples] for more details. +IMPORTANT: The Spring Cloud Release Train BOM imports `spring-cloud-contract-dependencies` + which in turn has exclusions for the dependencies needed by WireMock. This might lead to a situation that + even if you're not using Spring Cloud Contract then your dependencies will be influenced + anyways. + If you have a Spring Boot application that uses Tomcat as an embedded server, for example (the default with `spring-boot-starter-web`), then you can simply add `spring-cloud-contract-wiremock` to your classpath