From 4762336f3e3fccc2c772885b3ef1a7528f28723a Mon Sep 17 00:00:00 2001 From: buildmaster Date: Tue, 3 Apr 2018 10:17:03 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- multi/multi__spring_cloud_contract_faq.html | 4 ++-- multi/multi__using_the_pluggable_architecture.html | 4 ++-- single/spring-cloud-contract.html | 8 ++++---- spring-cloud-contract.xml | 4 ++-- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/multi/multi__spring_cloud_contract_faq.html b/multi/multi__spring_cloud_contract_faq.html index bb0999e170..0afd4104f6 100644 --- a/multi/multi__spring_cloud_contract_faq.html +++ b/multi/multi__spring_cloud_contract_faq.html @@ -519,7 +519,7 @@ setup can be found pact:// protocol. It’s enough to pass the URL to the -Pact Broker.

Maven.  +Pact Broker. An example of such setup can be found here.

Maven.  

<plugin>
     <groupId>org.springframework.cloud</groupId>
     <artifactId>spring-cloud-contract-maven-plugin</artifactId>
@@ -582,7 +582,7 @@ contracts {
 (for every single consumer define the expectations) but you’d prefer
 to do Producer Contracts (the producer provides the contracts and
 publishes stubs), it’s enough to use Spring Cloud Contract with
-Stub Runner option.
First, remember to add Stub Runner and Spring Cloud Contract Pact module
+Stub Runner option. An example of such setup can be found here.
First, remember to add Stub Runner and Spring Cloud Contract Pact module
 as test dependencies.
Maven. 
 
<dependencyManagement>
     <dependencies>
diff --git a/multi/multi__using_the_pluggable_architecture.html b/multi/multi__using_the_pluggable_architecture.html
index ebcf1a4ad4..c61460c26b 100644
--- a/multi/multi__using_the_pluggable_architecture.html
+++ b/multi/multi__using_the_pluggable_architecture.html
@@ -421,7 +421,7 @@ to clone the repository and use it as a source of contracts
 to generate tests or stubs.
Either via environment variables, system properties, properties set
 inside the plugin or contracts repository configuration you can
 tweak the downloader’s behaviour. Below you can find the list of
-properties
Table 10.1. SCM Stub Downloader properties
Type of a property
Name of the property
Description
* git.branch (plugin prop)
+properties
Table 10.1. SCM Stub Downloader properties
Type of a property
Name of the property
Description
* git.branch (plugin prop)
 
* stubrunner.properties.git.branch (system prop)
 
* STUBRUNNER_PROPERTIES_GIT_BRANCH (env prop)
master
Which branch to checkout
* git.username (plugin prop)
 
* stubrunner.properties.git.username (system prop)
@@ -437,7 +437,7 @@ to fetch the Pact contract definitions from the Pact Broker.
 Whatever is set after pact:// will be parsed as the Pact Broker URL.
Either via environment variables, system properties, properties set
 inside the plugin or contracts repository configuration you can
 tweak the downloader’s behaviour. Below you can find the list of
-properties
Table 10.2. SCM Stub Downloader properties
Type of a property
Name of the property
Description
* pactbroker.host (plugin prop)
+properties
Table 10.2. SCM Stub Downloader properties
Type of a property
Name of the property
Description
* pactbroker.host (plugin prop)
 
* stubrunner.properties.pactbroker.host (system prop)
 
* STUBRUNNER_PROPERTIES_PACTBROKER_HOST (env prop)
Host from URL passed to repositoryRoot
What is the URL of Pact Broker
* pactbroker.port (plugin prop)
 
* stubrunner.properties.pactbroker.port (system prop)
diff --git a/single/spring-cloud-contract.html b/single/spring-cloud-contract.html
index 37b4d63037..28dfe138cb 100644
--- a/single/spring-cloud-contract.html
+++ b/single/spring-cloud-contract.html
@@ -1300,7 +1300,7 @@ setup can be found pact:// protocol. It’s enough to pass the URL to the
-Pact Broker.
Maven. 
+Pact Broker. An example of such setup can be found here.
Maven. 
 
<plugin>
     <groupId>org.springframework.cloud</groupId>
     <artifactId>spring-cloud-contract-maven-plugin</artifactId>
@@ -1363,7 +1363,7 @@ contracts {
 (for every single consumer define the expectations) but you’d prefer
 to do Producer Contracts (the producer provides the contracts and
 publishes stubs), it’s enough to use Spring Cloud Contract with
-Stub Runner option.
First, remember to add Stub Runner and Spring Cloud Contract Pact module
+Stub Runner option. An example of such setup can be found here.
First, remember to add Stub Runner and Spring Cloud Contract Pact module
 as test dependencies.
Maven. 
 
<dependencyManagement>
     <dependencies>
@@ -5817,7 +5817,7 @@ to clone the repository and use it as a source of contracts
 to generate tests or stubs.
Either via environment variables, system properties, properties set
 inside the plugin or contracts repository configuration you can
 tweak the downloader’s behaviour. Below you can find the list of
-properties
Table 10.1. SCM Stub Downloader properties
Type of a property
Name of the property
Description
* git.branch (plugin prop)
+properties
Table 10.1. SCM Stub Downloader properties
Type of a property
Name of the property
Description
* git.branch (plugin prop)
 
* stubrunner.properties.git.branch (system prop)
 
* STUBRUNNER_PROPERTIES_GIT_BRANCH (env prop)
master
Which branch to checkout
* git.username (plugin prop)
 
* stubrunner.properties.git.username (system prop)
@@ -5833,7 +5833,7 @@ to fetch the Pact contract definitions from the Pact Broker.
 Whatever is set after pact:// will be parsed as the Pact Broker URL.
Either via environment variables, system properties, properties set
 inside the plugin or contracts repository configuration you can
 tweak the downloader’s behaviour. Below you can find the list of
-properties
Table 10.2. SCM Stub Downloader properties
Type of a property
Name of the property
Description
* pactbroker.host (plugin prop)
+properties
Table 10.2. SCM Stub Downloader properties
Type of a property
Name of the property
Description
* pactbroker.host (plugin prop)
 
* stubrunner.properties.pactbroker.host (system prop)
 
* STUBRUNNER_PROPERTIES_PACTBROKER_HOST (env prop)
Host from URL passed to repositoryRoot
What is the URL of Pact Broker
* pactbroker.port (plugin prop)
 
* stubrunner.properties.pactbroker.port (system prop)
diff --git a/spring-cloud-contract.xml b/spring-cloud-contract.xml
index 97b713d797..30bd0514a9 100644
--- a/spring-cloud-contract.xml
+++ b/spring-cloud-contract.xml
@@ -2166,7 +2166,7 @@ setup can be found here.
 
 Maven
 
@@ -2253,7 +2253,7 @@ contracts {
 (for every single consumer define the expectations) but you’d prefer
 to do Producer Contracts (the producer provides the contracts and
 publishes stubs), it’s enough to use Spring Cloud Contract with
-Stub Runner option.
+Stub Runner option. An example of such setup can be found here.
 First, remember to add Stub Runner and Spring Cloud Contract Pact module
 as test dependencies.