From ec65d1b69f8783b51e3760e9106828b83e67b08b Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Fri, 5 May 2017 11:42:59 +0200 Subject: [PATCH] Updated docs --- docs/src/main/asciidoc/spring-cloud-wiremock.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/spring-cloud-wiremock.adoc b/docs/src/main/asciidoc/spring-cloud-wiremock.adoc index 4500b75ff3..7ee2507e4c 100644 --- a/docs/src/main/asciidoc/spring-cloud-wiremock.adoc +++ b/docs/src/main/asciidoc/spring-cloud-wiremock.adoc @@ -289,7 +289,7 @@ NOTE: You can use either the `wiremock()` method or the `jsonPath()` and `contentType()` methods to create request matchers, but not both. On the consumer side, you can make the `resource.json` generated above -available on the classpath (by https://cloud.spring.io/spring-cloud-contract/1.0.x/#_publishing_stubs_as_jars[publishing stubs as JARs] for example). +available on the classpath (by https://cloud.spring.io/spring-cloud-contract/spring-cloud-contract.html#_publishing_stubs_as_jars[publishing stubs as JARs] for example). After that, you can create a stub using WireMock in a number of different ways, including as described above using `@AutoConfigureWireMock(stubs="classpath:resource.json")`.