From ee020bc43915d412baa840d72561a1a0cee59f94 Mon Sep 17 00:00:00 2001
From: buildmaster
Date: Wed, 31 Jan 2018 22:39:38 +0000
Subject: [PATCH] Sync docs from 1.2.x to gh-pages
---
1.2.x/multi/multi__contract_dsl.html | 10 +++++-----
1.2.x/single/spring-cloud-contract.html | 10 +++++-----
.../spring-cloud-contract-maven-plugin/checkstyle.html | 6 +++---
1.2.x/spring-cloud-contract-maven-plugin/complex.html | 6 +++---
1.2.x/spring-cloud-contract-maven-plugin/configs.html | 6 +++---
.../convert-mojo.html | 6 +++---
.../generateStubs-mojo.html | 6 +++---
.../generateTests-mojo.html | 6 +++---
.../spring-cloud-contract-maven-plugin/help-mojo.html | 6 +++---
1.2.x/spring-cloud-contract-maven-plugin/index.html | 6 +++---
.../integration.html | 6 +++---
.../issue-tracking.html | 6 +++---
1.2.x/spring-cloud-contract-maven-plugin/junit.html | 6 +++---
1.2.x/spring-cloud-contract-maven-plugin/license.html | 6 +++---
.../plugin-info.html | 6 +++---
.../plugin-management.html | 6 +++---
1.2.x/spring-cloud-contract-maven-plugin/plugins.html | 6 +++---
.../project-info.html | 6 +++---
.../project-reports.html | 6 +++---
.../project-summary.html | 6 +++---
1.2.x/spring-cloud-contract-maven-plugin/run-mojo.html | 6 +++---
1.2.x/spring-cloud-contract-maven-plugin/sitemap.html | 6 +++---
.../source-repository.html | 6 +++---
1.2.x/spring-cloud-contract-maven-plugin/spock.html | 6 +++---
.../spring-cloud-contract-maven-plugin/team-list.html | 6 +++---
1.2.x/spring-cloud-contract-maven-plugin/usage.html | 6 +++---
1.2.x/spring-cloud-contract.xml | 10 +++++-----
27 files changed, 87 insertions(+), 87 deletions(-)
diff --git a/1.2.x/multi/multi__contract_dsl.html b/1.2.x/multi/multi__contract_dsl.html
index fe4bac84d6..c4cb740350 100644
--- a/1.2.x/multi/multi__contract_dsl.html
+++ b/1.2.x/multi/multi__contract_dsl.html
@@ -1002,11 +1002,11 @@ Quite a few users are used to having a separation between the body and setting t
dynamic parts of a contract.
You can use two separate sections:
stubMatchers, which lets you define the dynamic values that should end up in a stub.
You can set it in the request or inputMessage part of your contract.
testMatchers, which is present in the response or outputMessage side of the
contract.
Currently, Spring Cloud Contract Verifier supports only JSON Path-based matchers with the
-following matching possibilities:
Groovy DSL
For stubMatchers:
byEquality(): The value taken from the response via the provided JSON Path must be
-equal to the value provided in the contract.
byRegex(…): The value taken from the response via the provided JSON Path must
-match the regex.
byDate(): The value taken from the response via the provided JSON Path must
-match the regex for an ISO Date value.
byTimestamp(): The value taken from the response via the provided JSON Path must
-match the regex for an ISO DateTime value.
byTime(): The value taken from the response via the provided JSON Path must
+following matching possibilities:
Groovy DSL
For stubMatchers:
byEquality(): The value taken from the request via the provided JSON Path must be
+equal to the value provided in the contract.
byRegex(…): The value taken from the request via the provided JSON Path must
+match the regex.
byDate(): The value taken from the request via the provided JSON Path must
+match the regex for an ISO Date value.
byTimestamp(): The value taken from the request via the provided JSON Path must
+match the regex for an ISO DateTime value.
byTime(): The value taken from the request via the provided JSON Path must
match the regex for an ISO Time value.
For testMatchers:
byEquality(): The value taken from the response via the provided JSON Path must be
equal to the provided value in the contract.
byRegex(…): The value taken from the response via the provided JSON Path must
match the regex.
byDate(): The value taken from the response via the provided JSON Path must match
diff --git a/1.2.x/single/spring-cloud-contract.html b/1.2.x/single/spring-cloud-contract.html
index e51569e410..f0ec6f32a9 100644
--- a/1.2.x/single/spring-cloud-contract.html
+++ b/1.2.x/single/spring-cloud-contract.html
@@ -3815,11 +3815,11 @@ Quite a few users are used to having a separation between the body and setting t
dynamic parts of a contract.
You can use two separate sections:
stubMatchers, which lets you define the dynamic values that should end up in a stub.
You can set it in the request or inputMessage part of your contract.
testMatchers, which is present in the response or outputMessage side of the
contract.
Currently, Spring Cloud Contract Verifier supports only JSON Path-based matchers with the
-following matching possibilities:
Groovy DSL
For stubMatchers:
byEquality(): The value taken from the response via the provided JSON Path must be
-equal to the value provided in the contract.
byRegex(…): The value taken from the response via the provided JSON Path must
-match the regex.
byDate(): The value taken from the response via the provided JSON Path must
-match the regex for an ISO Date value.
byTimestamp(): The value taken from the response via the provided JSON Path must
-match the regex for an ISO DateTime value.
byTime(): The value taken from the response via the provided JSON Path must
+following matching possibilities:
Groovy DSL
For stubMatchers:
byEquality(): The value taken from the request via the provided JSON Path must be
+equal to the value provided in the contract.
byRegex(…): The value taken from the request via the provided JSON Path must
+match the regex.
byDate(): The value taken from the request via the provided JSON Path must
+match the regex for an ISO Date value.
byTimestamp(): The value taken from the request via the provided JSON Path must
+match the regex for an ISO DateTime value.
byTime(): The value taken from the request via the provided JSON Path must
match the regex for an ISO Time value.
For testMatchers:
byEquality(): The value taken from the response via the provided JSON Path must be
equal to the provided value in the contract.
byRegex(…): The value taken from the response via the provided JSON Path must
match the regex.
byDate(): The value taken from the response via the provided JSON Path must match
diff --git a/1.2.x/spring-cloud-contract-maven-plugin/checkstyle.html b/1.2.x/spring-cloud-contract-maven-plugin/checkstyle.html
index de539c0955..12dc76923b 100644
--- a/1.2.x/spring-cloud-contract-maven-plugin/checkstyle.html
+++ b/1.2.x/spring-cloud-contract-maven-plugin/checkstyle.html
@@ -1,13 +1,13 @@
-
+
Spring Cloud Contract Maven Plugin – Checkstyle Results
@@ -146,7 +146,7 @@
Version: 1.2.3.BUILD-SNAPSHOT
diff --git a/1.2.x/spring-cloud-contract.xml b/1.2.x/spring-cloud-contract.xml
index f94465a920..4e9c614f57 100644
--- a/1.2.x/spring-cloud-contract.xml
+++ b/1.2.x/spring-cloud-contract.xml
@@ -6299,23 +6299,23 @@ following matching possibilities:
For stubMatchers:
-byEquality(): The value taken from the response via the provided JSON Path must be
+byEquality(): The value taken from the request via the provided JSON Path must be
equal to the value provided in the contract.
-byRegex(…): The value taken from the response via the provided JSON Path must
+byRegex(…): The value taken from the request via the provided JSON Path must
match the regex.
-byDate(): The value taken from the response via the provided JSON Path must
+byDate(): The value taken from the request via the provided JSON Path must
match the regex for an ISO Date value.
-byTimestamp(): The value taken from the response via the provided JSON Path must
+byTimestamp(): The value taken from the request via the provided JSON Path must
match the regex for an ISO DateTime value.
-byTime(): The value taken from the response via the provided JSON Path must
+byTime(): The value taken from the request via the provided JSON Path must
match the regex for an ISO Time value.