From 7dbfe4a6b83ef2eeb37bbc5880ab7d7f20a790ce Mon Sep 17 00:00:00 2001
From: buildmaster <buildmaster@springframework.org>
Date: Tue, 6 Nov 2018 13:18:46 +0000
Subject: [PATCH] Sync docs from master to gh-pages

---
 multi/multi__spring_cloud_contract_wiremock.html | 2 +-
 single/spring-cloud-contract.html                | 2 +-
 spring-cloud-contract.xml                        | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/multi/multi__spring_cloud_contract_wiremock.html b/multi/multi__spring_cloud_contract_wiremock.html
index 44c3923880..88baca327c 100644
--- a/multi/multi__spring_cloud_contract_wiremock.html
+++ b/multi/multi__spring_cloud_contract_wiremock.html
@@ -33,7 +33,7 @@ your test. The following code shows an example:</p><pre class="programlisting"><
 server port can be bound in the test application context with the "wiremock.server.port"
 property. Using <code class="literal">@AutoConfigureWireMock</code> adds a bean of type <code class="literal">WiremockConfiguration</code> to
 your test application context, where it will be cached in between methods and classes
-having the same context, the same as for Spring integration tests.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="_registering_stubs_automatically" href="#_registering_stubs_automatically"></a>11.1&nbsp;Registering Stubs Automatically</h2></div></div></div><p>If you use <code class="literal">@AutoConfigureWireMock</code>, it registers WireMock JSON stubs from the file
+having the same context, the same as for Spring integration tests. Also you can inject a bean of type <code class="literal">WireMockServer</code> into your test.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="_registering_stubs_automatically" href="#_registering_stubs_automatically"></a>11.1&nbsp;Registering Stubs Automatically</h2></div></div></div><p>If you use <code class="literal">@AutoConfigureWireMock</code>, it registers WireMock JSON stubs from the file
 system or classpath (by default, from <code class="literal">file:src/test/resources/mappings</code>). You can
 customize the locations using the <code class="literal">stubs</code> attribute in the annotation, which can be an
 Ant-style resource pattern or a directory. In the case of a directory, <code class="literal"><span class="strong"><strong>*/</strong></span>.json</code> is
diff --git a/single/spring-cloud-contract.html b/single/spring-cloud-contract.html
index 221128beb1..ac154bb64f 100644
--- a/single/spring-cloud-contract.html
+++ b/single/spring-cloud-contract.html
@@ -5922,7 +5922,7 @@ your test. The following code shows an example:</p><pre class="programlisting"><
 server port can be bound in the test application context with the "wiremock.server.port"
 property. Using <code class="literal">@AutoConfigureWireMock</code> adds a bean of type <code class="literal">WiremockConfiguration</code> to
 your test application context, where it will be cached in between methods and classes
-having the same context, the same as for Spring integration tests.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="_registering_stubs_automatically" href="#_registering_stubs_automatically"></a>11.1&nbsp;Registering Stubs Automatically</h2></div></div></div><p>If you use <code class="literal">@AutoConfigureWireMock</code>, it registers WireMock JSON stubs from the file
+having the same context, the same as for Spring integration tests. Also you can inject a bean of type <code class="literal">WireMockServer</code> into your test.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="_registering_stubs_automatically" href="#_registering_stubs_automatically"></a>11.1&nbsp;Registering Stubs Automatically</h2></div></div></div><p>If you use <code class="literal">@AutoConfigureWireMock</code>, it registers WireMock JSON stubs from the file
 system or classpath (by default, from <code class="literal">file:src/test/resources/mappings</code>). You can
 customize the locations using the <code class="literal">stubs</code> attribute in the annotation, which can be an
 Ant-style resource pattern or a directory. In the case of a directory, <code class="literal"><span class="strong"><strong>*/</strong></span>.json</code> is
diff --git a/spring-cloud-contract.xml b/spring-cloud-contract.xml
index 4c9608e8f9..06946d5ead 100644
--- a/spring-cloud-contract.xml
+++ b/spring-cloud-contract.xml
@@ -9418,7 +9418,7 @@ public class WiremockForDocsTests {
 server port can be bound in the test application context with the "wiremock.server.port"
 property. Using <literal>@AutoConfigureWireMock</literal> adds a bean of type <literal>WiremockConfiguration</literal> to
 your test application context, where it will be cached in between methods and classes
-having the same context, the same as for Spring integration tests.</simpara>
+having the same context, the same as for Spring integration tests. Also you can inject a bean of type <literal>WireMockServer</literal> into your test.</simpara>
 <section xml:id="_registering_stubs_automatically">
 <title>Registering Stubs Automatically</title>
 <simpara>If you use <literal>@AutoConfigureWireMock</literal>, it registers WireMock JSON stubs from the file