From 408644630ae6808f14e109ae99dc0bf78f4015fc Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Tue, 24 Dec 2019 00:04:58 +0100 Subject: [PATCH] Revert "Corrected links to use samples_branch rather than branch in documentation. (#1293)" (#1295) This reverts commit 4e5505269e9920d18d6411d0f70b0fbee9ef364a. --- docs/src/main/asciidoc/_project-features-wiremock.adoc | 4 ++-- docs/src/main/asciidoc/howto.adoc | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/src/main/asciidoc/_project-features-wiremock.adoc b/docs/src/main/asciidoc/_project-features-wiremock.adoc index df62f8fbea..db4484d9cc 100644 --- a/docs/src/main/asciidoc/_project-features-wiremock.adoc +++ b/docs/src/main/asciidoc/_project-features-wiremock.adoc @@ -4,7 +4,7 @@ include::_attributes.adoc[] The Spring Cloud Contract WireMock modules let you use https://github.com/tomakehurst/wiremock[WireMock] in a Spring Boot application. Check out the -https://github.com/spring-cloud/spring-cloud-contract/tree/{samples_branch}/samples[samples] +https://github.com/spring-cloud/spring-cloud-contract/tree/{branch}/samples[samples] for more details. If you have a Spring Boot application that uses Tomcat as an embedded server (which is @@ -36,7 +36,7 @@ The registered WireMock server is reset after each test class, however, if you n If you use `@AutoConfigureWireMock`, it registers WireMock JSON stubs from the file system or classpath (by default, from `file:src/test/resources/mappings`). You can -customize the locations by using the `stubs` attribute in the annotation, which can be an +customize the locations byusing the `stubs` attribute in the annotation, which can be an Ant-style resource pattern or a directory. In the case of a directory, `**/*.json` is appended. The following code shows an example: diff --git a/docs/src/main/asciidoc/howto.adoc b/docs/src/main/asciidoc/howto.adoc index 0737527436..d374a78ebb 100644 --- a/docs/src/main/asciidoc/howto.adoc +++ b/docs/src/main/asciidoc/howto.adoc @@ -257,7 +257,7 @@ with your local changes. Assume that we have a producer with coordinates of `com.example:server` and three consumers: `client1`, `client2`, and `client3`. Then, in the repository with common contracts, you could have the following setup (which you can check out -https://github.com/spring-cloud/spring-cloud-contract/tree/{samples_branch}/samples/standalone/contracts[here]). +https://github.com/spring-cloud/spring-cloud-contract/tree/{branch}/samples/standalone/contracts[here]). The following listing shows such a structure: ====