From 3b2686bf7be43e3e75283c8ab7fdf1609c61ee9b Mon Sep 17 00:00:00 2001
From: buildmaster <buildmaster@springframework.org>
Date: Tue, 9 Jun 2020 14:34:42 +0000
Subject: [PATCH] Sync docs from master to gh-pages

---
 reference/html/spring-cloud-contract.html     | 15028 +-----------
 .../htmlsingle/spring-cloud-contract.html     | 20044 ++++++++++++++++
 reference/pdf/spring-cloud-contract.pdf       |     4 +-
 .../apidocs/allclasses-frame.html             |     2 +-
 .../apidocs/allclasses-noframe.html           |     2 +-
 .../apidocs/constant-values.html              |     2 +-
 .../apidocs/deprecated-list.html              |     2 +-
 .../apidocs/help-doc.html                     |     2 +-
 .../apidocs/index-all.html                    |     2 +-
 .../apidocs/index.html                        |     2 +-
 .../maven/verifier/BaseClassMapping.html      |     2 +-
 .../contract/maven/verifier/ConvertMojo.html  |     2 +-
 .../maven/verifier/GenerateStubsMojo.html     |     2 +-
 .../maven/verifier/GenerateTestsMojo.html     |     2 +-
 .../contract/maven/verifier/HelpMojo.html     |     2 +-
 .../maven/verifier/PushStubsToScmMojo.html    |     2 +-
 .../contract/maven/verifier/RunMojo.html      |     2 +-
 .../verifier/class-use/BaseClassMapping.html  |     2 +-
 .../maven/verifier/class-use/ConvertMojo.html |     2 +-
 .../verifier/class-use/GenerateStubsMojo.html |     2 +-
 .../verifier/class-use/GenerateTestsMojo.html |     2 +-
 .../maven/verifier/class-use/HelpMojo.html    |     2 +-
 .../class-use/PushStubsToScmMojo.html         |     2 +-
 .../maven/verifier/class-use/RunMojo.html     |     2 +-
 .../maven/verifier/package-frame.html         |     2 +-
 .../maven/verifier/package-summary.html       |     2 +-
 .../contract/maven/verifier/package-tree.html |     2 +-
 .../contract/maven/verifier/package-use.html  |     2 +-
 .../AetherStubDownloaderFactory.html          |     2 +-
 .../verifier/stubrunner/LocalStubRunner.html  |     2 +-
 .../verifier/stubrunner/RemoteStubRunner.html |     2 +-
 .../AetherStubDownloaderFactory.html          |     2 +-
 .../stubrunner/class-use/LocalStubRunner.html |     2 +-
 .../class-use/RemoteStubRunner.html           |     2 +-
 .../verifier/stubrunner/package-frame.html    |     2 +-
 .../verifier/stubrunner/package-summary.html  |     2 +-
 .../verifier/stubrunner/package-tree.html     |     2 +-
 .../verifier/stubrunner/package-use.html      |     2 +-
 .../apidocs/overview-frame.html               |     2 +-
 .../apidocs/overview-summary.html             |     2 +-
 .../apidocs/overview-tree.html                |     2 +-
 41 files changed, 20145 insertions(+), 15007 deletions(-)
 create mode 100644 reference/htmlsingle/spring-cloud-contract.html

diff --git a/reference/html/spring-cloud-contract.html b/reference/html/spring-cloud-contract.html
index 8a5b0421d5..2b486b170d 100644
--- a/reference/html/spring-cloud-contract.html
+++ b/reference/html/spring-cloud-contract.html
@@ -4,8 +4,9 @@
 <meta charset="UTF-8">
 <!--[if IE]><meta http-equiv="X-UA-Compatible" content="IE=edge"><![endif]-->
 <meta name="viewport" content="width=device-width, initial-scale=1.0">
-<meta name="generator" content="Asciidoctor 1.5.7.1">
-<title>Spring Cloud Contract</title>
+<meta name="generator" content="Asciidoctor 1.5.8">
+<meta name="author" content="Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant">
+<title>Spring Cloud Contract Reference Documentation</title>
 <link rel="stylesheet" href="css/spring.css">
 <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css">
 
@@ -86,15023 +87,116 @@ function createSwitchItem(block, blockSwitch) {
 	return {'item': item, 'content': content};
 }
 
+function globalSwitch() {
+	$('.switch--item').each(function() {
+		$(this).off('click');
+		$(this).on('click', function() {
+			selectedText = $(this).text()
+			selectedIndex = $(this).index()
+			$(".switch--item").filter(function() { return ($(this).text() === selectedText) }).each(function() {
+				$(this).addClass('selected');
+				$(this).siblings().removeClass('selected');
+				selectedContent = $(this).parent().siblings(".content").eq(selectedIndex)
+				selectedContent.removeClass('hidden');
+				selectedContent.siblings().addClass('hidden');
+			});
+		});
+	});
+}
+
 $(addBlockSwitches);
+$(globalSwitch);
+
 </script>
 
 </head>
-<body class="book toc2 toc-left">
+<body id="spring-cloud-contract-reference-documentation" class="book">
 <div id="header">
-<h1>Spring Cloud Contract</h1>
-<div id="toc" class="toc2">
-<div id="toctitle">Table of Contents</div>
-<ul class="sectlevel1">
-<li><a href="#_spring_cloud_contract">1. Spring Cloud Contract</a></li>
-<li><a href="#_spring_cloud_contract_verifier_introduction">2. Spring Cloud Contract Verifier Introduction</a>
-<ul class="sectlevel2">
-<li><a href="#_history">2.1. History</a></li>
-<li><a href="#_why_a_contract_verifier">2.2. Why a Contract Verifier?</a>
-<ul class="sectlevel3">
-<li><a href="#_testing_issues">2.2.1. Testing issues</a></li>
-</ul>
-</li>
-<li><a href="#_purposes">2.3. Purposes</a></li>
-<li><a href="#_how_it_works">2.4. How It Works</a>
-<ul class="sectlevel3">
-<li><a href="#spring-cloud-contract-verifier-intro-three-second-tour">2.4.1. A Three-second Tour</a></li>
-<li><a href="#spring-cloud-contract-verifier-intro-three-minute-tour">2.4.2. A Three-minute Tour</a></li>
-<li><a href="#_defining_the_contract">2.4.3. Defining the Contract</a></li>
-<li><a href="#_client_side">2.4.4. Client Side</a></li>
-<li><a href="#_server_side">2.4.5. Server Side</a></li>
-</ul>
-</li>
-<li><a href="#_step_by_step_guide_to_consumer_driven_contracts_cdc">2.5. Step-by-step Guide to Consumer Driven Contracts (CDC)</a>
-<ul class="sectlevel3">
-<li><a href="#_technical_note">2.5.1. Technical note</a></li>
-<li><a href="#_consumer_side_loan_issuance">2.5.2. Consumer side (Loan Issuance)</a></li>
-<li><a href="#_producer_side_fraud_detection_server">2.5.3. Producer side (Fraud Detection server)</a></li>
-<li><a href="#_consumer_side_loan_issuance_final_step">2.5.4. Consumer Side (Loan Issuance) Final Step</a></li>
-</ul>
-</li>
-<li><a href="#_dependencies">2.6. Dependencies</a></li>
-<li><a href="#_additional_links">2.7. Additional Links</a>
-<ul class="sectlevel3">
-<li><a href="#_spring_cloud_contract_video">2.7.1. Spring Cloud Contract video</a></li>
-<li><a href="#_readings">2.7.2. Readings</a></li>
-</ul>
-</li>
-<li><a href="#_samples">2.8. Samples</a></li>
-</ul>
-</li>
-<li><a href="#_spring_cloud_contract_faq">3. Spring Cloud Contract FAQ</a>
-<ul class="sectlevel2">
-<li><a href="#_why_use_spring_cloud_contract_verifier_and_not_x">3.1. Why use Spring Cloud Contract Verifier and not X ?</a></li>
-<li><a href="#_i_dont_want_to_write_a_contract_in_groovy">3.2. I don&#8217;t want to write a contract in Groovy!</a></li>
-<li><a href="#_what_is_this_valueconsumer_producer">3.3. What is this value(consumer(), producer()) ?</a></li>
-<li><a href="#_how_to_do_stubs_versioning">3.4. How to do Stubs versioning?</a>
-<ul class="sectlevel3">
-<li><a href="#_api_versioning">3.4.1. API Versioning</a></li>
-<li><a href="#_jar_versioning">3.4.2. JAR versioning</a></li>
-<li><a href="#_dev_or_prod_stubs">3.4.3. Dev or prod stubs</a></li>
-</ul>
-</li>
-<li><a href="#_common_repo_with_contracts">3.5. Common repo with contracts</a>
-<ul class="sectlevel3">
-<li><a href="#_repo_structure">3.5.1. Repo structure</a></li>
-<li><a href="#_workflow">3.5.2. Workflow</a></li>
-<li><a href="#_consumer">3.5.3. Consumer</a></li>
-<li><a href="#_producer">3.5.4. Producer</a></li>
-<li><a href="#_how_can_i_define_messaging_contracts_per_topic_not_per_producer">3.5.5. How can I define messaging contracts per topic not per producer?</a></li>
-</ul>
-</li>
-<li><a href="#_do_i_need_a_binary_storage_cant_i_use_git">3.6. Do I need a Binary Storage? Can&#8217;t I use Git?</a>
-<ul class="sectlevel3">
-<li><a href="#_protocol_convention">3.6.1. Protocol convention</a></li>
-<li><a href="#_producer_2">3.6.2. Producer</a></li>
-<li><a href="#_producer_with_contracts_stored_locally">3.6.3. Producer with contracts stored locally</a></li>
-<li><a href="#_consumer_2">3.6.4. Consumer</a></li>
-</ul>
-</li>
-<li><a href="#_can_i_use_the_pact_broker">3.7. Can I use the Pact Broker?</a>
-<ul class="sectlevel3">
-<li><a href="#_pact_consumer">3.7.1. Pact Consumer</a></li>
-<li><a href="#_producer_3">3.7.2. Producer</a></li>
-<li><a href="#_pact_consumer_producer_contract_approach">3.7.3. Pact Consumer (Producer Contract approach)</a></li>
-</ul>
-</li>
-<li><a href="#_how_can_i_debug_the_requestresponse_being_sent_by_the_generated_tests_client">3.8. How can I debug the request/response being sent by the generated tests client?</a>
-<ul class="sectlevel3">
-<li><a href="#_how_can_i_debug_the_mappingrequestresponse_being_sent_by_wiremock">3.8.1. How can I debug the mapping/request/response being sent by WireMock?</a></li>
-<li><a href="#_how_can_i_see_what_got_registered_in_the_http_server_stub">3.8.2. How can I see what got registered in the HTTP server stub?</a></li>
-<li><a href="#_can_i_reference_text_from_file">3.8.3. Can I reference text from file?</a></li>
-</ul>
-</li>
-</ul>
-</li>
-<li><a href="#_spring_cloud_contract_verifier_setup">4. Spring Cloud Contract Verifier Setup</a>
-<ul class="sectlevel2">
-<li><a href="#gradle-project">4.1. Gradle Project</a>
-<ul class="sectlevel3">
-<li><a href="#gradle-prerequisites">4.1.1. Prerequisites</a></li>
-<li><a href="#gradle-add-gradle-plugin">4.1.2. Add Gradle Plugin with Dependencies</a></li>
-<li><a href="#gradle-and-rest-assured">4.1.3. Gradle and Rest Assured 2.0</a></li>
-<li><a href="#gradle-snapshot-versions">4.1.4. Snapshot Versions for Gradle</a></li>
-<li><a href="#gradle-add-stubs">4.1.5. Add stubs</a></li>
-<li><a href="#gradle-run-plugin">4.1.6. Run the Plugin</a></li>
-<li><a href="#gradle-default-setup">4.1.7. Default Setup</a></li>
-<li><a href="#gradle-configure-plugin">4.1.8. Configure Plugin</a></li>
-<li><a href="#gradle-configuration-options">4.1.9. Configuration Options</a></li>
-<li><a href="#gradle-single-base-class">4.1.10. Single Base Class for All Tests</a></li>
-<li><a href="#gradle-different-base-classes">4.1.11. Different Base Classes for Contracts</a></li>
-<li><a href="#gradle-invoking-generated-tests">4.1.12. Invoking Generated Tests</a></li>
-<li><a href="#gradle-pushing-stubs-to-scm">4.1.13. Pushing stubs to SCM</a></li>
-<li><a href="#gradle-consumer">4.1.14. Spring Cloud Contract Verifier on the Consumer Side</a></li>
-</ul>
-</li>
-<li><a href="#maven-project">4.2. Maven Project</a>
-<ul class="sectlevel3">
-<li><a href="#maven-add-plugin">4.2.1. Add maven plugin</a></li>
-<li><a href="#maven-rest-assured">4.2.2. Maven and Rest Assured 2.0</a></li>
-<li><a href="#maven-snapshot-versions">4.2.3. Snapshot versions for Maven</a></li>
-<li><a href="#maven-add-stubs">4.2.4. Add stubs</a></li>
-<li><a href="#maven-run-plugin">4.2.5. Run plugin</a></li>
-<li><a href="#maven-configure-plugin">4.2.6. Configure plugin</a></li>
-<li><a href="#maven-configuration-options">4.2.7. Configuration Options</a></li>
-<li><a href="#maven-single-base">4.2.8. Single Base Class for All Tests</a></li>
-<li><a href="#maven-different-base">4.2.9. Different base classes for contracts</a></li>
-<li><a href="#maven-invoking-generated-tests">4.2.10. Invoking generated tests</a></li>
-<li><a href="#maven-pushing-stubs-to-scm">4.2.11. Pushing stubs to SCM</a></li>
-<li><a href="#maven-sts">4.2.12. Maven Plugin and STS</a></li>
-<li><a href="#_maven_plugin_with_spock_tests">4.2.13. Maven Plugin with Spock Tests</a></li>
-</ul>
-</li>
-<li><a href="#_stubs_and_transitive_dependencies">4.3. Stubs and Transitive Dependencies</a></li>
-<li><a href="#_scenarios">4.4. Scenarios</a></li>
-<li><a href="#docker-project">4.5. Docker Project</a>
-<ul class="sectlevel3">
-<li><a href="#_short_intro_to_maven_jars_and_binary_storage">4.5.1. Short intro to Maven, JARs and Binary storage</a></li>
-<li><a href="#_how_it_works_2">4.5.2. How it works</a></li>
-<li><a href="#_example_of_usage">4.5.3. Example of usage</a></li>
-<li><a href="#docker-server-side">4.5.4. Server side (nodejs)</a></li>
-</ul>
-</li>
-</ul>
-</li>
-<li><a href="#_spring_cloud_contract_verifier_messaging">5. Spring Cloud Contract Verifier Messaging</a>
-<ul class="sectlevel2">
-<li><a href="#_integrations">5.1. Integrations</a></li>
-<li><a href="#_manual_integration_testing">5.2. Manual Integration Testing</a></li>
-<li><a href="#_publisher_side_test_generation">5.3. Publisher-Side Test Generation</a>
-<ul class="sectlevel3">
-<li><a href="#_scenario_1_no_input_message">5.3.1. Scenario 1: No Input Message</a></li>
-<li><a href="#_scenario_2_output_triggered_by_input">5.3.2. Scenario 2: Output Triggered by Input</a></li>
-<li><a href="#_scenario_3_no_output_message">5.3.3. Scenario 3: No Output Message</a></li>
-</ul>
-</li>
-<li><a href="#_consumer_stub_generation">5.4. Consumer Stub Generation</a></li>
-</ul>
-</li>
-<li><a href="#_spring_cloud_contract_stub_runner">6. Spring Cloud Contract Stub Runner</a>
-<ul class="sectlevel2">
-<li><a href="#_snapshot_versions">6.1. Snapshot versions</a></li>
-<li><a href="#publishing-stubs-as-jars">6.2. Publishing Stubs as JARs</a></li>
-<li><a href="#_stub_runner_core">6.3. Stub Runner Core</a>
-<ul class="sectlevel3">
-<li><a href="#_retrieving_stubs">6.3.1. Retrieving stubs</a></li>
-<li><a href="#_running_stubs">6.3.2. Running stubs</a></li>
-</ul>
-</li>
-<li><a href="#_stub_runner_junit_rule_and_stub_runner_junit5_extension">6.4. Stub Runner JUnit Rule and Stub Runner JUnit5 Extension</a>
-<ul class="sectlevel3">
-<li><a href="#_maven_settings">6.4.1. Maven settings</a></li>
-<li><a href="#_providing_fixed_ports">6.4.2. Providing fixed ports</a></li>
-<li><a href="#_fluent_api">6.4.3. Fluent API</a></li>
-<li><a href="#_stub_runner_with_spring">6.4.4. Stub Runner with Spring</a></li>
-</ul>
-</li>
-<li><a href="#_stub_runner_spring_cloud">6.5. Stub Runner Spring Cloud</a>
-<ul class="sectlevel3">
-<li><a href="#_stubbing_service_discovery">6.5.1. Stubbing Service Discovery</a></li>
-<li><a href="#_additional_configuration">6.5.2. Additional Configuration</a></li>
-</ul>
-</li>
-<li><a href="#_stub_runner_boot_application">6.6. Stub Runner Boot Application</a>
-<ul class="sectlevel3">
-<li><a href="#_how_to_use_it">6.6.1. How to use it?</a></li>
-<li><a href="#_endpoints">6.6.2. Endpoints</a></li>
-<li><a href="#_example">6.6.3. Example</a></li>
-<li><a href="#_stub_runner_boot_with_service_discovery">6.6.4. Stub Runner Boot with Service Discovery</a></li>
-</ul>
-</li>
-<li><a href="#_stubs_per_consumer">6.7. Stubs Per Consumer</a></li>
-<li><a href="#_common">6.8. Common</a>
-<ul class="sectlevel3">
-<li><a href="#common-properties-junit-spring">6.8.1. Common Properties for JUnit and Spring</a></li>
-<li><a href="#stub-runner-stub-ids">6.8.2. Stub Runner Stubs IDs</a></li>
-</ul>
-</li>
-<li><a href="#stubrunner-docker">6.9. Stub Runner Docker</a>
-<ul class="sectlevel3">
-<li><a href="#_how_to_use_it_2">6.9.1. How to use it</a></li>
-<li><a href="#_example_of_client_side_usage_in_a_non_jvm_project">6.9.2. Example of client side usage in a non JVM project</a></li>
-</ul>
-</li>
-</ul>
-</li>
-<li><a href="#stub-runner-for-messaging">7. Stub Runner for Messaging</a>
-<ul class="sectlevel2">
-<li><a href="#_stub_triggering">7.1. Stub triggering</a>
-<ul class="sectlevel3">
-<li><a href="#trigger-label">7.1.1. Trigger by Label</a></li>
-<li><a href="#trigger-group-artifact-ids">7.1.2. Trigger by Group and Artifact Ids</a></li>
-<li><a href="#trigger-artifact-ids">7.1.3. Trigger by Artifact Ids</a></li>
-<li><a href="#trigger-all-messages">7.1.4. Trigger All Messages</a></li>
-</ul>
-</li>
-<li><a href="#_stub_runner_camel">7.2. Stub Runner Camel</a>
-<ul class="sectlevel3">
-<li><a href="#_adding_it_to_the_project">7.2.1. Adding it to the project</a></li>
-<li><a href="#_disabling_the_functionality">7.2.2. Disabling the functionality</a></li>
-<li><a href="#_examples">7.2.3. Examples</a></li>
-</ul>
-</li>
-<li><a href="#_stub_runner_integration">7.3. Stub Runner Integration</a>
-<ul class="sectlevel3">
-<li><a href="#_adding_the_runner_to_the_project">7.3.1. Adding the Runner to the Project</a></li>
-<li><a href="#_disabling_the_functionality_2">7.3.2. Disabling the functionality</a></li>
-</ul>
-</li>
-<li><a href="#_stub_runner_stream">7.4. Stub Runner Stream</a>
-<ul class="sectlevel3">
-<li><a href="#_adding_the_runner_to_the_project_2">7.4.1. Adding the Runner to the Project</a></li>
-<li><a href="#_disabling_the_functionality_3">7.4.2. Disabling the functionality</a></li>
-</ul>
-</li>
-<li><a href="#_stub_runner_spring_amqp">7.5. Stub Runner Spring AMQP</a>
-<ul class="sectlevel3">
-<li><a href="#_adding_the_runner_to_the_project_3">7.5.1. Adding the Runner to the Project</a></li>
-</ul>
-</li>
-</ul>
-</li>
-<li><a href="#contract-dsl">8. Contract DSL</a>
-<ul class="sectlevel2">
-<li><a href="#_limitations">8.1. Limitations</a></li>
-<li><a href="#_common_top_level_elements">8.2. Common Top-Level elements</a>
-<ul class="sectlevel3">
-<li><a href="#contract-dsl-description">8.2.1. Description</a></li>
-<li><a href="#contract-dsl-name">8.2.2. Name</a></li>
-<li><a href="#contract-dsl-ignoring-contracts">8.2.3. Ignoring Contracts</a></li>
-<li><a href="#contract-dsl-passing-values-from-files">8.2.4. Passing Values from Files</a></li>
-<li><a href="#contract-dsl-http-top-level-elements">8.2.5. HTTP Top-Level Elements</a></li>
-</ul>
-</li>
-<li><a href="#_request">8.3. Request</a></li>
-<li><a href="#_response">8.4. Response</a></li>
-<li><a href="#_dynamic_properties">8.5. Dynamic properties</a>
-<ul class="sectlevel3">
-<li><a href="#_dynamic_properties_inside_the_body">8.5.1. Dynamic properties inside the body</a></li>
-<li><a href="#_regular_expressions">8.5.2. Regular expressions</a></li>
-<li><a href="#_passing_optional_parameters">8.5.3. Passing Optional Parameters</a></li>
-<li><a href="#_executing_custom_methods_on_the_server_side">8.5.4. Executing Custom Methods on the Server Side</a></li>
-<li><a href="#_referencing_the_request_from_the_response">8.5.5. Referencing the Request from the Response</a></li>
-<li><a href="#_registering_your_own_wiremock_extension">8.5.6. Registering Your Own WireMock Extension</a></li>
-<li><a href="#contract-matchers">8.5.7. Dynamic Properties in the Matchers Sections</a></li>
-</ul>
-</li>
-<li><a href="#_jax_rs_support">8.6. JAX-RS Support</a></li>
-<li><a href="#_async_support">8.7. Async Support</a></li>
-<li><a href="#_working_with_context_paths">8.8. Working with Context Paths</a></li>
-<li><a href="#_working_with_webflux">8.9. Working with WebFlux</a>
-<ul class="sectlevel3">
-<li><a href="#_webflux_with_webtestclient">8.9.1. WebFlux with WebTestClient</a></li>
-<li><a href="#_webflux_with_explicit_mode">8.9.2. WebFlux with Explicit mode</a></li>
-</ul>
-</li>
-<li><a href="#_xml_support_for_rest">8.10. XML Support for REST</a></li>
-<li><a href="#_messaging_top_level_elements">8.11. Messaging Top-Level Elements</a>
-<ul class="sectlevel3">
-<li><a href="#contract-dsl-output-triggered-method">8.11.1. Output Triggered by a Method</a></li>
-<li><a href="#contract-dsl-output-triggered-message">8.11.2. Output Triggered by a Message</a></li>
-<li><a href="#contract-dsl-consumer-producer">8.11.3. Consumer/Producer</a></li>
-<li><a href="#contract-dsl-common">8.11.4. Common</a></li>
-</ul>
-</li>
-<li><a href="#_multiple_contracts_in_one_file">8.12. Multiple Contracts in One File</a></li>
-<li><a href="#_generating_spring_rest_docs_snippets_from_the_contracts">8.13. Generating Spring REST Docs snippets from the contracts</a></li>
-</ul>
-</li>
-<li><a href="#_customization">9. Customization</a>
-<ul class="sectlevel2">
-<li><a href="#_extending_the_dsl">9.1. Extending the DSL</a>
-<ul class="sectlevel3">
-<li><a href="#_common_jar">9.1.1. Common JAR</a></li>
-<li><a href="#_adding_the_dependency_to_the_project">9.1.2. Adding the Dependency to the Project</a></li>
-<li><a href="#_test_the_dependency_in_the_projects_dependencies">9.1.3. Test the Dependency in the Project&#8217;s Dependencies</a></li>
-<li><a href="#_test_a_dependency_in_the_plugins_dependencies">9.1.4. Test a Dependency in the Plugin&#8217;s Dependencies</a></li>
-<li><a href="#_referencing_classes_in_dsls">9.1.5. Referencing classes in DSLs</a></li>
-</ul>
-</li>
-</ul>
-</li>
-<li><a href="#_using_the_pluggable_architecture">10. Using the Pluggable Architecture</a>
-<ul class="sectlevel2">
-<li><a href="#_custom_contract_converter">10.1. Custom Contract Converter</a>
-<ul class="sectlevel3">
-<li><a href="#pact-converter">10.1.1. Pact Converter</a></li>
-<li><a href="#_pact_contract">10.1.2. Pact Contract</a></li>
-<li><a href="#_pact_for_producers">10.1.3. Pact for Producers</a></li>
-<li><a href="#_pact_for_consumers">10.1.4. Pact for Consumers</a></li>
-</ul>
-</li>
-<li><a href="#_using_the_custom_test_generator">10.2. Using the Custom Test Generator</a></li>
-<li><a href="#_using_the_custom_stub_generator">10.3. Using the Custom Stub Generator</a></li>
-<li><a href="#_using_the_custom_stub_runner">10.4. Using the Custom Stub Runner</a></li>
-<li><a href="#_using_the_custom_stub_downloader">10.5. Using the Custom Stub Downloader</a></li>
-<li><a href="#scm-stub-downloader">10.6. Using the SCM Stub Downloader</a></li>
-<li><a href="#pact-stub-downloader">10.7. Using the Pact Stub Downloader</a></li>
-</ul>
-</li>
-<li><a href="#_spring_cloud_contract_wiremock">11. Spring Cloud Contract WireMock</a>
-<ul class="sectlevel2">
-<li><a href="#_registering_stubs_automatically">11.1. Registering Stubs Automatically</a></li>
-<li><a href="#_using_files_to_specify_the_stub_bodies">11.2. Using Files to Specify the Stub Bodies</a></li>
-<li><a href="#_alternative_using_junit_rules">11.3. Alternative: Using JUnit Rules</a></li>
-<li><a href="#_relaxed_ssl_validation_for_rest_template">11.4. Relaxed SSL Validation for Rest Template</a></li>
-<li><a href="#_wiremock_and_spring_mvc_mocks">11.5. WireMock and Spring MVC Mocks</a></li>
-<li><a href="#_customization_of_wiremock_configuration">11.6. Customization of WireMock configuration</a></li>
-<li><a href="#_generating_stubs_using_rest_docs">11.7. Generating Stubs using REST Docs</a></li>
-<li><a href="#_generating_contracts_by_using_rest_docs">11.8. Generating Contracts by Using REST Docs</a></li>
-</ul>
-</li>
-<li><a href="#_migrations">12. Migrations</a>
-<ul class="sectlevel2">
-<li><a href="#cloud-verifier-1.0-1.1">12.1. 1.0.x &#8594; 1.1.x</a>
-<ul class="sectlevel3">
-<li><a href="#_new_structure_of_generated_stubs">12.1.1. New structure of generated stubs</a></li>
-</ul>
-</li>
-<li><a href="#cloud-verifier-1.1-1.2">12.2. 1.1.x &#8594; 1.2.x</a>
-<ul class="sectlevel3">
-<li><a href="#_custom_httpserverstub">12.2.1. Custom <code>HttpServerStub</code></a></li>
-<li><a href="#_new_packages_for_generated_tests">12.2.2. New packages for generated tests</a></li>
-<li><a href="#_new_methods_in_templateprocessor">12.2.3. New Methods in TemplateProcessor</a></li>
-<li><a href="#_restassured_3_0">12.2.4. RestAssured 3.0</a></li>
-</ul>
-</li>
-<li><a href="#cloud-verifier-1.2-2.0">12.3. 1.2.x &#8594; 2.0.x</a></li>
-</ul>
-</li>
-<li><a href="#_links">13. Links</a></li>
-</ul>
+<h1>Spring Cloud Contract Reference Documentation</h1>
+<div class="details">
+<span id="author" class="author">Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant</span><br>
 </div>
 </div>
 <div id="content">
 <div id="preamble">
 <div class="sectionbody">
 <div class="paragraph">
-<p><em>Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak,
-Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant</em></p>
+<p>The reference documentation consists of the following sections:</p>
 </div>
-<div class="paragraph">
-<p>2.2.0.BUILD-SNAPSHOT</p>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_spring_cloud_contract"><a class="link" href="#_spring_cloud_contract">1. Spring Cloud Contract</a></h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>You need confidence when pushing new features to a new application or service in a
-distributed system. This project provides support for Consumer Driven Contracts and
-service schemas in Spring applications (for both HTTP and message-based interactions),
-covering a range of options for writing tests,  publishing them as assets, and asserting
-that a contract is kept by producers and consumers.</p>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_spring_cloud_contract_verifier_introduction"><a class="link" href="#_spring_cloud_contract_verifier_introduction">2. Spring Cloud Contract Verifier Introduction</a></h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>Spring Cloud Contract Verifier enables Consumer Driven Contract (CDC) development of
-JVM-based applications. It moves TDD to the level of software architecture.</p>
-</div>
-<div class="paragraph">
-<p>Spring Cloud Contract Verifier ships with <em>Contract Definition Language</em> (CDL). Contract
-definitions are used to produce the following resources:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>JSON stub definitions to be used by WireMock when doing integration testing on the
-client code (<em>client tests</em>). Test code must still be written by hand, and test data is
-produced by Spring Cloud Contract Verifier.</p>
-</li>
-<li>
-<p>Messaging routes, if you&#8217;re using a messaging service. We integrate with Spring
-Integration, Spring Cloud Stream, Spring AMQP, and Apache Camel. You can also set your
-own integrations.</p>
-</li>
-<li>
-<p>Acceptance tests (in JUnit 4, JUnit 5, TestNG or Spock) are used to verify if server-side implementation
-of the API is compliant with the contract (<em>server tests</em>). A full test is generated by
-Spring Cloud Contract Verifier.</p>
-</li>
-</ul>
-</div>
-<div class="sect2">
-<h3 id="_history"><a class="link" href="#_history">2.1. History</a></h3>
-<div class="paragraph">
-<p>Before becoming Spring Cloud Contract, this project was called <a href="https://github.com/Codearte/accurest">Accurest</a>.
-It was created by <a href="https://twitter.com/mgrzejszczak">Marcin Grzejszczak</a> and <a href="https://twitter.com/jkubrynski">Jakub Kubrynski</a>
-from (<a href="https://github.com/Codearte">Codearte</a>.</p>
-</div>
-<div class="paragraph">
-<p>The <code>0.1.0</code> release took place on 26 Jan 2015 and it became stable with <code>1.0.0</code> release on 29 Feb 2016.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_why_a_contract_verifier"><a class="link" href="#_why_a_contract_verifier">2.2. Why a Contract Verifier?</a></h3>
-<div class="paragraph">
-<p>Assume that we have a system consisting of multiple microservices:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="https://raw.githubusercontent.com/spring-cloud/spring-cloud-contract/master/docs/src/main/asciidoc/images/Deps.png" alt="Microservices Architecture">
-</div>
-</div>
-<div class="sect3">
-<h4 id="_testing_issues"><a class="link" href="#_testing_issues">2.2.1. Testing issues</a></h4>
-<div class="paragraph">
-<p>If we wanted to test the application in top left corner to determine whether it can
-communicate with other services, we could do one of two things:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Deploy all microservices and perform end-to-end tests.</p>
-</li>
-<li>
-<p>Mock other microservices in unit/integration tests.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Both have their advantages but also a lot of disadvantages.</p>
-</div>
-<div class="paragraph">
-<p><strong>Deploy all microservices and perform end to end tests</strong></p>
-</div>
-<div class="paragraph">
-<p>Advantages:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Simulates production.</p>
-</li>
-<li>
-<p>Tests real communication between services.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Disadvantages:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>To test one microservice, we have to deploy 6 microservices, a couple of databases,
-etc.</p>
-</li>
-<li>
-<p>The environment where the tests run is locked for a single suite of tests (nobody else
-would be able to run the tests in the meantime).</p>
-</li>
-<li>
-<p>They take a long time to run.</p>
-</li>
-<li>
-<p>The feedback comes very late in the process.</p>
-</li>
-<li>
-<p>They are extremely hard to debug.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p><strong>Mock other microservices in unit/integration tests</strong></p>
-</div>
-<div class="paragraph">
-<p>Advantages:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>They provide very fast feedback.</p>
-</li>
-<li>
-<p>They have no infrastructure requirements.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Disadvantages:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>The implementor of the service creates stubs that might have nothing to do with
-reality.</p>
-</li>
-<li>
-<p>You can go to production with passing tests and failing production.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>To solve the aforementioned issues, Spring Cloud Contract Verifier with Stub Runner was
-created. The main idea is to give you very fast feedback, without the need to set up the
-whole world of microservices. If you work on stubs, then the only applications you need
-are those that your application directly uses.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="https://raw.githubusercontent.com/spring-cloud/spring-cloud-contract/master/docs/src/main/asciidoc/images/Stubs2.png" alt="Stubbed Services">
-</div>
-</div>
-<div class="paragraph">
-<p>Spring Cloud Contract Verifier gives you the certainty that the stubs that you use were
-created by the service that you&#8217;re calling. Also, if you can use them, it means that they
-were tested against the producer&#8217;s side. In short, you can trust those stubs.</p>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_purposes"><a class="link" href="#_purposes">2.3. Purposes</a></h3>
-<div class="paragraph">
-<p>The main purposes of Spring Cloud Contract Verifier with Stub Runner are:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>To ensure that WireMock/Messaging stubs (used when developing the client) do exactly
-what the actual server-side implementation does.</p>
-</li>
-<li>
-<p>To promote ATDD method and Microservices architectural style.</p>
-</li>
-<li>
-<p>To provide a way to publish changes in contracts that are immediately visible on both
-sides.</p>
-</li>
-<li>
-<p>To generate boilerplate test code to be used on the server side.</p>
-</li>
-</ul>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-Spring Cloud Contract Verifier&#8217;s purpose is NOT to start writing business
-features in the contracts. Assume that we have a business use case of fraud check. If a
-user can be a fraud for 100 different reasons, we would assume that you would create 2
-contracts, one for the positive case and one for the negative case. Contract tests are
-used to test contracts between applications and not to simulate full behavior.
-</td>
-</tr>
-</table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_how_it_works"><a class="link" href="#_how_it_works">2.4. How It Works</a></h3>
-<div class="paragraph">
-<p>This section explores how Spring Cloud Contract Verifier with Stub Runner works.</p>
-</div>
-<div class="sect3">
-<h4 id="spring-cloud-contract-verifier-intro-three-second-tour"><a class="link" href="#spring-cloud-contract-verifier-intro-three-second-tour">2.4.1. A Three-second Tour</a></h4>
-<div class="paragraph">
-<p>This very brief tour walks through using Spring Cloud Contract:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="#spring-cloud-contract-verifier-intro-three-second-tour-producer">On the Producer Side</a></p>
-</li>
-<li>
-<p><a href="#spring-cloud-contract-verifier-intro-three-second-tour-consumer">On the Consumer Side</a></p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>You can find a somewhat longer tour
-<a href="#spring-cloud-contract-verifier-intro-three-minute-tour">here</a>.</p>
-</div>
-<div class="sect4">
-<h5 id="spring-cloud-contract-verifier-intro-three-second-tour-producer"><a class="link" href="#spring-cloud-contract-verifier-intro-three-second-tour-producer">On the Producer Side</a></h5>
-<div class="paragraph">
-<p>To start working with Spring Cloud Contract, add files with <code>REST/</code> messaging contracts
-expressed in either Groovy DSL or YAML to the contracts directory, which is set by the
-<code>contractsDslDir</code> property. By default, it is <code>$rootDir/src/test/resources/contracts</code>.</p>
-</div>
-<div class="paragraph">
-<p>Then add the Spring Cloud Contract Verifier dependency and plugin to your build file, as
-shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-starter-contract-verifier&lt;/artifactId&gt;
-	&lt;scope&gt;test&lt;/scope&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following listing shows how to add the plugin, which should go in the build/plugins
-portion of the file:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-	&lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-	&lt;extensions&gt;true&lt;/extensions&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Running <code>./mvnw clean install</code> automatically generates tests that verify the application
-compliance with the added contracts. By default, the tests get generated under
-<code>org.springframework.cloud.contract.verifier.tests.</code>.</p>
-</div>
-<div class="paragraph">
-<p>As the implementation of the functionalities described by the contracts is not yet
-present, the tests fail.</p>
-</div>
-<div class="paragraph">
-<p>To make them pass, you must add the correct implementation of either handling HTTP
-requests or messages. Also, you must add a correct base test class for auto-generated
-tests to the project. This class is extended by all the auto-generated tests, and it
-should contain all the setup necessary to run them (for example <code>RestAssuredMockMvc</code>
-controller setup or messaging test setup).</p>
-</div>
-<div class="paragraph">
-<p>Once the implementation and the test base class are in place, the tests pass, and both the
-application and the stub artifacts are built and installed in the local Maven repository.
-The changes can now be merged, and both the application and the stub artifacts may be
-published in an online repository.</p>
-</div>
-</div>
-<div class="sect4">
-<h5 id="spring-cloud-contract-verifier-intro-three-second-tour-consumer"><a class="link" href="#spring-cloud-contract-verifier-intro-three-second-tour-consumer">On the Consumer Side</a></h5>
-<div class="paragraph">
-<p><code>Spring Cloud Contract Stub Runner</code> can be used in the integration tests to get a running
-WireMock instance or messaging route that simulates the actual service.</p>
-</div>
-<div class="paragraph">
-<p>To do so, add the dependency to <code>Spring Cloud Contract Stub Runner</code>, as shown in the
-following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-starter-contract-stub-runner&lt;/artifactId&gt;
-	&lt;scope&gt;test&lt;/scope&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You can get the Producer-side stubs installed in your Maven repository in either of two
-ways:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>By checking out the Producer side repository and adding contracts and generating the stubs
-by running the following commands:</p>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ cd local-http-server-repo
-$ ./mvnw clean install -DskipTests</code></pre>
-</div>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-The tests are being skipped because the Producer-side contract implementation is not
-in place yet, so the automatically-generated contract tests fail.
-</td>
-</tr>
-</table>
-</div>
-</li>
-<li>
-<p>By getting already-existing producer service stubs from a remote repository. To do so,
-pass the stub artifact IDs and artifact repository URL as <code>Spring Cloud Contract
-Stub Runner</code> properties, as shown in the following example:</p>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">stubrunner:
-  ids: 'com.example:http-server-dsl:+:stubs:8080'
-  repositoryRoot: https://repo.spring.io/libs-snapshot</code></pre>
-</div>
-</div>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Now you can annotate your test class with <code>@AutoConfigureStubRunner</code>. In the annotation,
-provide the <code>group-id</code> and <code>artifact-id</code> values for <code>Spring Cloud Contract Stub Runner</code> to
-run the collaborators' stubs for you, as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
-@SpringBootTest(webEnvironment=WebEnvironment.NONE)
-@AutoConfigureStubRunner(ids = {"com.example:http-server-dsl:+:stubs:6565"},
-		stubsMode = StubRunnerProperties.StubsMode.LOCAL)
-public class LoanApplicationServiceTests {</code></pre>
-</div>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-Use the <code>REMOTE</code> <code>stubsMode</code> when downloading stubs from an online repository and
-<code>LOCAL</code> for offline work.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>Now, in your integration test, you can receive stubbed versions of HTTP responses or
-messages that are expected to be emitted by the collaborator service.</p>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="spring-cloud-contract-verifier-intro-three-minute-tour"><a class="link" href="#spring-cloud-contract-verifier-intro-three-minute-tour">2.4.2. A Three-minute Tour</a></h4>
-<div class="paragraph">
-<p>This brief tour walks through using Spring Cloud Contract:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="#spring-cloud-contract-verifier-intro-three-minute-tour-producer">On the Producer Side</a></p>
-</li>
-<li>
-<p><a href="#spring-cloud-contract-verifier-intro-three-minute-tour-consumer">On the Consumer Side</a></p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>You can find an even more brief tour
-<a href="#spring-cloud-contract-verifier-intro-three-second-tour">here</a>.</p>
-</div>
-<div class="sect4">
-<h5 id="spring-cloud-contract-verifier-intro-three-minute-tour-producer"><a class="link" href="#spring-cloud-contract-verifier-intro-three-minute-tour-producer">On the Producer Side</a></h5>
-<div class="paragraph">
-<p>To start working with <code>Spring Cloud Contract</code>, add files with <code>REST/</code> messaging contracts
-expressed in either Groovy DSL or YAML to the contracts directory, which is set by the
-<code>contractsDslDir</code> property. By default, it is <code>$rootDir/src/test/resources/contracts</code>.</p>
-</div>
-<div class="paragraph">
-<p>For the HTTP stubs, a contract defines what kind of response should be returned for a
-given request (taking into account the HTTP methods, URLs, headers, status codes, and so
-on). The following example shows how an HTTP stub contract in Groovy DSL:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package contracts
-
-org.springframework.cloud.contract.spec.Contract.make {
-	request {
-		method 'PUT'
-		url '/fraudcheck'
-		body([
-			   "client.id": $(regex('[0-9]{10}')),
-			   loanAmount: 99999
-		])
-		headers {
-			contentType('application/json')
-		}
-	}
-	response {
-		status OK()
-		body([
-			   fraudCheckStatus: "FRAUD",
-			   "rejection.reason": "Amount too high"
-		])
-		headers {
-			contentType('application/json')
-		}
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The same contract expressed in YAML would look like the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">request:
-  method: PUT
-  url: /fraudcheck
-  body:
-    "client.id": 1234567890
-    loanAmount: 99999
-  headers:
-    Content-Type: application/json
-  matchers:
-    body:
-      - path: $.['client.id']
-        type: by_regex
-        value: "[0-9]{10}"
-response:
-  status: 200
-  body:
-    fraudCheckStatus: "FRAUD"
-    "rejection.reason": "Amount too high"
-  headers:
-    Content-Type: application/json;charset=UTF-8</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In the case of messaging, you can define:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>The input and the output messages can be defined (taking into account from and where it
-was sent, the message body, and the header).</p>
-</li>
-<li>
-<p>The methods that should be called after the message is received.</p>
-</li>
-<li>
-<p>The methods that, when called, should trigger a message.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>The following example shows a Camel messaging contract expressed in Groovy DSL:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">			def contractDsl = Contract.make {
-				name "foo"
-				label 'some_label'
-				input {
-					messageFrom('jms:delete')
-					messageBody([
-							bookName: 'foo'
-					])
-					messageHeaders {
-						header('sample', 'header')
-					}
-					assertThat('bookWasDeleted()')
-				}
-			}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following example shows the same contract expressed in YAML:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">label: some_label
-input:
-  messageFrom: jms:delete
-  messageBody:
-    bookName: 'foo'
-  messageHeaders:
-    sample: header
-  assertThat: bookWasDeleted()</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Then you can add Spring Cloud Contract Verifier dependency and plugin to your build file,
-as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-starter-contract-verifier&lt;/artifactId&gt;
-	&lt;scope&gt;test&lt;/scope&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following listing shows how to add the plugin, which should go in the build/plugins
-portion of the file:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-	&lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-	&lt;extensions&gt;true&lt;/extensions&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Running <code>./mvnw clean install</code> automatically generates tests that verify the application
-compliance with the added contracts. By default, the generated tests are under
-<code>org.springframework.cloud.contract.verifier.tests.</code>.</p>
-</div>
-<div class="paragraph">
-<p>The following example shows a sample auto-generated test for an HTTP contract:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Test
-public void validate_shouldMarkClientAsFraud() throws Exception {
-    // given:
-        MockMvcRequestSpecification request = given()
-                .header("Content-Type", "application/vnd.fraud.v1+json")
-                .body("{\"client.id\":\"1234567890\",\"loanAmount\":99999}");
-
-    // when:
-        ResponseOptions response = given().spec(request)
-                .put("/fraudcheck");
-
-    // then:
-        assertThat(response.statusCode()).isEqualTo(200);
-        assertThat(response.header("Content-Type")).matches("application/vnd.fraud.v1.json.*");
-    // and:
-        DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
-        assertThatJson(parsedJson).field("['fraudCheckStatus']").matches("[A-Z]{5}");
-        assertThatJson(parsedJson).field("['rejection.reason']").isEqualTo("Amount too high");
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The preceding example uses Spring&#8217;s <code>MockMvc</code> to run the tests. This is the default test
-mode for HTTP contracts. However, JAX-RS client and explicit HTTP invocations can also be
-used. (To do so, change the <code>testMode</code> property of the plugin to <code>JAX-RS</code> or <code>EXPLICIT</code>,
-respectively.)</p>
-</div>
-<div class="paragraph">
-<p>Since 2.1.0, it is also possible to use <code>RestAssuredWebTestClient`with Spring&#8217;s reactive `WebTestClient</code>
-run under the hood. This is particularly recommended while working with Reactive, <code>Web-Flux</code>-based applications.
-In order to use <code>WebTestClient</code> set <code>testMode</code> to <code>WEBTESTCLIENT</code>.</p>
-</div>
-<div class="paragraph">
-<p>Here is an example of a test generated in <code>WEBTESTCLIENT</code> test mode:</p>
-</div>
-<div class="literalblock">
-<div class="content">
-<pre>[source,java,indent=0]</pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>@Test
-	public void validate_shouldRejectABeerIfTooYoung() throws Exception {
-		// given:
-			WebTestClientRequestSpecification request = given()
-					.header("Content-Type", "application/json")
-					.body("{\"age\":10}");
-
-		// when:
-			WebTestClientResponse response = given().spec(request)
-					.post("/check");
-
-		// then:
-			assertThat(response.statusCode()).isEqualTo(200);
-			assertThat(response.header("Content-Type")).matches("application/json.*");
-		// and:
-			DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
-			assertThatJson(parsedJson).field("['status']").isEqualTo("NOT_OK");
-	}</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Apart from the default JUnit 4, you can instead use JUnit 5, TestNG or Spock tests, by setting the plugin
-<code>testFramework</code> property to either <code>JUNIT5</code>, <code>TESTNG</code> or <code>Spock</code>.</p>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-You can now also generate WireMock scenarios based on the contracts, by including an
-order number followed by an underscore at the beginning of the contract file names.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>The following example shows an auto-generated test in Spock for a messaging stub contract:</p>
-</div>
-<div class="literalblock">
-<div class="content">
-<pre>[source,groovy,indent=0]</pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>given:
-	 ContractVerifierMessage inputMessage = contractVerifierMessaging.create(
-		\'\'\'{"bookName":"foo"}\'\'\',
-		['sample': 'header']
-	)
-
-when:
-	 contractVerifierMessaging.send(inputMessage, 'jms:delete')
-
-then:
-	 noExceptionThrown()
-	 bookWasDeleted()</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>As the implementation of the functionalities described by the contracts is not yet
-present, the tests fail.</p>
-</div>
-<div class="paragraph">
-<p>To make them pass, you must add the correct implementation of handling either HTTP
-requests or messages. Also, you must add a correct base test class for auto-generated
-tests to the project. This class is extended by all the auto-generated tests and should
-contain all the setup necessary to run them (for example, <code>RestAssuredMockMvc</code> controller
-setup or messaging test setup).</p>
-</div>
-<div class="paragraph">
-<p>Once the implementation and the test base class are in place, the tests pass, and both the
-application and the stub artifacts are built and installed in the local Maven repository.
-Information about installing the stubs jar to the local repository appears in the logs, as
-shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">[INFO] --- spring-cloud-contract-maven-plugin:1.0.0.BUILD-SNAPSHOT:generateStubs (default-generateStubs) @ http-server ---
-[INFO] Building jar: /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar
-[INFO]
-[INFO] --- maven-jar-plugin:2.6:jar (default-jar) @ http-server ---
-[INFO] Building jar: /some/path/http-server/target/http-server-0.0.1-SNAPSHOT.jar
-[INFO]
-[INFO] --- spring-boot-maven-plugin:1.5.5.BUILD-SNAPSHOT:repackage (default) @ http-server ---
-[INFO]
-[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ http-server ---
-[INFO] Installing /some/path/http-server/target/http-server-0.0.1-SNAPSHOT.jar to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT.jar
-[INFO] Installing /some/path/http-server/pom.xml to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT.pom
-[INFO] Installing /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You can now merge the changes and publish both the application and the stub artifacts
-in an online repository.</p>
-</div>
-<div class="paragraph">
-<p><strong>Docker Project</strong></p>
-</div>
-<div class="paragraph">
-<p>In order to enable working with contracts while creating applications in non-JVM
-technologies, the <code>springcloud/spring-cloud-contract</code> Docker image has been created. It
-contains a project that automatically generates tests for HTTP contracts and executes them
-in  <code>EXPLICIT</code> test mode. Then, if the tests pass, it generates Wiremock stubs and,
-optionally, publishes them to an artifact manager. In order to use the image, you can
-mount the contracts into the <code>/contracts</code> directory and set a few environment variables.</p>
-</div>
-</div>
-<div class="sect4">
-<h5 id="spring-cloud-contract-verifier-intro-three-minute-tour-consumer"><a class="link" href="#spring-cloud-contract-verifier-intro-three-minute-tour-consumer">On the Consumer Side</a></h5>
-<div class="paragraph">
-<p><code>Spring Cloud Contract Stub Runner</code> can be used in the integration tests to get a running
-WireMock instance or messaging route that simulates the actual service.</p>
-</div>
-<div class="paragraph">
-<p>To get started, add the dependency to <code>Spring Cloud Contract Stub Runner</code>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-starter-contract-stub-runner&lt;/artifactId&gt;
-	&lt;scope&gt;test&lt;/scope&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You can get the Producer-side stubs installed in your Maven repository in either of two
-ways:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>By checking out the Producer side repository and adding contracts and generating the
-stubs by running the following commands:</p>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ cd local-http-server-repo
-$ ./mvnw clean install -DskipTests</code></pre>
-</div>
-</div>
-<div class="admonitionblock note">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-note" title="Note"></i>
-</td>
-<td class="content">
-The tests are skipped because the Producer-side contract implementation is not yet
-in place, so the automatically-generated contract tests fail.
-</td>
-</tr>
-</table>
-</div>
-</li>
-<li>
-<p>Getting already existing producer service stubs from a remote repository. To do so,
-pass the stub artifact IDs and artifact repository URl as <code>Spring Cloud Contract Stub
-Runner</code> properties, as shown in the following example:</p>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">stubrunner:
-  ids: 'com.example:http-server-dsl:+:stubs:8080'
-  repositoryRoot: https://repo.spring.io/libs-snapshot</code></pre>
-</div>
-</div>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Now you can annotate your test class with <code>@AutoConfigureStubRunner</code>. In the annotation,
-provide the <code>group-id</code> and <code>artifact-id</code> for <code>Spring Cloud Contract Stub Runner</code> to run
-the collaborators' stubs for you, as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
-@SpringBootTest(webEnvironment=WebEnvironment.NONE)
-@AutoConfigureStubRunner(ids = {"com.example:http-server-dsl:+:stubs:6565"},
-		stubsMode = StubRunnerProperties.StubsMode.LOCAL)
-public class LoanApplicationServiceTests {</code></pre>
-</div>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-Use the <code>REMOTE</code> <code>stubsMode</code> when downloading stubs from an online repository and
-<code>LOCAL</code> for offline work.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>In your integration test, you can receive stubbed versions of HTTP responses or messages
-that are expected to be emitted by the collaborator service. You can see entries similar
-to the following in the build logs:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">2016-07-19 14:22:25.403  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Desired version is + - will try to resolve the latest version
-2016-07-19 14:22:25.438  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Resolved version is 0.0.1-SNAPSHOT
-2016-07-19 14:22:25.439  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Resolving artifact com.example:http-server:jar:stubs:0.0.1-SNAPSHOT using remote repositories []
-2016-07-19 14:22:25.451  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Resolved artifact com.example:http-server:jar:stubs:0.0.1-SNAPSHOT to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar
-2016-07-19 14:22:25.465  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Unpacking stub from JAR [URI: file:/path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar]
-2016-07-19 14:22:25.475  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Unpacked file to [/var/folders/0p/xwq47sq106x1_g3dtv6qfm940000gq/T/contracts100276532569594265]
-2016-07-19 14:22:27.737  INFO 41050 --- [           main] o.s.c.c.stubrunner.StubRunnerExecutor    : All stubs are now running RunningStubs [namesAndPorts={com.example:http-server:0.0.1-SNAPSHOT:stubs=8080}]</code></pre>
-</div>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_defining_the_contract"><a class="link" href="#_defining_the_contract">2.4.3. Defining the Contract</a></h4>
-<div class="paragraph">
-<p>As consumers of services, we need to define what exactly we want to achieve. We need to
-formulate our expectations. That is why we write contracts.</p>
-</div>
-<div class="paragraph">
-<p>Assume that you want to send a request containing the ID of a client company and the
-amount it wants to borrow from us. You also want to send it to the /fraudcheck url via
-the PUT method.</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">/*
- * Copyright 2013-2019 the original author or authors.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *      https://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
-package contracts
-
-org.springframework.cloud.contract.spec.Contract.make {
-	request { // (1)
-		method 'PUT' // (2)
-		url '/fraudcheck' // (3)
-		body([ // (4)
-			   "client.id": $(regex('[0-9]{10}')),
-			   loanAmount : 99999
-		])
-		headers { // (5)
-			contentType('application/json')
-		}
-	}
-	response { // (6)
-		status OK() // (7)
-		body([ // (8)
-			   fraudCheckStatus  : "FRAUD",
-			   "rejection.reason": "Amount too high"
-		])
-		headers { // (9)
-			contentType('application/json')
-		}
-	}
-}
-
-/*
-From the Consumer perspective, when shooting a request in the integration test:
-
-(1) - If the consumer sends a request
-(2) - With the "PUT" method
-(3) - to the URL "/fraudcheck"
-(4) - with the JSON body that
- * has a field `client.id` that matches a regular expression `[0-9]{10}`
- * has a field `loanAmount` that is equal to `99999`
-(5) - with header `Content-Type` equal to `application/json`
-(6) - then the response will be sent with
-(7) - status equal `200`
-(8) - and JSON body equal to
- { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
-(9) - with header `Content-Type` equal to `application/json`
-
-From the Producer perspective, in the autogenerated producer-side test:
-
-(1) - A request will be sent to the producer
-(2) - With the "PUT" method
-(3) - to the URL "/fraudcheck"
-(4) - with the JSON body that
- * has a field `client.id` that will have a generated value that matches a regular expression `[0-9]{10}`
- * has a field `loanAmount` that is equal to `99999`
-(5) - with header `Content-Type` equal to `application/json`
-(6) - then the test will assert if the response has been sent with
-(7) - status equal `200`
-(8) - and JSON body equal to
- { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
-(9) - with header `Content-Type` matching `application/json.*`
- */</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request: # (1)
-  method: PUT # (2)
-  url: /fraudcheck # (3)
-  body: # (4)
-    "client.id": 1234567890
-    loanAmount: 99999
-  headers: # (5)
-    Content-Type: application/json
-  matchers:
-    body:
-      - path: $.['client.id'] # (6)
-        type: by_regex
-        value: "[0-9]{10}"
-response: # (7)
-  status: 200 # (8)
-  body:  # (9)
-    fraudCheckStatus: "FRAUD"
-    "rejection.reason": "Amount too high"
-  headers: # (10)
-    Content-Type: application/json
-
-
-#From the Consumer perspective, when shooting a request in the integration test:
-#
-#(1) - If the consumer sends a request
-#(2) - With the "PUT" method
-#(3) - to the URL "/fraudcheck"
-#(4) - with the JSON body that
-# * has a field `client.id`
-# * has a field `loanAmount` that is equal to `99999`
-#(5) - with header `Content-Type` equal to `application/json`
-#(6) - and a `client.id` json entry matches the regular expression `[0-9]{10}`
-#(7) - then the response will be sent with
-#(8) - status equal `200`
-#(9) - and JSON body equal to
-# { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
-#(10) - with header `Content-Type` equal to `application/json`
-#
-#From the Producer perspective, in the autogenerated producer-side test:
-#
-#(1) - A request will be sent to the producer
-#(2) - With the "PUT" method
-#(3) - to the URL "/fraudcheck"
-#(4) - with the JSON body that
-# * has a field `client.id` `1234567890`
-# * has a field `loanAmount` that is equal to `99999`
-#(5) - with header `Content-Type` equal to `application/json`
-#(7) - then the test will assert if the response has been sent with
-#(8) - status equal `200`
-#(9) - and JSON body equal to
-# { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
-#(10) - with header `Content-Type` equal to `application/json`</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_client_side"><a class="link" href="#_client_side">2.4.4. Client Side</a></h4>
-<div class="paragraph">
-<p>Spring Cloud Contract generates stubs, which you can use during client-side testing.
-You get a running WireMock instance/Messaging route that simulates the service.
-You would like to feed that instance with a proper stub definition.</p>
-</div>
-<div class="paragraph">
-<p>At some point in time, you need to send a request to the Fraud Detection service.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">ResponseEntity&lt;FraudServiceResponse&gt; response = restTemplate.exchange(
-		"http://localhost:" + port + "/fraudcheck", HttpMethod.PUT,
-		new HttpEntity&lt;&gt;(request, httpHeaders), FraudServiceResponse.class);</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Annotate your test class with <code>@AutoConfigureStubRunner</code>. In the annotation provide the group id and artifact id for the Stub Runner to download stubs of your collaborators.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@RunWith(SpringRunner.class)
-@SpringBootTest(webEnvironment = WebEnvironment.NONE)
-@AutoConfigureStubRunner(ids = {
-		"com.example:http-server-dsl:+:stubs:6565" }, stubsMode = StubRunnerProperties.StubsMode.LOCAL)
-public class LoanApplicationServiceTests {</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>After that, during the tests, Spring Cloud Contract automatically finds the stubs
-(simulating the real service) in the Maven repository and exposes them on a configured
-(or random) port.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_server_side"><a class="link" href="#_server_side">2.4.5. Server Side</a></h4>
-<div class="paragraph">
-<p>Since you are developing your stub, you need to be sure that it actually resembles your
-concrete implementation. You cannot have a situation where your stub acts in one way and
-your application behaves in a different way, especially in production.</p>
-</div>
-<div class="paragraph">
-<p>To ensure that your application behaves the way you define in your stub, tests are
-generated from the stub you provide.</p>
-</div>
-<div class="paragraph">
-<p>The autogenerated test looks, more or less, like this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Test
-public void validate_shouldMarkClientAsFraud() throws Exception {
-    // given:
-        MockMvcRequestSpecification request = given()
-                .header("Content-Type", "application/vnd.fraud.v1+json")
-                .body("{\"client.id\":\"1234567890\",\"loanAmount\":99999}");
-
-    // when:
-        ResponseOptions response = given().spec(request)
-                .put("/fraudcheck");
-
-    // then:
-        assertThat(response.statusCode()).isEqualTo(200);
-        assertThat(response.header("Content-Type")).matches("application/vnd.fraud.v1.json.*");
-    // and:
-        DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
-        assertThatJson(parsedJson).field("['fraudCheckStatus']").matches("[A-Z]{5}");
-        assertThatJson(parsedJson).field("['rejection.reason']").isEqualTo("Amount too high");
-}</code></pre>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_step_by_step_guide_to_consumer_driven_contracts_cdc"><a class="link" href="#_step_by_step_guide_to_consumer_driven_contracts_cdc">2.5. Step-by-step Guide to Consumer Driven Contracts (CDC)</a></h3>
-<div class="paragraph">
-<p>Consider an example of Fraud Detection and the Loan Issuance process. The business
-scenario is such that we want to issue loans to people but do not want them to steal from
-us. The current implementation of our system grants loans to everybody.</p>
-</div>
-<div class="paragraph">
-<p>Assume that <code>Loan Issuance</code> is a client to the <code>Fraud Detection</code> server. In the current
-sprint, we must develop a new feature: if a client wants to borrow too much money, then
-we mark the client as a fraud.</p>
-</div>
-<div class="paragraph">
-<p>Technical remark - Fraud Detection has an <code>artifact-id</code> of <code>http-server</code>, while Loan
-Issuance has an artifact-id of <code>http-client</code>, and both have a <code>group-id</code> of <code>com.example</code>.</p>
-</div>
-<div class="paragraph">
-<p>Social remark - both client and server development teams need to communicate directly and
-discuss changes while going through the process. CDC is all about communication.</p>
-</div>
-<div class="paragraph">
-<p>The <a href="https://github.com/spring-cloud/spring-cloud-contract/tree/master/samples/standalone/dsl/http-server">server
-side code is available here</a> and <a href="https://github.com/spring-cloud/spring-cloud-contract/tree/master/samples/standalone/dsl/http-client">the
-client code here</a>.</p>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-In this case, the producer owns the contracts. Physically, all the contract are
-in the producer&#8217;s repository.
-</td>
-</tr>
-</table>
-</div>
-<div class="sect3">
-<h4 id="_technical_note"><a class="link" href="#_technical_note">2.5.1. Technical note</a></h4>
-<div class="paragraph">
-<p>If using the <strong>SNAPSHOT</strong> / <strong>Milestone</strong> / <strong>Release Candidate</strong> versions please add the
-following section to your build:</p>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;repositories&gt;
-	&lt;repository&gt;
-		&lt;id&gt;spring-snapshots&lt;/id&gt;
-		&lt;name&gt;Spring Snapshots&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;true&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/repository&gt;
-	&lt;repository&gt;
-		&lt;id&gt;spring-milestones&lt;/id&gt;
-		&lt;name&gt;Spring Milestones&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;false&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/repository&gt;
-	&lt;repository&gt;
-		&lt;id&gt;spring-releases&lt;/id&gt;
-		&lt;name&gt;Spring Releases&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;false&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/repository&gt;
-&lt;/repositories&gt;
-&lt;pluginRepositories&gt;
-	&lt;pluginRepository&gt;
-		&lt;id&gt;spring-snapshots&lt;/id&gt;
-		&lt;name&gt;Spring Snapshots&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;true&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/pluginRepository&gt;
-	&lt;pluginRepository&gt;
-		&lt;id&gt;spring-milestones&lt;/id&gt;
-		&lt;name&gt;Spring Milestones&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;false&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/pluginRepository&gt;
-	&lt;pluginRepository&gt;
-		&lt;id&gt;spring-releases&lt;/id&gt;
-		&lt;name&gt;Spring Releases&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;false&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/pluginRepository&gt;
-&lt;/pluginRepositories&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">repositories {
-	mavenCentral()
-	mavenLocal()
-	maven { url "https://repo.spring.io/snapshot" }
-	maven { url "https://repo.spring.io/milestone" }
-	maven { url "https://repo.spring.io/release" }
-}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_consumer_side_loan_issuance"><a class="link" href="#_consumer_side_loan_issuance">2.5.2. Consumer side (Loan Issuance)</a></h4>
-<div class="paragraph">
-<p>As a developer of the Loan Issuance service (a consumer of the Fraud Detection server), you might do the following steps:</p>
-</div>
-<div class="olist arabic">
-<ol class="arabic">
-<li>
-<p>Start doing TDD by writing a test for your feature.</p>
-</li>
-<li>
-<p>Write the missing implementation.</p>
-</li>
-<li>
-<p>Clone the Fraud Detection service repository locally.</p>
-</li>
-<li>
-<p>Define the contract locally in the repo of Fraud Detection service.</p>
-</li>
-<li>
-<p>Add the Spring Cloud Contract Verifier plugin.</p>
-</li>
-<li>
-<p>Run the integration tests.</p>
-</li>
-<li>
-<p>File a pull request.</p>
-</li>
-<li>
-<p>Create an initial implementation.</p>
-</li>
-<li>
-<p>Take over the pull request.</p>
-</li>
-<li>
-<p>Write the missing implementation.</p>
-</li>
-<li>
-<p>Deploy your app.</p>
-</li>
-<li>
-<p>Work online.</p>
-</li>
-</ol>
-</div>
-<div class="paragraph">
-<p><strong>Start doing TDD by writing a test for your feature.</strong></p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@Test
-public void shouldBeRejectedDueToAbnormalLoanAmount() {
-	// given:
-	LoanApplication application = new LoanApplication(new Client("1234567890"),
-			99999);
-	// when:
-	LoanApplicationResult loanApplication = service.loanApplication(application);
-	// then:
-	assertThat(loanApplication.getLoanApplicationStatus())
-			.isEqualTo(LoanApplicationStatus.LOAN_APPLICATION_REJECTED);
-	assertThat(loanApplication.getRejectionReason()).isEqualTo("Amount too high");
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Assume that you have written a test of your new feature. If a loan application for a big
-amount is received, the system should reject that loan application with some description.</p>
-</div>
-<div class="paragraph">
-<p><strong>Write the missing implementation.</strong></p>
-</div>
-<div class="paragraph">
-<p>At some point in time, you need to send a request to the Fraud Detection service. Assume
-that you need to send the request containing the ID of the client and the amount the
-client wants to borrow. You want to send it to the <code>/fraudcheck</code> url via the <code>PUT</code> method.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">ResponseEntity&lt;FraudServiceResponse&gt; response = restTemplate.exchange(
-		"http://localhost:" + port + "/fraudcheck", HttpMethod.PUT,
-		new HttpEntity&lt;&gt;(request, httpHeaders), FraudServiceResponse.class);</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>For simplicity, the port of the Fraud Detection service is set to <code>8080</code>, and the
-application runs on <code>8090</code>.</p>
-</div>
-<div class="paragraph">
-<p>If you start the test at this point, it breaks, because no service currently runs on port
-<code>8080</code>.</p>
-</div>
-<div class="paragraph">
-<p><strong>Clone the Fraud Detection service repository locally.</strong></p>
-</div>
-<div class="paragraph">
-<p>You can start by playing around with the server side contract. To do so, you must first
-clone it.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ git clone https://your-git-server.com/server-side.git local-http-server-repo</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><strong>Define the contract locally in the repo of Fraud Detection service.</strong></p>
-</div>
-<div class="paragraph">
-<p>As a consumer, you need to define what exactly you want to achieve. You need to formulate
-your expectations. To do so, write the following contract:</p>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-Place the contract under <code>src/test/resources/contracts/fraud</code> folder. The <code>fraud</code> folder
-is important because the producer&#8217;s test base class name references that folder.
-</td>
-</tr>
-</table>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">/*
- * Copyright 2013-2019 the original author or authors.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *      https://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
-package contracts
-
-org.springframework.cloud.contract.spec.Contract.make {
-	request { // (1)
-		method 'PUT' // (2)
-		url '/fraudcheck' // (3)
-		body([ // (4)
-			   "client.id": $(regex('[0-9]{10}')),
-			   loanAmount : 99999
-		])
-		headers { // (5)
-			contentType('application/json')
-		}
-	}
-	response { // (6)
-		status OK() // (7)
-		body([ // (8)
-			   fraudCheckStatus  : "FRAUD",
-			   "rejection.reason": "Amount too high"
-		])
-		headers { // (9)
-			contentType('application/json')
-		}
-	}
-}
-
-/*
-From the Consumer perspective, when shooting a request in the integration test:
-
-(1) - If the consumer sends a request
-(2) - With the "PUT" method
-(3) - to the URL "/fraudcheck"
-(4) - with the JSON body that
- * has a field `client.id` that matches a regular expression `[0-9]{10}`
- * has a field `loanAmount` that is equal to `99999`
-(5) - with header `Content-Type` equal to `application/json`
-(6) - then the response will be sent with
-(7) - status equal `200`
-(8) - and JSON body equal to
- { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
-(9) - with header `Content-Type` equal to `application/json`
-
-From the Producer perspective, in the autogenerated producer-side test:
-
-(1) - A request will be sent to the producer
-(2) - With the "PUT" method
-(3) - to the URL "/fraudcheck"
-(4) - with the JSON body that
- * has a field `client.id` that will have a generated value that matches a regular expression `[0-9]{10}`
- * has a field `loanAmount` that is equal to `99999`
-(5) - with header `Content-Type` equal to `application/json`
-(6) - then the test will assert if the response has been sent with
-(7) - status equal `200`
-(8) - and JSON body equal to
- { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
-(9) - with header `Content-Type` matching `application/json.*`
- */</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request: # (1)
-  method: PUT # (2)
-  url: /fraudcheck # (3)
-  body: # (4)
-    "client.id": 1234567890
-    loanAmount: 99999
-  headers: # (5)
-    Content-Type: application/json
-  matchers:
-    body:
-      - path: $.['client.id'] # (6)
-        type: by_regex
-        value: "[0-9]{10}"
-response: # (7)
-  status: 200 # (8)
-  body:  # (9)
-    fraudCheckStatus: "FRAUD"
-    "rejection.reason": "Amount too high"
-  headers: # (10)
-    Content-Type: application/json
-
-
-#From the Consumer perspective, when shooting a request in the integration test:
-#
-#(1) - If the consumer sends a request
-#(2) - With the "PUT" method
-#(3) - to the URL "/fraudcheck"
-#(4) - with the JSON body that
-# * has a field `client.id`
-# * has a field `loanAmount` that is equal to `99999`
-#(5) - with header `Content-Type` equal to `application/json`
-#(6) - and a `client.id` json entry matches the regular expression `[0-9]{10}`
-#(7) - then the response will be sent with
-#(8) - status equal `200`
-#(9) - and JSON body equal to
-# { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
-#(10) - with header `Content-Type` equal to `application/json`
-#
-#From the Producer perspective, in the autogenerated producer-side test:
-#
-#(1) - A request will be sent to the producer
-#(2) - With the "PUT" method
-#(3) - to the URL "/fraudcheck"
-#(4) - with the JSON body that
-# * has a field `client.id` `1234567890`
-# * has a field `loanAmount` that is equal to `99999`
-#(5) - with header `Content-Type` equal to `application/json`
-#(7) - then the test will assert if the response has been sent with
-#(8) - status equal `200`
-#(9) - and JSON body equal to
-# { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
-#(10) - with header `Content-Type` equal to `application/json`</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The YML contract is quite straight-forward. However when you take a look at the Contract
-written using a statically typed Groovy DSL - you might wonder what the
-<code>value(client(&#8230;&#8203;), server(&#8230;&#8203;))</code> parts are. By using this notation, Spring Cloud
-Contract lets you define parts of a JSON block, a URL, etc., which are dynamic. In case
-of an identifier or a timestamp, you need not hardcode a value. You want to allow some
-different ranges of values. To enable ranges of values, you can set regular expressions
-matching those values for the consumer side. You can provide the body by means of either
-a map notation or String with interpolations.
-Consult the <a href="#contract-dsl">Contract DSL</a> section for more information. We highly recommend using the map notation!</p>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-You must understand the map notation in order to set up contracts. Please read the
-<a href="https://groovy-lang.org/json.html">Groovy docs regarding JSON</a>.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>The previously shown contract is an agreement between two sides that:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>if an HTTP request is sent with all of</p>
-<div class="ulist">
-<ul>
-<li>
-<p>a <code>PUT</code> method on the <code>/fraudcheck</code> endpoint,</p>
-</li>
-<li>
-<p>a JSON body with a <code>client.id</code> that matches the regular expression <code>[0-9]{10}</code> and
-<code>loanAmount</code> equal to <code>99999</code>,</p>
-</li>
-<li>
-<p>and a <code>Content-Type</code> header with a value of <code>application/vnd.fraud.v1+json</code>,</p>
-</li>
-</ul>
-</div>
-</li>
-<li>
-<p>then an HTTP response is sent to the consumer that</p>
-<div class="ulist">
-<ul>
-<li>
-<p>has status <code>200</code>,</p>
-</li>
-<li>
-<p>contains a JSON body with the <code>fraudCheckStatus</code> field containing a value <code>FRAUD</code> and
-the <code>rejectionReason</code> field having value <code>Amount too high</code>,</p>
-</li>
-<li>
-<p>and a <code>Content-Type</code> header with a value of <code>application/vnd.fraud.v1+json</code>.</p>
-</li>
-</ul>
-</div>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Once you are ready to check the API in practice in the integration tests, you need to
-install the stubs locally.</p>
-</div>
-<div class="paragraph">
-<p><strong>Add the Spring Cloud Contract Verifier plugin.</strong></p>
-</div>
-<div class="paragraph">
-<p>We can add either a Maven or a Gradle plugin. In this example, you see how to add Maven.
-First, add the <code>Spring Cloud Contract</code> BOM.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependencyManagement&gt;
-	&lt;dependencies&gt;
-		&lt;dependency&gt;
-			&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-			&lt;artifactId&gt;spring-cloud-dependencies&lt;/artifactId&gt;
-			&lt;version&gt;${spring-cloud-release.version}&lt;/version&gt;
-			&lt;type&gt;pom&lt;/type&gt;
-			&lt;scope&gt;import&lt;/scope&gt;
-		&lt;/dependency&gt;
-	&lt;/dependencies&gt;
-&lt;/dependencyManagement&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Next, add the <code>Spring Cloud Contract Verifier</code> Maven plugin</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-	&lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-	&lt;extensions&gt;true&lt;/extensions&gt;
-	&lt;configuration&gt;
-		&lt;packageWithBaseClasses&gt;com.example.fraud&lt;/packageWithBaseClasses&gt;
-		&lt;convertToYaml&gt;true&lt;/convertToYaml&gt;
-	&lt;/configuration&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Since the plugin was added, you get the <code>Spring Cloud Contract Verifier</code> features which,
-from the provided contracts:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>generate and run tests</p>
-</li>
-<li>
-<p>produce and install stubs</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>You do not want to generate tests since you, as the consumer, want only to play with the
-stubs. You need to skip the test generation and execution. When you execute:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ cd local-http-server-repo
-$ ./mvnw clean install -DskipTests</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In the logs, you see something like this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">[INFO] --- spring-cloud-contract-maven-plugin:1.0.0.BUILD-SNAPSHOT:generateStubs (default-generateStubs) @ http-server ---
-[INFO] Building jar: /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar
-[INFO]
-[INFO] --- maven-jar-plugin:2.6:jar (default-jar) @ http-server ---
-[INFO] Building jar: /some/path/http-server/target/http-server-0.0.1-SNAPSHOT.jar
-[INFO]
-[INFO] --- spring-boot-maven-plugin:1.5.5.BUILD-SNAPSHOT:repackage (default) @ http-server ---
-[INFO]
-[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ http-server ---
-[INFO] Installing /some/path/http-server/target/http-server-0.0.1-SNAPSHOT.jar to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT.jar
-[INFO] Installing /some/path/http-server/pom.xml to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT.pom
-[INFO] Installing /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following line is extremely important:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">[INFO] Installing /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>It confirms that the stubs of the <code>http-server</code> have been installed in the local
-repository.</p>
-</div>
-<div class="paragraph">
-<p><strong>Run the integration tests.</strong></p>
-</div>
-<div class="paragraph">
-<p>In order to profit from the Spring Cloud Contract Stub Runner functionality of automatic
-stub downloading, you must do the following in your consumer side project (<code>Loan
-Application service</code>):</p>
-</div>
-<div class="paragraph">
-<p>Add the <code>Spring Cloud Contract</code> BOM:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependencyManagement&gt;
-	&lt;dependencies&gt;
-		&lt;dependency&gt;
-			&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-			&lt;artifactId&gt;spring-cloud-dependencies&lt;/artifactId&gt;
-			&lt;version&gt;${spring-cloud-release-train.version}&lt;/version&gt;
-			&lt;type&gt;pom&lt;/type&gt;
-			&lt;scope&gt;import&lt;/scope&gt;
-		&lt;/dependency&gt;
-	&lt;/dependencies&gt;
-&lt;/dependencyManagement&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Add the dependency to <code>Spring Cloud Contract Stub Runner</code>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-starter-contract-stub-runner&lt;/artifactId&gt;
-	&lt;scope&gt;test&lt;/scope&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Annotate your test class with <code>@AutoConfigureStubRunner</code>. In the annotation, provide the
-<code>group-id</code> and <code>artifact-id</code> for the Stub Runner to download the stubs of your
-collaborators. (Optional step) Because you&#8217;re playing with the collaborators offline, you
-can also provide the offline work switch (<code>StubRunnerProperties.StubsMode.LOCAL</code>).</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@RunWith(SpringRunner.class)
-@SpringBootTest(webEnvironment = WebEnvironment.NONE)
-@AutoConfigureStubRunner(ids = {
-		"com.example:http-server-dsl:+:stubs:6565" }, stubsMode = StubRunnerProperties.StubsMode.LOCAL)
-public class LoanApplicationServiceTests {</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Now, when you run your tests, you see something like this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">2016-07-19 14:22:25.403  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Desired version is + - will try to resolve the latest version
-2016-07-19 14:22:25.438  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Resolved version is 0.0.1-SNAPSHOT
-2016-07-19 14:22:25.439  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Resolving artifact com.example:http-server:jar:stubs:0.0.1-SNAPSHOT using remote repositories []
-2016-07-19 14:22:25.451  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Resolved artifact com.example:http-server:jar:stubs:0.0.1-SNAPSHOT to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar
-2016-07-19 14:22:25.465  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Unpacking stub from JAR [URI: file:/path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar]
-2016-07-19 14:22:25.475  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Unpacked file to [/var/folders/0p/xwq47sq106x1_g3dtv6qfm940000gq/T/contracts100276532569594265]
-2016-07-19 14:22:27.737  INFO 41050 --- [           main] o.s.c.c.stubrunner.StubRunnerExecutor    : All stubs are now running RunningStubs [namesAndPorts={com.example:http-server:0.0.1-SNAPSHOT:stubs=8080}]</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>This output means that Stub Runner has found your stubs and started a server for your app
-with group id <code>com.example</code>, artifact id <code>http-server</code> with version <code>0.0.1-SNAPSHOT</code> of
-the stubs and with <code>stubs</code> classifier on port <code>8080</code>.</p>
-</div>
-<div class="paragraph">
-<p><strong>File a pull request.</strong></p>
-</div>
-<div class="paragraph">
-<p>What you have done until now is an iterative process. You can play around with the
-contract, install it locally, and work on the consumer side until the contract works as
-you wish.</p>
-</div>
-<div class="paragraph">
-<p>Once you are satisfied with the results and the test passes, publish a pull request to
-the server side. Currently, the consumer side work is done.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_producer_side_fraud_detection_server"><a class="link" href="#_producer_side_fraud_detection_server">2.5.3. Producer side (Fraud Detection server)</a></h4>
-<div class="paragraph">
-<p>As a developer of the Fraud Detection server (a server to the Loan Issuance service):</p>
-</div>
-<div class="paragraph">
-<p><strong>Create an initial implementation.</strong></p>
-</div>
-<div class="paragraph">
-<p>As a reminder, you can see the initial implementation here:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RequestMapping(value = "/fraudcheck", method = PUT)
-public FraudCheckResult fraudCheck(@RequestBody FraudCheck fraudCheck) {
-return new FraudCheckResult(FraudCheckStatus.OK, NO_REASON);
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><strong>Take over the pull request.</strong></p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ git checkout -b contract-change-pr master
-$ git pull https://your-git-server.com/server-side-fork.git contract-change-pr</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You must add the dependencies needed by the autogenerated tests:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-starter-contract-verifier&lt;/artifactId&gt;
-	&lt;scope&gt;test&lt;/scope&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In the configuration of the Maven plugin, pass the <code>packageWithBaseClasses</code> property</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-	&lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-	&lt;extensions&gt;true&lt;/extensions&gt;
-	&lt;configuration&gt;
-		&lt;packageWithBaseClasses&gt;com.example.fraud&lt;/packageWithBaseClasses&gt;
-		&lt;convertToYaml&gt;true&lt;/convertToYaml&gt;
-	&lt;/configuration&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-This example uses "convention based" naming by setting the
-<code>packageWithBaseClasses</code> property. Doing so means that the two last packages combine to
-make the name of the base test class. In our case, the contracts were placed under
-<code>src/test/resources/contracts/fraud</code>. Since you do not have two packages starting from
-the <code>contracts</code> folder, pick only one, which should be <code>fraud</code>. Add the <code>Base</code> suffix and
-capitalize <code>fraud</code>. That gives you the <code>FraudBase</code> test class name.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>All the generated tests extend that class. Over there, you can set up your Spring Context
-or whatever is necessary. In this case, use <a href="https://github.com/rest-assured/rest-assured">Rest Assured MVC</a> to
-start the server side <code>FraudDetectionController</code>.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">/*
- * Copyright 2013-2019 the original author or authors.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *      https://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
-package com.example.fraud;
-
-import io.restassured.module.mockmvc.RestAssuredMockMvc;
-import org.junit.Before;
-
-public class FraudBase {
-
-	@Before
-	public void setup() {
-		RestAssuredMockMvc.standaloneSetup(new FraudDetectionController(),
-				new FraudStatsController(stubbedStatsProvider()));
-	}
-
-	private StatsProvider stubbedStatsProvider() {
-		return fraudType -&gt; {
-			switch (fraudType) {
-			case DRUNKS:
-				return 100;
-			case ALL:
-				return 200;
-			}
-			return 0;
-		};
-	}
-
-	public void assertThatRejectionReasonIsNull(Object rejectionReason) {
-		assert rejectionReason == null;
-	}
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Now, if you run the <code>./mvnw clean install</code>, you get something like this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">Results :
-
-Tests in error:
-  ContractVerifierTest.validate_shouldMarkClientAsFraud:32 » IllegalState Parsed...</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>This error occurs because you have a new contract from which a test was generated and it
-failed since you have not implemented the feature. The auto-generated test would look
-like this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Test
-public void validate_shouldMarkClientAsFraud() throws Exception {
-    // given:
-        MockMvcRequestSpecification request = given()
-                .header("Content-Type", "application/vnd.fraud.v1+json")
-                .body("{\"client.id\":\"1234567890\",\"loanAmount\":99999}");
-
-    // when:
-        ResponseOptions response = given().spec(request)
-                .put("/fraudcheck");
-
-    // then:
-        assertThat(response.statusCode()).isEqualTo(200);
-        assertThat(response.header("Content-Type")).matches("application/vnd.fraud.v1.json.*");
-    // and:
-        DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
-        assertThatJson(parsedJson).field("['fraudCheckStatus']").matches("[A-Z]{5}");
-        assertThatJson(parsedJson).field("['rejection.reason']").isEqualTo("Amount too high");
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>If you used the Groovy DSL, you can see, all the <code>producer()</code> parts of the Contract that were present in the
-<code>value(consumer(&#8230;&#8203;), producer(&#8230;&#8203;))</code> blocks got injected into the test.
-In case of using YAML, the same applied for the <code>matchers</code> sections of the <code>response</code>.</p>
-</div>
-<div class="paragraph">
-<p>Note that, on the producer side, you are also doing TDD. The expectations are expressed
-in the form of a test. This test sends a request to our own application with the URL,
-headers, and body defined in the contract. It also is expecting precisely defined values
-in the response. In other words, you have the <code>red</code> part of <code>red</code>, <code>green</code>, and
-<code>refactor</code>. It is time to convert the <code>red</code> into the <code>green</code>.</p>
-</div>
-<div class="paragraph">
-<p><strong>Write the missing implementation.</strong></p>
-</div>
-<div class="paragraph">
-<p>Because you know the expected input and expected output, you can write the missing
-implementation:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RequestMapping(value = "/fraudcheck", method = PUT)
-public FraudCheckResult fraudCheck(@RequestBody FraudCheck fraudCheck) {
-if (amountGreaterThanThreshold(fraudCheck)) {
-	return new FraudCheckResult(FraudCheckStatus.FRAUD, AMOUNT_TOO_HIGH);
-}
-return new FraudCheckResult(FraudCheckStatus.OK, NO_REASON);
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>When you execute <code>./mvnw clean install</code> again, the tests pass. Since the <code>Spring Cloud
-Contract Verifier</code> plugin adds the tests to the <code>generated-test-sources</code>, you can
-actually run those tests from your IDE.</p>
-</div>
-<div class="paragraph">
-<p><strong>Deploy your app.</strong></p>
-</div>
-<div class="paragraph">
-<p>Once you finish your work, you can deploy your change. First, merge the branch:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ git checkout master
-$ git merge --no-ff contract-change-pr
-$ git push origin master</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Your CI might run something like <code>./mvnw clean deploy</code>, which would publish both the
-application and the stub artifacts.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_consumer_side_loan_issuance_final_step"><a class="link" href="#_consumer_side_loan_issuance_final_step">2.5.4. Consumer Side (Loan Issuance) Final Step</a></h4>
-<div class="paragraph">
-<p>As a developer of the Loan Issuance service (a consumer of the Fraud Detection server):</p>
-</div>
-<div class="paragraph">
-<p><strong>Merge branch to master.</strong></p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ git checkout master
-$ git merge --no-ff contract-change-pr</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><strong>Work online.</strong></p>
-</div>
-<div class="paragraph">
-<p>Now you can disable the offline work for Spring Cloud Contract Stub Runner and indicate
-where the repository with your stubs is located. At this moment the stubs of the server
-side are automatically downloaded from Nexus/Artifactory. You can set the value of
-<code>stubsMode</code> to <code>REMOTE</code>. The following code shows an example of
-achieving the same thing by changing the properties.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">stubrunner:
-  ids: 'com.example:http-server-dsl:+:stubs:8080'
-  repositoryRoot: https://repo.spring.io/libs-snapshot</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>That&#8217;s it!</p>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_dependencies"><a class="link" href="#_dependencies">2.6. Dependencies</a></h3>
-<div class="paragraph">
-<p>The best way to add dependencies is to use the proper <code>starter</code> dependency.</p>
-</div>
-<div class="paragraph">
-<p>For <code>stub-runner</code>, use <code>spring-cloud-starter-stub-runner</code>. When you use a plugin, add
-<code>spring-cloud-starter-contract-verifier</code>.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_additional_links"><a class="link" href="#_additional_links">2.7. Additional Links</a></h3>
-<div class="paragraph">
-<p>Here are some resources related to Spring Cloud Contract Verifier and Stub Runner. Note
-that some may be outdated, because the Spring Cloud Contract Verifier project is under
-constant development.</p>
-</div>
-<div class="sect3">
-<h4 id="_spring_cloud_contract_video"><a class="link" href="#_spring_cloud_contract_video">2.7.1. Spring Cloud Contract video</a></h4>
-<div class="paragraph">
-<p>You can check out the video from the Warsaw JUG about Spring Cloud Contract:</p>
-</div>
-<div class="videoblock">
-<div class="content">
-<iframe width="640" height="480" src="https://www.youtube.com/embed/sAAklvxmPmk?rel=0&amp;start=538" frameborder="0" allowfullscreen></iframe>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_readings"><a class="link" href="#_readings">2.7.2. Readings</a></h4>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="https://www.slideshare.net/MarcinGrzejszczak/stick-to-the-rules-consumer-driven-contracts-201507-confitura">Slides from Marcin Grzejszczak&#8217;s talk about Accurest</a></p>
-</li>
-<li>
-<p><a href="https://toomuchcoding.com/blog/categories/accurest/">Accurest related articles from Marcin Grzejszczak&#8217;s blog</a></p>
-</li>
-<li>
-<p><a href="https://toomuchcoding.com/blog/categories/spring-cloud-contract/">Spring Cloud Contract related articles from Marcin Grzejszczak&#8217;s blog</a></p>
-</li>
-<li>
-<p><a href="https://groovy-lang.org/json.html">Groovy docs regarding JSON</a></p>
-</li>
-</ul>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_samples"><a class="link" href="#_samples">2.8. Samples</a></h3>
-<div class="paragraph">
-<p>You can find some samples at
-<a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples">samples</a>.</p>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_spring_cloud_contract_faq"><a class="link" href="#_spring_cloud_contract_faq">3. Spring Cloud Contract FAQ</a></h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_why_use_spring_cloud_contract_verifier_and_not_x"><a class="link" href="#_why_use_spring_cloud_contract_verifier_and_not_x">3.1. Why use Spring Cloud Contract Verifier and not X ?</a></h3>
-<div class="paragraph">
-<p>For the time being Spring Cloud Contract is a JVM based tool. So it could be your first pick when you&#8217;re already creating
-software for the JVM. This project has a lot of really interesting features but especially quite a few of them definitely make
-Spring Cloud Contract Verifier stand out on the "market" of Consumer Driven Contract (CDC) tooling. Out of many the most interesting are:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Possibility to do CDC with messaging</p>
-</li>
-<li>
-<p>Clear and easy to use, statically typed DSL</p>
-</li>
-<li>
-<p>Possibility to copy paste your current JSON file to the contract and only edit its elements</p>
-</li>
-<li>
-<p>Automatic generation of tests from the defined Contract</p>
-</li>
-<li>
-<p>Stub Runner functionality - the stubs are automatically downloaded at runtime from Nexus / Artifactory</p>
-</li>
-<li>
-<p>Spring Cloud integration - no discovery service is needed for integration tests</p>
-</li>
-<li>
-<p>Spring Cloud Contract integrates with Pact out of the box and provides easy hooks to extend its functionality</p>
-</li>
-<li>
-<p>Via Docker adds support for any language &amp; framework used</p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_i_dont_want_to_write_a_contract_in_groovy"><a class="link" href="#_i_dont_want_to_write_a_contract_in_groovy">3.2. I don&#8217;t want to write a contract in Groovy!</a></h3>
-<div class="paragraph">
-<p>No problem. You can write a contract in YAML!</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_what_is_this_valueconsumer_producer"><a class="link" href="#_what_is_this_valueconsumer_producer">3.3. What is this value(consumer(), producer()) ?</a></h3>
-<div class="paragraph">
-<p>One of the biggest challenges related to stubs is their reusability. Only if they can be vastly used, will they serve their purpose.
-What typically makes that difficult are the hard-coded values of request / response elements. For example dates or ids.
-Imagine the following JSON request</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
-    "time" : "2016-10-10 20:10:15",
-    "id" : "9febab1c-6f36-4a0b-88d6-3b6a6d81cd4a",
-    "body" : "foo"
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>and JSON response</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
-    "time" : "2016-10-10 21:10:15",
-    "id" : "c4231e1f-3ca9-48d3-b7e7-567d55f0d051",
-    "body" : "bar"
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Imagine the pain required to set proper value of the <code>time</code> field (let&#8217;s assume that this content is generated by the
-database) by changing the clock in the system or providing stub implementations of data providers. The same is related
-to the field called <code>id</code>. Will you create a stubbed implementation of UUID generator? Makes little sense&#8230;&#8203;</p>
-</div>
-<div class="paragraph">
-<p>So as a consumer you would like to send a request that matches any form of a time or any UUID. That way your system
-will work as usual - will generate data and you won&#8217;t have to stub anything out. Let&#8217;s assume that in case of the aforementioned
-JSON the most important part is the <code>body</code> field. You can focus on that and provide matching for other fields. In other words
-you would like the stub to work like this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
-    "time" : "SOMETHING THAT MATCHES TIME",
-    "id" : "SOMETHING THAT MATCHES UUID",
-    "body" : "foo"
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>As far as the response goes as a consumer you need a concrete value that you can operate on. So such a JSON is valid</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
-    "time" : "2016-10-10 21:10:15",
-    "id" : "c4231e1f-3ca9-48d3-b7e7-567d55f0d051",
-    "body" : "bar"
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>As you could see in the previous sections we generate tests from contracts. So from the producer&#8217;s side the situation looks
-much different. We&#8217;re parsing the provided contract and in the test we want to send a real request to your endpoints.
-So for the case of a producer for the request we can&#8217;t have any sort of matching. We need concrete values that the
-producer&#8217;s backend can work on. Such a JSON would be a valid one:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
-    "time" : "2016-10-10 20:10:15",
-    "id" : "9febab1c-6f36-4a0b-88d6-3b6a6d81cd4a",
-    "body" : "foo"
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>On the other hand from the point of view of the validity of the contract the response doesn&#8217;t necessarily have to
-contain concrete values of <code>time</code> or <code>id</code>. Let&#8217;s say that you generate those on the producer side - again, you&#8217;d
-have to do a lot of stubbing to ensure that you always return the same values. That&#8217;s why from the producer&#8217;s side
-what you might want is the following response:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
-    "time" : "SOMETHING THAT MATCHES TIME",
-    "id" : "SOMETHING THAT MATCHES UUID",
-    "body" : "bar"
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>How can you then provide one time a matcher for the consumer and a concrete value for the producer and vice versa?
-In Spring Cloud Contract we&#8217;re allowing you to provide a <strong>dynamic value</strong>. That means that it can differ for both
-sides of the communication. You can pass the values:</p>
-</div>
-<div class="paragraph">
-<p>Either via the <code>value</code> method</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">value(consumer(...), producer(...))
-value(stub(...), test(...))
-value(client(...), server(...))</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>or using the <code>$()</code> method</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">$(consumer(...), producer(...))
-$(stub(...), test(...))
-$(client(...), server(...))</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You can read more about this in the <a href="#contract-dsl">Contract DSL</a> section.</p>
-</div>
-<div class="paragraph">
-<p>Calling <code>value()</code> or <code>$()</code> tells Spring Cloud Contract that you will be passing a dynamic value.
-Inside the <code>consumer()</code> method you pass the value that should be used on the consumer side (in the generated stub).
-Inside the <code>producer()</code> method you pass the value that should be used on the producer side (in the generated test).</p>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-If on one side you have passed the regular expression and you haven&#8217;t passed the other, then the
-other side will get auto-generated.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>Most often you will use that method together with the <code>regex</code> helper method. E.g. <code>consumer(regex('[0-9]{10}'))</code>.</p>
-</div>
-<div class="paragraph">
-<p>To sum it up the contract for the aforementioned scenario would look more or less like this (the regular expression
-for time and UUID are simplified and most likely invalid but we want to keep things very simple in this example):</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-				request {
-					method 'GET'
-					url '/someUrl'
-					body([
-					    time : value(consumer(regex('[0-9]{4}-[0-9]{2}-[0-9]{2} [0-2][0-9]-[0-5][0-9]-[0-5][0-9]')),
-					    id: value(consumer(regex('[0-9a-zA-z]{8}-[0-9a-zA-z]{4}-[0-9a-zA-z]{4}-[0-9a-zA-z]{12}'))
-					    body: "foo"
-					])
-				}
-			response {
-				status OK()
-				body([
-					    time : value(producer(regex('[0-9]{4}-[0-9]{2}-[0-9]{2} [0-2][0-9]-[0-5][0-9]-[0-5][0-9]')),
-					    id: value([producer(regex('[0-9a-zA-z]{8}-[0-9a-zA-z]{4}-[0-9a-zA-z]{4}-[0-9a-zA-z]{12}'))
-					    body: "bar"
-					])
-			}
-}</code></pre>
-</div>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-Please read the <a href="https://groovy-lang.org/json.html">Groovy docs related to JSON</a> to understand how to
-properly structure the request / response bodies.
-</td>
-</tr>
-</table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_how_to_do_stubs_versioning"><a class="link" href="#_how_to_do_stubs_versioning">3.4. How to do Stubs versioning?</a></h3>
-<div class="sect3">
-<h4 id="_api_versioning"><a class="link" href="#_api_versioning">3.4.1. API Versioning</a></h4>
-<div class="paragraph">
-<p>Let&#8217;s try to answer a question what versioning really means. If you&#8217;re referring to the API version then there are
-different approaches.</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>use Hypermedia, links and do not version your API by any means</p>
-</li>
-<li>
-<p>pass versions through headers / urls</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>I will not try to answer a question which approach is better. Whatever suits your needs and allows you to generate
-business value should be picked.</p>
-</div>
-<div class="paragraph">
-<p>Let&#8217;s assume that you do version your API. In that case you should provide as many contracts as many versions you support.
-You can create a subfolder for every version or append it to the contract name - whatever suits you more.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_jar_versioning"><a class="link" href="#_jar_versioning">3.4.2. JAR versioning</a></h4>
-<div class="paragraph">
-<p>If by versioning you mean the version of the JAR that contains the stubs then there are essentially two main approaches.</p>
-</div>
-<div class="paragraph">
-<p>Let&#8217;s assume that you&#8217;re doing Continuous Delivery / Deployment which means that you&#8217;re generating a new version of
-the jar each time you go through the pipeline and that jar can go to production at any time. For example your jar version
-looks like this (it got built on the 20.10.2016 at 20:15:21) :</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">1.0.0.20161020-201521-RELEASE</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In that case your generated stub jar will look like this.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">1.0.0.20161020-201521-RELEASE-stubs.jar</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In this case you should inside your <code>application.yml</code> or <code>@AutoConfigureStubRunner</code> when referencing stubs provide the
- latest version of the stubs. You can do that by passing the <code>+</code> sign. Example</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(ids = {"com.example:http-server-dsl:+:stubs:8080"})</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>If the versioning however is fixed (e.g. <code>1.0.4.RELEASE</code> or <code>2.1.1</code>) then you have to set the concrete value of the jar
-version. Example for 2.1.1.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(ids = {"com.example:http-server-dsl:2.1.1:stubs:8080"})</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_dev_or_prod_stubs"><a class="link" href="#_dev_or_prod_stubs">3.4.3. Dev or prod stubs</a></h4>
-<div class="paragraph">
-<p>You can manipulate the classifier to run the tests against current development version of the stubs of other services
- or the ones that were deployed to production. If you alter your build to deploy the stubs with the <code>prod-stubs</code> classifier
- once you reach production deployment then you can run tests in one case with dev stubs and one with prod stubs.</p>
-</div>
-<div class="paragraph">
-<p>Example of tests using development version of stubs</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(ids = {"com.example:http-server-dsl:+:stubs:8080"})</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Example of tests using production version of stubs</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(ids = {"com.example:http-server-dsl:+:prod-stubs:8080"})</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You can pass those values also via properties from your deployment pipeline.</p>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_common_repo_with_contracts"><a class="link" href="#_common_repo_with_contracts">3.5. Common repo with contracts</a></h3>
-<div class="paragraph">
-<p>Another way of storing contracts other than having them with the producer is keeping them in a common place.
-It can be related to security issues where the consumers can&#8217;t clone the producer&#8217;s code. Also if you keep
-contracts in a single place then you, as a producer, will know how many consumers you have and which
-consumer you will break with your local changes.</p>
-</div>
-<div class="sect3">
-<h4 id="_repo_structure"><a class="link" href="#_repo_structure">3.5.1. Repo structure</a></h4>
-<div class="paragraph">
-<p>Let&#8217;s assume that we have a producer with coordinates <code>com.example:server</code> and 3 consumers: <code>client1</code>,
-<code>client2</code>, <code>client3</code>. Then in the repository with common contracts you would have the following setup
-(which you can checkout <a href="https://github.com/spring-cloud/spring-cloud-contract/tree/master/samples/standalone/contracts">here</a>):</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── com
-│   └── example
-│       └── server
-│           ├── client1
-│           │   └── expectation.groovy
-│           ├── client2
-│           │   └── expectation.groovy
-│           ├── client3
-│           │   └── expectation.groovy
-│           └── pom.xml
-├── mvnw
-├── mvnw.cmd
-├── pom.xml
-└── src
-    └── assembly
-        └── contracts.xml</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>As you can see under the slash-delimited groupid <code>/</code> artifact id folder (<code>com/example/server</code>) you have
-expectations of the 3 consumers (<code>client1</code>, <code>client2</code> and <code>client3</code>). Expectations are the standard Groovy DSL
-contract files as described throughout this documentation. This repository has to produce a JAR file that maps
-one to one to the contents of the repo.</p>
-</div>
-<div class="paragraph">
-<p>Example of a <code>pom.xml</code> inside the <code>server</code> folder.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;project xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-		 xmlns="http://maven.apache.org/POM/4.0.0"
-		 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd"&gt;
-	&lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
-
-	&lt;groupId&gt;com.example&lt;/groupId&gt;
-	&lt;artifactId&gt;server&lt;/artifactId&gt;
-	&lt;version&gt;0.0.1-SNAPSHOT&lt;/version&gt;
-
-	&lt;name&gt;Server Stubs&lt;/name&gt;
-	&lt;description&gt;POM used to install locally stubs for consumer side&lt;/description&gt;
-
-	&lt;parent&gt;
-		&lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
-		&lt;artifactId&gt;spring-boot-starter-parent&lt;/artifactId&gt;
-		&lt;version&gt;2.2.0.BUILD-SNAPSHOT&lt;/version&gt;
-		&lt;relativePath/&gt;
-	&lt;/parent&gt;
-
-	&lt;properties&gt;
-		&lt;project.build.sourceEncoding&gt;UTF-8&lt;/project.build.sourceEncoding&gt;
-		&lt;java.version&gt;1.8&lt;/java.version&gt;
-		&lt;spring-cloud-contract.version&gt;2.2.0.BUILD-SNAPSHOT&lt;/spring-cloud-contract.version&gt;
-		&lt;spring-cloud-release.version&gt;Hoxton.BUILD-SNAPSHOT&lt;/spring-cloud-release.version&gt;
-		&lt;excludeBuildFolders&gt;true&lt;/excludeBuildFolders&gt;
-	&lt;/properties&gt;
-
-	&lt;dependencyManagement&gt;
-		&lt;dependencies&gt;
-			&lt;dependency&gt;
-				&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-				&lt;artifactId&gt;spring-cloud-dependencies&lt;/artifactId&gt;
-				&lt;version&gt;${spring-cloud-release.version}&lt;/version&gt;
-				&lt;type&gt;pom&lt;/type&gt;
-				&lt;scope&gt;import&lt;/scope&gt;
-			&lt;/dependency&gt;
-		&lt;/dependencies&gt;
-	&lt;/dependencyManagement&gt;
-
-	&lt;build&gt;
-		&lt;plugins&gt;
-			&lt;plugin&gt;
-				&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-				&lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-				&lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-				&lt;extensions&gt;true&lt;/extensions&gt;
-				&lt;configuration&gt;
-					&lt;!-- By default it would search under src/test/resources/ --&gt;
-					&lt;contractsDirectory&gt;${project.basedir}&lt;/contractsDirectory&gt;
-				&lt;/configuration&gt;
-			&lt;/plugin&gt;
-		&lt;/plugins&gt;
-	&lt;/build&gt;
-
-	&lt;repositories&gt;
-		&lt;repository&gt;
-			&lt;id&gt;spring-snapshots&lt;/id&gt;
-			&lt;name&gt;Spring Snapshots&lt;/name&gt;
-			&lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
-			&lt;snapshots&gt;
-				&lt;enabled&gt;true&lt;/enabled&gt;
-			&lt;/snapshots&gt;
-		&lt;/repository&gt;
-		&lt;repository&gt;
-			&lt;id&gt;spring-milestones&lt;/id&gt;
-			&lt;name&gt;Spring Milestones&lt;/name&gt;
-			&lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
-			&lt;snapshots&gt;
-				&lt;enabled&gt;false&lt;/enabled&gt;
-			&lt;/snapshots&gt;
-		&lt;/repository&gt;
-		&lt;repository&gt;
-			&lt;id&gt;spring-releases&lt;/id&gt;
-			&lt;name&gt;Spring Releases&lt;/name&gt;
-			&lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
-			&lt;snapshots&gt;
-				&lt;enabled&gt;false&lt;/enabled&gt;
-			&lt;/snapshots&gt;
-		&lt;/repository&gt;
-	&lt;/repositories&gt;
-	&lt;pluginRepositories&gt;
-		&lt;pluginRepository&gt;
-			&lt;id&gt;spring-snapshots&lt;/id&gt;
-			&lt;name&gt;Spring Snapshots&lt;/name&gt;
-			&lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
-			&lt;snapshots&gt;
-				&lt;enabled&gt;true&lt;/enabled&gt;
-			&lt;/snapshots&gt;
-		&lt;/pluginRepository&gt;
-		&lt;pluginRepository&gt;
-			&lt;id&gt;spring-milestones&lt;/id&gt;
-			&lt;name&gt;Spring Milestones&lt;/name&gt;
-			&lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
-			&lt;snapshots&gt;
-				&lt;enabled&gt;false&lt;/enabled&gt;
-			&lt;/snapshots&gt;
-		&lt;/pluginRepository&gt;
-		&lt;pluginRepository&gt;
-			&lt;id&gt;spring-releases&lt;/id&gt;
-			&lt;name&gt;Spring Releases&lt;/name&gt;
-			&lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
-			&lt;snapshots&gt;
-				&lt;enabled&gt;false&lt;/enabled&gt;
-			&lt;/snapshots&gt;
-		&lt;/pluginRepository&gt;
-	&lt;/pluginRepositories&gt;
-
-&lt;/project&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>As you can see there are no dependencies other than the Spring Cloud Contract Maven Plugin.
-Those poms are necessary for the consumer side to run <code>mvn clean install -DskipTests</code> to locally install
- stubs of the producer project.</p>
-</div>
-<div class="paragraph">
-<p>The <code>pom.xml</code> in the root folder can look like this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;project xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-		 xmlns="http://maven.apache.org/POM/4.0.0"
-		 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd"&gt;
-	&lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
-
-	&lt;groupId&gt;com.example.standalone&lt;/groupId&gt;
-	&lt;artifactId&gt;contracts&lt;/artifactId&gt;
-	&lt;version&gt;0.0.1-SNAPSHOT&lt;/version&gt;
-
-	&lt;name&gt;Contracts&lt;/name&gt;
-	&lt;description&gt;Contains all the Spring Cloud Contracts, well, contracts. JAR used by the
-		producers to generate tests and stubs
-	&lt;/description&gt;
-
-	&lt;properties&gt;
-		&lt;project.build.sourceEncoding&gt;UTF-8&lt;/project.build.sourceEncoding&gt;
-	&lt;/properties&gt;
-
-	&lt;build&gt;
-		&lt;plugins&gt;
-			&lt;plugin&gt;
-				&lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
-				&lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
-				&lt;executions&gt;
-					&lt;execution&gt;
-						&lt;id&gt;contracts&lt;/id&gt;
-						&lt;phase&gt;prepare-package&lt;/phase&gt;
-						&lt;goals&gt;
-							&lt;goal&gt;single&lt;/goal&gt;
-						&lt;/goals&gt;
-						&lt;configuration&gt;
-							&lt;attach&gt;true&lt;/attach&gt;
-							&lt;descriptor&gt;${basedir}/src/assembly/contracts.xml&lt;/descriptor&gt;
-							&lt;!-- If you want an explicit classifier remove the following line --&gt;
-							&lt;appendAssemblyId&gt;false&lt;/appendAssemblyId&gt;
-						&lt;/configuration&gt;
-					&lt;/execution&gt;
-				&lt;/executions&gt;
-			&lt;/plugin&gt;
-		&lt;/plugins&gt;
-	&lt;/build&gt;
-
-&lt;/project&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>It&#8217;s using the assembly plugin in order to build the JAR with all the contracts. Example of such setup is here:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;assembly xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-		  xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3"
-		  xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3 https://maven.apache.org/xsd/assembly-1.1.3.xsd"&gt;
-	&lt;id&gt;project&lt;/id&gt;
-	&lt;formats&gt;
-		&lt;format&gt;jar&lt;/format&gt;
-	&lt;/formats&gt;
-	&lt;includeBaseDirectory&gt;false&lt;/includeBaseDirectory&gt;
-	&lt;fileSets&gt;
-		&lt;fileSet&gt;
-			&lt;directory&gt;${project.basedir}&lt;/directory&gt;
-			&lt;outputDirectory&gt;/&lt;/outputDirectory&gt;
-			&lt;useDefaultExcludes&gt;true&lt;/useDefaultExcludes&gt;
-			&lt;excludes&gt;
-				&lt;exclude&gt;**/${project.build.directory}/**&lt;/exclude&gt;
-				&lt;exclude&gt;mvnw&lt;/exclude&gt;
-				&lt;exclude&gt;mvnw.cmd&lt;/exclude&gt;
-				&lt;exclude&gt;.mvn/**&lt;/exclude&gt;
-				&lt;exclude&gt;src/**&lt;/exclude&gt;
-			&lt;/excludes&gt;
-		&lt;/fileSet&gt;
-	&lt;/fileSets&gt;
-&lt;/assembly&gt;</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_workflow"><a class="link" href="#_workflow">3.5.2. Workflow</a></h4>
-<div class="paragraph">
-<p>The workflow would look similar to the one presented in the <code>Step by step guide to CDC</code>. The only difference
- is that the producer doesn&#8217;t own the contracts anymore. So the consumer and the producer have to work on
- common contracts in a common repository.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_consumer"><a class="link" href="#_consumer">3.5.3. Consumer</a></h4>
-<div class="paragraph">
-<p>When the <strong>consumer</strong> wants to work on the contracts offline, instead of cloning the producer code, the
-consumer team clones the common repository, goes to the required producer&#8217;s folder (e.g. <code>com/example/server</code>)
-and runs <code>mvn clean install -DskipTests</code> to install locally the stubs converted from the contracts.</p>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-You need to have <a href="https://maven.apache.org/download.cgi">Maven installed locally</a>
-</td>
-</tr>
-</table>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_producer"><a class="link" href="#_producer">3.5.4. Producer</a></h4>
-<div class="paragraph">
-<p>As a <strong>producer</strong> it&#8217;s enough to alter the Spring Cloud Contract Verifier to provide the URL and the dependency
-of the JAR containing the contracts:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-	&lt;configuration&gt;
-		&lt;contractsMode&gt;REMOTE&lt;/contractsMode&gt;
-		&lt;contractsRepositoryUrl&gt;
-			https://link/to/your/nexus/or/artifactory/or/sth
-		&lt;/contractsRepositoryUrl&gt;
-		&lt;contractDependency&gt;
-			&lt;groupId&gt;com.example.standalone&lt;/groupId&gt;
-			&lt;artifactId&gt;contracts&lt;/artifactId&gt;
-		&lt;/contractDependency&gt;
-	&lt;/configuration&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>With this setup the JAR with groupid <code>com.example.standalone</code> and artifactid <code>contracts</code> will be downloaded
-from <code><a href="https://link/to/your/nexus/or/artifactory/or/sth" class="bare">https://link/to/your/nexus/or/artifactory/or/sth</a></code>. It will be then unpacked in a local temporary folder
-and contracts present under the <code>com/example/server</code> will be picked as the ones used to generate the
-tests and the stubs. Due to this convention the producer team will know which consumer teams will be broken
-when some incompatible changes are done.</p>
-</div>
-<div class="paragraph">
-<p>The rest of the flow looks the same.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_how_can_i_define_messaging_contracts_per_topic_not_per_producer"><a class="link" href="#_how_can_i_define_messaging_contracts_per_topic_not_per_producer">3.5.5. How can I define messaging contracts per topic not per producer?</a></h4>
-<div class="paragraph">
-<p>To avoid messaging contracts duplication in the common repo, when few producers writing messages to one topic,
-we could create the structure when the rest contracts would be placed in a folder per producer and messaging
-contracts in the folder per topic.</p>
-</div>
-<div class="sect4">
-<h5 id="_for_maven_project"><a class="link" href="#_for_maven_project">For Maven Project</a></h5>
-<div class="paragraph">
-<p>To make it possible to work on the producer side we should specify an inclusion pattern for
-filtering common repository jar by messaging topics we are interested in. <code><code>includedFiles</code></code> property of <code><code>Maven Spring Cloud Contract plugin</code></code>
-allows us to do that. Also <code><code>contractsPath</code></code> need to be specified since the default path would be the common repository <code><code>groupid/artifactid</code></code>.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-   &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-   &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-   &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-   &lt;configuration&gt;
-      &lt;contractsMode&gt;REMOTE&lt;/contractsMode&gt;
-      &lt;contractsRepositoryUrl&gt;https://link/to/your/nexus/or/artifactory/or/sth&lt;/contractsRepositoryUrl&gt;
-      &lt;contractDependency&gt;
-         &lt;groupId&gt;com.example&lt;/groupId&gt;
-         &lt;artifactId&gt;common-repo-with-contracts&lt;/artifactId&gt;
-         &lt;version&gt;+&lt;/version&gt;
-      &lt;/contractDependency&gt;
-      &lt;contractsPath&gt;/&lt;/contractsPath&gt;
-      &lt;baseClassMappings&gt;
-         &lt;baseClassMapping&gt;
-            &lt;contractPackageRegex&gt;.*messaging.*&lt;/contractPackageRegex&gt;
-            &lt;baseClassFQN&gt;com.example.services.MessagingBase&lt;/baseClassFQN&gt;
-         &lt;/baseClassMapping&gt;
-         &lt;baseClassMapping&gt;
-            &lt;contractPackageRegex&gt;.*rest.*&lt;/contractPackageRegex&gt;
-            &lt;baseClassFQN&gt;com.example.services.TestBase&lt;/baseClassFQN&gt;
-         &lt;/baseClassMapping&gt;
-      &lt;/baseClassMappings&gt;
-      &lt;includedFiles&gt;
-         &lt;includedFile&gt;**/${project.artifactId}/**&lt;/includedFile&gt;
-         &lt;includedFile&gt;**/${first-topic}/**&lt;/includedFile&gt;
-         &lt;includedFile&gt;**/${second-topic}/**&lt;/includedFile&gt;
-      &lt;/includedFiles&gt;
-   &lt;/configuration&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_for_gradle_project"><a class="link" href="#_for_gradle_project">For Gradle Project</a></h5>
-<div class="ulist">
-<ul>
-<li>
-<p>Add a custom configuration for the common-repo dependency:</p>
-</li>
-</ul>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">ext {
-    conractsGroupId = "com.example"
-    contractsArtifactId = "common-repo"
-    contractsVersion = "1.2.3"
-}
-
-configurations {
-    contracts {
-        transitive = false
-    }
-}</code></pre>
-</div>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Add the common-repo dependency to your classpath:</p>
-</li>
-</ul>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">dependencies {
-    contracts "${conractsGroupId}:${contractsArtifactId}:${contractsVersion}"
-    testCompile "${conractsGroupId}:${contractsArtifactId}:${contractsVersion}"
-}</code></pre>
-</div>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Download the dependency to an appropriate folder:</p>
-</li>
-</ul>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">task getContracts(type: Copy) {
-    from configurations.contracts
-    into new File(project.buildDir, "downloadedContracts")
-}</code></pre>
-</div>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Unzip JAR:</p>
-</li>
-</ul>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">task unzipContracts(type: Copy) {
-    def zipFile = new File(project.buildDir, "downloadedContracts/${contractsArtifactId}-${contractsVersion}.jar")
-    def outputDir = file("${buildDir}/unpackedContracts")
-
-    from zipTree(zipFile)
-    into outputDir
-}</code></pre>
-</div>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Cleanup unused contracts:</p>
-</li>
-</ul>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">task deleteUnwantedContracts(type: Delete) {
-    delete fileTree(dir: "${buildDir}/unpackedContracts",
-        include: "**/*",
-        excludes: [
-            "**/${project.name}/**"",
-            "**/${first-topic}/**",
-            "**/${second-topic}/**"])
-}</code></pre>
-</div>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Create task dependencies:</p>
-</li>
-</ul>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">unzipContracts.dependsOn("getContracts")
-deleteUnwantedContracts.dependsOn("unzipContracts")
-build.dependsOn("deleteUnwantedContracts")</code></pre>
-</div>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Configure plugin by specifying the directory containing contracts using <code>contractsDslDir</code> property</p>
-</li>
-</ul>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
-    contractsDslDir = new File("${buildDir}/unpackedContracts")
-}</code></pre>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_do_i_need_a_binary_storage_cant_i_use_git"><a class="link" href="#_do_i_need_a_binary_storage_cant_i_use_git">3.6. Do I need a Binary Storage? Can&#8217;t I use Git?</a></h3>
-<div class="paragraph">
-<p>In the polyglot world, there are languages that don&#8217;t use binary storages like
-Artifactory or Nexus. Starting from Spring Cloud Contract version 2.0.0 we provide
-mechanisms to store contracts and stubs in a SCM repository. Currently the
-only supported SCM is Git.</p>
-</div>
-<div class="paragraph">
-<p>The repository would have to the following setup
-(which you can checkout <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x/contracts_git/">here</a>):</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code>.
-└── META-INF
-    └── com.example
-        └── beer-api-producer-git
-            └── 0.0.1-SNAPSHOT
-                ├── contracts
-                │   └── beer-api-consumer
-                │       ├── messaging
-                │       │   ├── shouldSendAcceptedVerification.groovy
-                │       │   └── shouldSendRejectedVerification.groovy
-                │       └── rest
-                │           ├── shouldGrantABeerIfOldEnough.groovy
-                │           └── shouldRejectABeerIfTooYoung.groovy
-                └── mappings
-                    └── beer-api-consumer
-                        └── rest
-                            ├── shouldGrantABeerIfOldEnough.json
-                            └── shouldRejectABeerIfTooYoung.json</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Under <code>META-INF</code> folder:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>we group applications via <code>groupId</code> (e.g. <code>com.example</code>)</p>
-</li>
-<li>
-<p>then each application is represented via the <code>artifactId</code> (e.g. <code>beer-api-producer-git</code>)</p>
-</li>
-<li>
-<p>next, the version of the application (e.g. <code>0.0.1-SNAPSHOT</code>). Starting from Spring Cloud Contract version <code>2.1.0</code>, you can specify the versions as follows (assuming that your versions follow the semantic versioning)</p>
-<div class="ulist">
-<ul>
-<li>
-<p><code>+</code> or <code>latest</code> - to find the latest version of your stubs (assuming that the snapshots are always the latest artifact for a given revision number). That means:</p>
-<div class="ulist">
-<ul>
-<li>
-<p>if you have a version <code>1.0.0.RELEASE</code>, <code>2.0.0.BUILD-SNAPSHOT</code> and <code>2.0.0.RELEASE</code> we will assume that the latest is <code>2.0.0.BUILD-SNAPSHOT</code></p>
-</li>
-<li>
-<p>if you have a version <code>1.0.0.RELEASE</code> and <code>2.0.0.RELEASE</code> we will assume that the latest is <code>2.0.0.RELEASE</code></p>
-</li>
-<li>
-<p>if you have a version called <code>latest</code> or <code>+</code> we will pick that folder</p>
-</li>
-</ul>
-</div>
-</li>
-<li>
-<p><code>release</code> - to find the latest release version of your stubs. That means:</p>
-<div class="ulist">
-<ul>
-<li>
-<p>if you have a version <code>1.0.0.RELEASE</code>, <code>2.0.0.BUILD-SNAPSHOT</code> and <code>2.0.0.RELEASE</code> we will assume that the latest is <code>2.0.0.RELEASE</code></p>
-</li>
-<li>
-<p>if you have a version called <code>release</code> we will pick that folder</p>
-</li>
-</ul>
-</div>
-</li>
-</ul>
-</div>
-</li>
-<li>
-<p>finally, there are two folders:</p>
-<div class="ulist">
-<ul>
-<li>
-<p><code>contracts</code> - the good practice is to store the contracts required by each
-consumer in the folder with the consumer name (e.g. <code>beer-api-consumer</code>). That way you
-can use the <code>stubs-per-consumer</code> feature. Further directory structure is arbitrary.</p>
-</li>
-<li>
-<p><code>mappings</code> - in this folder the Maven / Gradle Spring Cloud Contract plugins will push
-the stub server mappings. On the consumer side, Stub Runner will scan this folder
-to start stub servers with stub definitions. The folder structure will be a copy
-of the one created in the <code>contracts</code> subfolder.</p>
-</li>
-</ul>
-</div>
-</li>
-</ul>
-</div>
-<div class="sect3">
-<h4 id="_protocol_convention"><a class="link" href="#_protocol_convention">3.6.1. Protocol convention</a></h4>
-<div class="paragraph">
-<p>In order to control the type and location of the source of contracts (whether it&#8217;s
-a binary storage or an SCM repository), you can use the protocol in the URL of
-the repository. Spring Cloud Contract iterates over registered protocol resolvers
-and tries to fetch the contracts (via a plugin) or stubs (via Stub Runner).</p>
-</div>
-<div class="paragraph">
-<p>For the SCM functionality, currently, we support the Git repository. To use it,
-in the property, where the repository URL needs to be placed you just have to prefix
-the connection URL with <code>git://</code>. Here you can find a couple of examples:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code>git://file:///foo/bar
-git://https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git
-git://git@github.com:spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_producer_2"><a class="link" href="#_producer_2">3.6.2. Producer</a></h4>
-<div class="paragraph">
-<p>For the producer, to use the SCM approach, we can reuse the
-same mechanism we use for external contracts. We route Spring Cloud Contract
-to use the SCM implementation via the URL that contains
-the <code>git://</code> protocol.</p>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-You have to manually add the <code>pushStubsToScm</code>
-goal in Maven or execute (bind) the <code>pushStubsToScm</code> task in
-Gradle. We don&#8217;t push stubs to <code>origin</code> of your git
-repository out of the box.
-</td>
-</tr>
-</table>
-</div>
-<div class="listingblock">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-    &lt;extensions&gt;true&lt;/extensions&gt;
-    &lt;configuration&gt;
-        &lt;!-- Base class mappings etc. --&gt;
-
-        &lt;!-- We want to pick contracts from a Git repository --&gt;
-        &lt;contractsRepositoryUrl&gt;git://https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git&lt;/contractsRepositoryUrl&gt;
-
-        &lt;!-- We reuse the contract dependency section to set up the path
-        to the folder that contains the contract definitions. In our case the
-        path will be /groupId/artifactId/version/contracts --&gt;
-        &lt;contractDependency&gt;
-            &lt;groupId&gt;${project.groupId}&lt;/groupId&gt;
-            &lt;artifactId&gt;${project.artifactId}&lt;/artifactId&gt;
-            &lt;version&gt;${project.version}&lt;/version&gt;
-        &lt;/contractDependency&gt;
-
-        &lt;!-- The contracts mode can't be classpath --&gt;
-        &lt;contractsMode&gt;REMOTE&lt;/contractsMode&gt;
-    &lt;/configuration&gt;
-    &lt;executions&gt;
-        &lt;execution&gt;
-            &lt;phase&gt;package&lt;/phase&gt;
-            &lt;goals&gt;
-                &lt;!-- By default we will not push the stubs back to SCM,
-                you have to explicitly add it as a goal --&gt;
-                &lt;goal&gt;pushStubsToScm&lt;/goal&gt;
-            &lt;/goals&gt;
-        &lt;/execution&gt;
-    &lt;/executions&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-gradle hljs" data-lang="gradle">contracts {
-	// We want to pick contracts from a Git repository
-	contractDependency {
-		stringNotation = "${project.group}:${project.name}:${project.version}"
-	}
-	/*
-	We reuse the contract dependency section to set up the path
-	to the folder that contains the contract definitions. In our case the
-	path will be /groupId/artifactId/version/contracts
-	 */
-	contractRepository {
-		repositoryUrl = "git://https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git"
-	}
-	// The mode can't be classpath
-	contractsMode = "REMOTE"
-	// Base class mappings etc.
-}
-
-/*
-In this scenario we want to publish stubs to SCM whenever
-the `publish` task is executed
-*/
-publish.dependsOn("publishStubsToScm")</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>With such a setup:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Git project will be cloned to a temporary directory</p>
-</li>
-<li>
-<p>The SCM stub downloader will go to <code>META-INF/groupId/artifactId/version/contracts</code> folder
-to find contracts. E.g. for <code>com.example:foo:1.0.0</code> the path would be
-<code>META-INF/com.example/foo/1.0.0/contracts</code></p>
-</li>
-<li>
-<p>Tests will be generated from the contracts</p>
-</li>
-<li>
-<p>Stubs will be created from the contracts</p>
-</li>
-<li>
-<p>Once the tests pass, the stubs will be committed in the cloned repository</p>
-</li>
-<li>
-<p>Finally, a push will be done to that repo&#8217;s <code>origin</code></p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_producer_with_contracts_stored_locally"><a class="link" href="#_producer_with_contracts_stored_locally">3.6.3. Producer with contracts stored locally</a></h4>
-<div class="paragraph">
-<p>Another option to use the SCM as the destination for stubs and contracts is to store the contracts locally, with the producer, and only push the contracts and the stubs to SCM. Below, you can find the setup required to achieve this using Maven and Gradle.</p>
-</div>
-<div class="listingblock">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-	&lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-	&lt;extensions&gt;true&lt;/extensions&gt;
-	&lt;!-- In the default configuration, we want to use the contracts stored locally --&gt;
-	&lt;configuration&gt;
-		&lt;baseClassMappings&gt;
-			&lt;baseClassMapping&gt;
-				&lt;contractPackageRegex&gt;.*messaging.*&lt;/contractPackageRegex&gt;
-				&lt;baseClassFQN&gt;com.example.BeerMessagingBase&lt;/baseClassFQN&gt;
-			&lt;/baseClassMapping&gt;
-			&lt;baseClassMapping&gt;
-				&lt;contractPackageRegex&gt;.*rest.*&lt;/contractPackageRegex&gt;
-				&lt;baseClassFQN&gt;com.example.BeerRestBase&lt;/baseClassFQN&gt;
-			&lt;/baseClassMapping&gt;
-		&lt;/baseClassMappings&gt;
-		&lt;basePackageForTests&gt;com.example&lt;/basePackageForTests&gt;
-	&lt;/configuration&gt;
-	&lt;executions&gt;
-		&lt;execution&gt;
-			&lt;phase&gt;package&lt;/phase&gt;
-			&lt;goals&gt;
-				&lt;!-- By default we will not push the stubs back to SCM,
-				you have to explicitly add it as a goal --&gt;
-				&lt;goal&gt;pushStubsToScm&lt;/goal&gt;
-			&lt;/goals&gt;
-			&lt;configuration&gt;
-				&lt;!-- We want to pick contracts from a Git repository --&gt;
-				&lt;contractsRepositoryUrl&gt;git://file://${env.ROOT}/target/contract_empty_git/
-				&lt;/contractsRepositoryUrl&gt;
-				&lt;!-- Example of URL via git protocol --&gt;
-				&lt;!--&lt;contractsRepositoryUrl&gt;git://git@github.com:spring-cloud-samples/spring-cloud-contract-samples.git&lt;/contractsRepositoryUrl&gt;--&gt;
-				&lt;!-- Example of URL via http protocol --&gt;
-				&lt;!--&lt;contractsRepositoryUrl&gt;git://https://github.com/spring-cloud-samples/spring-cloud-contract-samples.git&lt;/contractsRepositoryUrl&gt;--&gt;
-				&lt;!-- We reuse the contract dependency section to set up the path
-				to the folder that contains the contract definitions. In our case the
-				path will be /groupId/artifactId/version/contracts --&gt;
-				&lt;contractDependency&gt;
-					&lt;groupId&gt;${project.groupId}&lt;/groupId&gt;
-					&lt;artifactId&gt;${project.artifactId}&lt;/artifactId&gt;
-					&lt;version&gt;${project.version}&lt;/version&gt;
-				&lt;/contractDependency&gt;
-				&lt;!-- The mode can't be classpath --&gt;
-				&lt;contractsMode&gt;LOCAL&lt;/contractsMode&gt;
-			&lt;/configuration&gt;
-		&lt;/execution&gt;
-	&lt;/executions&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">contracts {
-		// Base package for generated tests
-	basePackageForTests = "com.example"
-	baseClassMappings {
-		baseClassMapping(".*messaging.*", "com.example.BeerMessagingBase")
-		baseClassMapping(".*rest.*", "com.example.BeerRestBase")
-	}
-}
-
-/*
-In this scenario we want to publish stubs to SCM whenever
-the `publish` task is executed
-*/
-publishStubsToScm {
-	// We want to modify the default set up of the plugin when publish stubs to scm is called
-	customize {
-		// We want to pick contracts from a Git repository
-		contractDependency {
-			stringNotation = "${project.group}:${project.name}:${project.version}"
-		}
-		/*
-		We reuse the contract dependency section to set up the path
-		to the folder that contains the contract definitions. In our case the
-		path will be /groupId/artifactId/version/contracts
-		 */
-		contractRepository {
-			repositoryUrl = "git://file://${System.getenv("ROOT")}/target/contract_empty_git/"
-		}
-		// The mode can't be classpath
-		contractsMode = "LOCAL"
-	}
-}
-
-publish.dependsOn("publishStubsToScm")
-publishToMavenLocal.dependsOn("publishStubsToScm")</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>With such a setup:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Contracts from the default <code>src/test/resources/contracts</code> directory will be picked</p>
-</li>
-<li>
-<p>Tests will be generated from the contracts</p>
-</li>
-<li>
-<p>Stubs will be created from the contracts</p>
-</li>
-<li>
-<p>Once the tests pass</p>
-<div class="ulist">
-<ul>
-<li>
-<p>Git project will be cloned to a temporary directory</p>
-</li>
-<li>
-<p>The stubs and contracts will be committed in the cloned repository</p>
-</li>
-</ul>
-</div>
-</li>
-<li>
-<p>Finally, a push will be done to that repo&#8217;s <code>origin</code></p>
-</li>
-</ul>
-</div>
-<div class="sect4">
-<h5 id="_keeping_contracts_with_the_producer_and_stubs_in_an_external_repository"><a class="link" href="#_keeping_contracts_with_the_producer_and_stubs_in_an_external_repository">Keeping contracts with the producer and stubs in an external repository</a></h5>
-<div class="paragraph">
-<p>It is also possible to keep the contracts in the producer repository, but keep the stubs in an external git repo.
-This is most useful when you want to use the base consumer-producer collaboration flow, but do not have a possibility to
-use an artifact repository for storing the stubs.</p>
-</div>
-<div class="paragraph">
-<p>In order to do that, use the usual producer setup, and then add the <code>pushStubsToScm</code> goal and set
-<code>contractsRepositoryUrl</code> to the repository where you want to keep the stubs.</p>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_consumer_2"><a class="link" href="#_consumer_2">3.6.4. Consumer</a></h4>
-<div class="paragraph">
-<p>On the consumer side when passing the <code>repositoryRoot</code> parameter,
-either from the <code>@AutoConfigureStubRunner</code> annotation, the
-JUnit rule, JUnit 5 extension or properties, it&#8217;s enough to pass the URL of the
-SCM repository, prefixed with the protocol. For example</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(
-    stubsMode="REMOTE",
-    repositoryRoot="git://https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git",
-    ids="com.example:bookstore:0.0.1.RELEASE"
-)</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>With such a setup:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Git project will be cloned to a temporary directory</p>
-</li>
-<li>
-<p>The SCM stub downloader will go to <code>META-INF/groupId/artifactId/version/</code> folder
-to find stub definitions and contracts. E.g. for <code>com.example:foo:1.0.0</code> the path would be
-<code>META-INF/com.example/foo/1.0.0/</code></p>
-</li>
-<li>
-<p>Stub servers will be started and fed with mappings</p>
-</li>
-<li>
-<p>Messaging definitions will be read and used in the messaging tests</p>
-</li>
-</ul>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_can_i_use_the_pact_broker"><a class="link" href="#_can_i_use_the_pact_broker">3.7. Can I use the Pact Broker?</a></h3>
-<div class="paragraph">
-<p>When using <a href="https://pact.io/">Pact</a> you can use the <a href="https://github.com/pact-foundation/pact_broker">Pact Broker</a>
-to store and share Pact definitions. Starting from Spring Cloud Contract
-2.0.0 one can fetch Pact files from the Pact Broker to generate
-tests and stubs.</p>
-</div>
-<div class="paragraph">
-<p>As a prerequisite the Pact Converter and Pact Stub Downloader
-are required. You have to add them via the <code>spring-cloud-contract-pact</code> dependency.
-You can read more about it in the <a href="#pact-converter">Pact Converter</a> section.</p>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-Pact follows the Consumer Contract convention. That means
-that the Consumer creates the Pact definitions first, then
-shares the files with the Producer. Those expectations are generated
-from the Consumer&#8217;s code and can break the Producer if the expectations
-are not met.
-</td>
-</tr>
-</table>
-</div>
-<div class="sect3">
-<h4 id="_pact_consumer"><a class="link" href="#_pact_consumer">3.7.1. Pact Consumer</a></h4>
-<div class="paragraph">
-<p>The consumer uses Pact framework to generate Pact files. The
-Pact files are sent to the Pact Broker. An example of such
-setup can be found <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x/consumer_pact">here</a>.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_producer_3"><a class="link" href="#_producer_3">3.7.2. Producer</a></h4>
-<div class="paragraph">
-<p>For the producer, to use the Pact files from the Pact Broker, we can reuse the
-same mechanism we use for external contracts. We route Spring Cloud Contract
-to use the Pact implementation via the URL that contains
-the <code>pact://</code> protocol. It&#8217;s enough to pass the URL to the
-Pact Broker. An example of such setup can be found <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x/producer_pact">here</a>.</p>
-</div>
-<div class="listingblock">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-    &lt;extensions&gt;true&lt;/extensions&gt;
-    &lt;configuration&gt;
-        &lt;!-- Base class mappings etc. --&gt;
-
-        &lt;!-- We want to pick contracts from a Git repository --&gt;
-        &lt;contractsRepositoryUrl&gt;pact://http://localhost:8085&lt;/contractsRepositoryUrl&gt;
-
-        &lt;!-- We reuse the contract dependency section to set up the path
-        to the folder that contains the contract definitions. In our case the
-        path will be /groupId/artifactId/version/contracts --&gt;
-        &lt;contractDependency&gt;
-            &lt;groupId&gt;${project.groupId}&lt;/groupId&gt;
-            &lt;artifactId&gt;${project.artifactId}&lt;/artifactId&gt;
-            &lt;!-- When + is passed, a latest tag will be applied when fetching pacts --&gt;
-            &lt;version&gt;+&lt;/version&gt;
-        &lt;/contractDependency&gt;
-
-        &lt;!-- The contracts mode can't be classpath --&gt;
-        &lt;contractsMode&gt;REMOTE&lt;/contractsMode&gt;
-    &lt;/configuration&gt;
-    &lt;!-- Don't forget to add spring-cloud-contract-pact to the classpath! --&gt;
-    &lt;dependencies&gt;
-        &lt;dependency&gt;
-            &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-            &lt;artifactId&gt;spring-cloud-contract-pact&lt;/artifactId&gt;
-            &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-        &lt;/dependency&gt;
-    &lt;/dependencies&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-gradle hljs" data-lang="gradle">buildscript {
-	repositories {
-		//...
-	}
-
-	dependencies {
-		// ...
-		// Don't forget to add spring-cloud-contract-pact to the classpath!
-		classpath "org.springframework.cloud:spring-cloud-contract-pact:${contractVersion}"
-	}
-}
-
-contracts {
-	// When + is passed, a latest tag will be applied when fetching pacts
-	contractDependency {
-		stringNotation = "${project.group}:${project.name}:+"
-	}
-	contractRepository {
-		repositoryUrl = "pact://http://localhost:8085"
-	}
-	// The mode can't be classpath
-	contractsMode = "REMOTE"
-	// Base class mappings etc.
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>With such a setup:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Pact files will be downloaded from the Pact Broker</p>
-</li>
-<li>
-<p>Spring Cloud Contract will convert the Pact files into tests and stubs</p>
-</li>
-<li>
-<p>The JAR with the stubs gets automatically created as usual</p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_pact_consumer_producer_contract_approach"><a class="link" href="#_pact_consumer_producer_contract_approach">3.7.3. Pact Consumer (Producer Contract approach)</a></h4>
-<div class="paragraph">
-<p>In the scenario where you don&#8217;t want to do Consumer Contract approach
-(for every single consumer define the expectations) but you&#8217;d prefer
-to do Producer Contracts (the producer provides the contracts and
-publishes stubs), it&#8217;s enough to use Spring Cloud Contract with
-Stub Runner option. An example of such setup can be found <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x/consumer_pact_stubrunner">here</a>.</p>
-</div>
-<div class="paragraph">
-<p>First, remember to add Stub Runner and Spring Cloud Contract Pact module
-as test dependencies.</p>
-</div>
-<div class="listingblock">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependencyManagement&gt;
-    &lt;dependencies&gt;
-        &lt;dependency&gt;
-            &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-            &lt;artifactId&gt;spring-cloud-dependencies&lt;/artifactId&gt;
-            &lt;version&gt;${spring-cloud.version}&lt;/version&gt;
-            &lt;type&gt;pom&lt;/type&gt;
-            &lt;scope&gt;import&lt;/scope&gt;
-        &lt;/dependency&gt;
-    &lt;/dependencies&gt;
-&lt;/dependencyManagement&gt;
-
-&lt;!-- Don't forget to add spring-cloud-contract-pact to the classpath! --&gt;
-&lt;dependencies&gt;
-    &lt;!-- ... --&gt;
-    &lt;dependency&gt;
-        &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-        &lt;artifactId&gt;spring-cloud-starter-contract-stub-runner&lt;/artifactId&gt;
-        &lt;scope&gt;test&lt;/scope&gt;
-    &lt;/dependency&gt;
-    &lt;dependency&gt;
-        &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-        &lt;artifactId&gt;spring-cloud-contract-pact&lt;/artifactId&gt;
-        &lt;scope&gt;test&lt;/scope&gt;
-    &lt;/dependency&gt;
-&lt;/dependencies&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-gradle hljs" data-lang="gradle">dependencyManagement {
-    imports {
-        mavenBom "org.springframework.cloud:spring-cloud-dependencies:${springCloudVersion}"
-    }
-}
-
-dependencies {
-    //...
-    testCompile("org.springframework.cloud:spring-cloud-starter-contract-stub-runner")
-    // Don't forget to add spring-cloud-contract-pact to the classpath!
-    testCompile("org.springframework.cloud:spring-cloud-contract-pact")
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Next, just pass the URL of the Pact Broker to <code>repositoryRoot</code>, prefixed
-with <code>pact://</code> protocol. E.g. <code>pact://http://localhost:8085</code></p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
-@SpringBootTest
-@AutoConfigureStubRunner(stubsMode = StubRunnerProperties.StubsMode.REMOTE,
-		ids = "com.example:beer-api-producer-pact",
-		repositoryRoot = "pact://http://localhost:8085")
-public class BeerControllerTest {
-    //Inject the port of the running stub
-    @StubRunnerPort("beer-api-producer-pact") int producerPort;
-    //...
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>With such a setup:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Pact files will be downloaded from the Pact Broker</p>
-</li>
-<li>
-<p>Spring Cloud Contract will convert the Pact files into stub definitions</p>
-</li>
-<li>
-<p>The stub servers will be started and fed with stubs</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>For more information about Pact support you can go to
-the <a href="#pact-stub-downloader">Using the Pact Stub Downloader</a> section.</p>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_how_can_i_debug_the_requestresponse_being_sent_by_the_generated_tests_client"><a class="link" href="#_how_can_i_debug_the_requestresponse_being_sent_by_the_generated_tests_client">3.8. How can I debug the request/response being sent by the generated tests client?</a></h3>
-<div class="paragraph">
-<p>The generated tests all boil down to RestAssured in some form or fashion which relies on <a href="https://hc.apache.org/httpcomponents-client-ga/">Apache HttpClient</a>.  HttpClient has a facility called <a href="https://hc.apache.org/httpcomponents-client-ga/logging.html#Wire_Logging">wire logging</a> which logs the entire request and response to HttpClient.  Spring Boot has a logging <a href="https://docs.spring.io/spring-boot/docs/current/reference/html/common-application-properties.html">common application property</a> for doing this sort of thing, just add this to your application properties</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-properties hljs" data-lang="properties">logging.level.org.apache.http.wire=DEBUG</code></pre>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_how_can_i_debug_the_mappingrequestresponse_being_sent_by_wiremock"><a class="link" href="#_how_can_i_debug_the_mappingrequestresponse_being_sent_by_wiremock">3.8.1. How can I debug the mapping/request/response being sent by WireMock?</a></h4>
-<div class="paragraph">
-<p>Starting from version <code>1.2.0</code> we turn on WireMock logging to
-info and the WireMock notifier to being verbose. Now you will
-exactly know what request was received by WireMock server and which
-matching response definition was picked.</p>
-</div>
-<div class="paragraph">
-<p>To turn off this feature just bump WireMock logging to <code>ERROR</code></p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-properties hljs" data-lang="properties">logging.level.com.github.tomakehurst.wiremock=ERROR</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_how_can_i_see_what_got_registered_in_the_http_server_stub"><a class="link" href="#_how_can_i_see_what_got_registered_in_the_http_server_stub">3.8.2. How can I see what got registered in the HTTP server stub?</a></h4>
-<div class="paragraph">
-<p>You can use the <code>mappingsOutputFolder</code> property on <code>@AutoConfigureStubRunner</code>, <code>StubRunnerRule</code> or
-`StubRunnerExtension`to dump all mappings per artifact id. Also the port at which the given stub server
-was started will be attached.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_can_i_reference_text_from_file"><a class="link" href="#_can_i_reference_text_from_file">3.8.3. Can I reference text from file?</a></h4>
-<div class="paragraph">
-<p>Yes! With version 1.2.0 we&#8217;ve added such a possibility. It&#8217;s enough to call <code>file(&#8230;&#8203;)</code> method in the
-DSL and provide a path relative to where the contract lays.
-If you&#8217;re using YAML just use the <code>bodyFromFile</code> property.</p>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_spring_cloud_contract_verifier_setup"><a class="link" href="#_spring_cloud_contract_verifier_setup">4. Spring Cloud Contract Verifier Setup</a></h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>You can set up Spring Cloud Contract Verifier in the following ways:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="#gradle-project">As a Gradle project</a></p>
-</li>
-<li>
-<p><a href="#maven-project">As a Maven project</a></p>
-</li>
-<li>
-<p><a href="#docker-project">As a Docker project</a></p>
-</li>
-</ul>
-</div>
-<div class="sect2">
-<h3 id="gradle-project"><a class="link" href="#gradle-project">4.1. Gradle Project</a></h3>
-<div class="paragraph">
-<p>To learn how to set up the Gradle project for Spring Cloud Contract Verifier, read the
-following sections:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="#gradle-prerequisites">Prerequisites</a></p>
-</li>
-<li>
-<p><a href="#gradle-add-gradle-plugin">Add Gradle Plugin with Dependencies</a></p>
-</li>
-<li>
-<p><a href="#gradle-and-rest-assured">Gradle and Rest Assured 2.0</a></p>
-</li>
-<li>
-<p><a href="#gradle-snapshot-versions">Snapshot Versions for Gradle</a></p>
-</li>
-<li>
-<p><a href="#gradle-add-stubs">Add stubs</a></p>
-</li>
-<li>
-<p><a href="#gradle-default-setup">Default Setup</a></p>
-</li>
-<li>
-<p><a href="#gradle-configure-plugin">Configure Plugin</a></p>
-</li>
-<li>
-<p><a href="#gradle-configuration-options">Configuration Options</a></p>
-</li>
-<li>
-<p><a href="#gradle-single-base-class">Single Base Class for All Tests</a></p>
-</li>
-<li>
-<p><a href="#gradle-different-base-classes">Different Base Classes for Contracts</a></p>
-</li>
-<li>
-<p><a href="#gradle-invoking-generated-tests">Invoking Generated Tests</a></p>
-</li>
-<li>
-<p><a href="#gradle-pushing-stubs-to-scm">Pushing stubs to SCM</a></p>
-</li>
-<li>
-<p><a href="#gradle-consumer">Spring Cloud Contract Verifier on the Consumer Side</a></p>
-</li>
-</ul>
-</div>
-<div class="sect3">
-<h4 id="gradle-prerequisites"><a class="link" href="#gradle-prerequisites">4.1.1. Prerequisites</a></h4>
-<div class="paragraph">
-<p>In order to use Spring Cloud Contract Verifier with WireMock, you muse use either a
-Gradle or a Maven plugin.</p>
-</div>
-<div class="admonitionblock warning">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-warning" title="Warning"></i>
-</td>
-<td class="content">
-If you want to use Spock in your projects, you must add separately the
-<code>spock-core</code> and <code>spock-spring</code> modules. Check <a href="https://spockframework.github.io/">Spock
-docs for more information</a>
-</td>
-</tr>
-</table>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gradle-add-gradle-plugin"><a class="link" href="#gradle-add-gradle-plugin">4.1.2. Add Gradle Plugin with Dependencies</a></h4>
-<div class="paragraph">
-<p>To add a Gradle plugin with dependencies, use code similar to this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">buildscript {
-	repositories {
-		mavenCentral()
-	}
-	dependencies {
-		classpath "org.springframework.boot:spring-boot-gradle-plugin:${springboot_version}"
-		classpath "org.springframework.cloud:spring-cloud-contract-gradle-plugin:${verifier_version}"
-	}
-}
-
-apply plugin: 'groovy'
-apply plugin: 'spring-cloud-contract'
-
-dependencyManagement {
-	imports {
-		mavenBom "org.springframework.cloud:spring-cloud-contract-dependencies:${verifier_version}"
-	}
-}
-
-dependencies {
-	testCompile 'org.codehaus.groovy:groovy-all:2.4.6'
-	// example with adding Spock core and Spock Spring
-	testCompile 'org.spockframework:spock-core:1.0-groovy-2.4'
-	testCompile 'org.spockframework:spock-spring:1.0-groovy-2.4'
-	testCompile 'org.springframework.cloud:spring-cloud-starter-contract-verifier'
-}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gradle-and-rest-assured"><a class="link" href="#gradle-and-rest-assured">4.1.3. Gradle and Rest Assured 2.0</a></h4>
-<div class="paragraph">
-<p>By default, Rest Assured 3.x is added to the classpath. However, to use Rest Assured 2.x
-you can add it to the plugins classpath, as shown here:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">buildscript {
-	repositories {
-		mavenCentral()
-	}
-	dependencies {
-		classpath "org.springframework.boot:spring-boot-gradle-plugin:${springboot_version}"
-		classpath "org.springframework.cloud:spring-cloud-contract-gradle-plugin:${verifier_version}"
-		classpath "com.jayway.restassured:rest-assured:2.5.0"
-		classpath "com.jayway.restassured:spring-mock-mvc:2.5.0"
-	}
-}
-
-depenendencies {
-    // all dependencies
-    // you can exclude rest-assured from spring-cloud-contract-verifier
-    testCompile "com.jayway.restassured:rest-assured:2.5.0"
-    testCompile "com.jayway.restassured:spring-mock-mvc:2.5.0"
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>That way, the plugin automatically sees that Rest Assured 2.x is present on the classpath
-and modifies the imports accordingly.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gradle-snapshot-versions"><a class="link" href="#gradle-snapshot-versions">4.1.4. Snapshot Versions for Gradle</a></h4>
-<div class="paragraph">
-<p>Add the additional snapshot repository to your build.gradle to use snapshot versions,
-which are automatically uploaded after every successful build, as shown here:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">buildscript {
-	repositories {
-		mavenCentral()
-		mavenLocal()
-		maven { url "https://repo.spring.io/snapshot" }
-		maven { url "https://repo.spring.io/milestone" }
-		maven { url "https://repo.spring.io/release" }
-	}
-}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gradle-add-stubs"><a class="link" href="#gradle-add-stubs">4.1.5. Add stubs</a></h4>
-<div class="paragraph">
-<p>By default, Spring Cloud Contract Verifier is looking for stubs in the
-<code>src/test/resources/contracts</code> directory.</p>
-</div>
-<div class="paragraph">
-<p>The directory containing stub definitions is treated as a class name, and each stub
-definition is treated as a single test. Spring Cloud Contract Verifier assumes that it
-contains at  least one level of directories that are to be used as the test class name.
-If more than  one level of nested directories is present, all except the last one is used
-as the package name. For example, with following structure:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">src/test/resources/contracts/myservice/shouldCreateUser.groovy
-src/test/resources/contracts/myservice/shouldReturnUser.groovy</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Spring Cloud Contract Verifier creates a test class named <code>defaultBasePackage.MyService</code>
-with two methods:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>shouldCreateUser()</code></p>
-</li>
-<li>
-<p><code>shouldReturnUser()</code></p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gradle-run-plugin"><a class="link" href="#gradle-run-plugin">4.1.6. Run the Plugin</a></h4>
-<div class="paragraph">
-<p>The plugin registers itself to be invoked before a <code>check</code> task. If you want it to be
-part of your build process, you need to do nothing more. If you just want to generate
-tests, invoke the <code>generateContractTests</code> task.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gradle-default-setup"><a class="link" href="#gradle-default-setup">4.1.7. Default Setup</a></h4>
-<div class="paragraph">
-<p>The default Gradle Plugin setup creates the following Gradle part of the build (in
-pseudocode):</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
-    testFramework ='JUNIT'
-    testMode = 'MockMvc'
-    generatedTestSourcesDir = project.file("${project.buildDir}/generated-test-sources/contracts")
-    generatedTestResourcesDir = project.file("${project.buildDir}/generated-test-resources/contracts")
-    contractsDslDir = "${project.rootDir}/src/test/resources/contracts"
-    basePackageForTests = 'org.springframework.cloud.verifier.tests'
-    stubsOutputDir = project.file("${project.buildDir}/stubs")
-
-    // the following properties are used when you want to provide where the JAR with contract lays
-    contractDependency {
-        stringNotation = ''
-    }
-    contractsPath = ''
-    contractsWorkOffline = false
-    contractRepository {
-        cacheDownloadedContracts(true)
-    }
-}
-
-tasks.create(type: Jar, name: 'verifierStubsJar', dependsOn: 'generateClientStubs') {
-    baseName = project.name
-    classifier = contracts.stubsSuffix
-    from contractVerifier.stubsOutputDir
-}
-
-project.artifacts {
-    archives task
-}
-
-tasks.create(type: Copy, name: 'copyContracts') {
-    from contracts.contractsDslDir
-    into contracts.stubsOutputDir
-}
-
-verifierStubsJar.dependsOn 'copyContracts'
-
-publishing {
-    publications {
-        stubs(MavenPublication) {
-            artifactId project.name
-            artifact verifierStubsJar
-        }
-    }
-}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gradle-configure-plugin"><a class="link" href="#gradle-configure-plugin">4.1.8. Configure Plugin</a></h4>
-<div class="paragraph">
-<p>To change the default configuration, add a <code>contracts</code> snippet to your Gradle config, as
-shown here:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
-	testMode = 'MockMvc'
-	baseClassForTests = 'org.mycompany.tests'
-	generatedTestSourcesDir = project.file('src/generatedContract')
-}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gradle-configuration-options"><a class="link" href="#gradle-configuration-options">4.1.9. Configuration Options</a></h4>
-<div class="ulist">
-<ul>
-<li>
-<p><strong>testMode</strong>: Defines the mode for acceptance tests. By default, the mode is MockMvc,
-which is based on Spring&#8217;s MockMvc. It can also be changed to <strong>WebTestClient</strong>, <strong>JaxRsClient</strong> or to
-<strong>Explicit</strong> for real HTTP calls.</p>
-</li>
-<li>
-<p><strong>imports</strong>: Creates an array with imports that should be included in generated tests
-(for example ['org.myorg.Matchers']). By default, it creates an empty array.</p>
-</li>
-<li>
-<p><strong>staticImports</strong>: Creates an array with static imports that should be included in
-generated tests(for example ['org.myorg.Matchers.*']). By default, it creates an empty
-array.</p>
-</li>
-<li>
-<p><strong>basePackageForTests</strong>: Specifies the base package for all generated tests. If not set,
-the value is picked from <code>baseClassForTests&#8217;s package and from `packageWithBaseClasses</code>.
-If neither of these values are set, then the value is set to
-<code>org.springframework.cloud.contract.verifier.tests</code>.</p>
-</li>
-<li>
-<p><strong>baseClassForTests</strong>: Creates a base class for all generated tests. By default, if you
-use Spock classes, the class is <code>spock.lang.Specification</code>.</p>
-</li>
-<li>
-<p><strong>packageWithBaseClasses</strong>: Defines a package where all the base classes reside. This
-setting takes precedence over <strong>baseClassForTests</strong>.</p>
-</li>
-<li>
-<p><strong>baseClassMappings</strong>: Explicitly maps a contract package to a FQN of a base class. This
-setting takes precedence over <strong>packageWithBaseClasses</strong> and <strong>baseClassForTests</strong>.</p>
-</li>
-<li>
-<p><strong>ruleClassForTests</strong>: Specifies a rule that should be added to the generated test
-classes.</p>
-</li>
-<li>
-<p><strong>ignoredFiles</strong>: Uses an <code>Antmatcher</code> to allow defining stub files for which processing
-should be skipped. By default, it is an empty array.</p>
-</li>
-<li>
-<p><strong>contractsDslDir</strong>: Specifies the directory containing contracts written using the
-GroovyDSL. By default, its value is <code>$rootDir/src/test/resources/contracts</code>.</p>
-</li>
-<li>
-<p><strong>generatedTestSourcesDir</strong>: Specifies the test source directory where tests generated
-from the Groovy DSL should be placed. By default its value is
-<code>$buildDir/generated-test-sources/contracts</code>.</p>
-</li>
-<li>
-<p><strong>generatedTestResourcesDir</strong>: Specifies the test resource directory where resources used by the tests generated
-from the Groovy DSL should be placed. By default its value is
-<code>$buildDir/generated-test-resources/contracts</code>.</p>
-</li>
-<li>
-<p><strong>stubsOutputDir</strong>: Specifies the directory where the generated WireMock stubs from
-the Groovy DSL should be placed.</p>
-</li>
-<li>
-<p><strong>testFramework</strong>: Specifies the target test framework to be used. Currently, Spock, JUnit 4 (<code>TestFramework.JUNIT</code>), TestNG and
-JUnit 5 are supported with JUnit 4 being the default framework.</p>
-</li>
-<li>
-<p><strong>contractsProperties</strong>: a map containing properties to be passed to Spring Cloud Contract
-components. Those properties might be used by e.g. inbuilt or custom Stub Downloaders.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>The following properties are used when you want to specify the location of the JAR
-containing the contracts:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><strong>contractDependency</strong>: Specifies the Dependency that provides
-<code>groupid:artifactid:version:classifier</code> coordinates. You can use the <code>contractDependency</code>
-closure to set it up.</p>
-</li>
-<li>
-<p><strong>contractsPath</strong>: Specifies the path to the jar. If contract dependencies are
-downloaded, the path defaults to <code>groupid/artifactid</code> where <code>groupid</code> is slash
-separated. Otherwise, it scans contracts under the provided directory.</p>
-</li>
-<li>
-<p><strong>contractsMode</strong>: Specifies the mode of downloading contracts (whether the
-JAR is available offline, remotely etc.)</p>
-</li>
-<li>
-<p><strong>deleteStubsAfterTest</strong>: If set to <code>false</code> will not remove any downloaded
-contracts from temporary directories</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Below you can find a list of experimental features you can turn on via the plugin:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><strong>convertToYaml</strong>: converts all DSLs to the declarative, YAML format. This can be extremely useful when you&#8217;re using external libraries in your Groovy DSLs. By turning this feature on (by setting it to <code>true</code>) you will not need to add the library dependency on the consumer side.</p>
-</li>
-<li>
-<p><strong>assertJsonSize</strong>: You can check the size of JSON arrays in the generated tests. This feature is disabled by default.</p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gradle-single-base-class"><a class="link" href="#gradle-single-base-class">4.1.10. Single Base Class for All Tests</a></h4>
-<div class="paragraph">
-<p>When using Spring Cloud Contract Verifier in default MockMvc, you need to create a base
-specification for all generated acceptance tests. In this class, you need to point to an
-endpoint, which should be verified.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">abstract class BaseMockMvcSpec extends Specification {
-
-	def setup() {
-		RestAssuredMockMvc.standaloneSetup(new PairIdController())
-	}
-
-	void isProperCorrelationId(Integer correlationId) {
-		assert correlationId == 123456
-	}
-
-	void isEmpty(String value) {
-		assert value == null
-	}
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>If you use <code>Explicit</code> mode, you can use a base class to initialize the whole tested app
-as you might see in regular integration tests. If you use the <code>JAXRSCLIENT</code> mode, this
-base class should also contain a <code>protected WebTarget webTarget</code> field. Right now, the
-only option to test the JAX-RS API is to start a web server.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gradle-different-base-classes"><a class="link" href="#gradle-different-base-classes">4.1.11. Different Base Classes for Contracts</a></h4>
-<div class="paragraph">
-<p>If your base classes differ between contracts, you can tell the Spring Cloud Contract
-plugin which class should get extended by the autogenerated tests. You have two options:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Follow a convention by providing the <code>packageWithBaseClasses</code></p>
-</li>
-<li>
-<p>Provide explicit mapping via <code>baseClassMappings</code></p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p><strong>By Convention</strong></p>
-</div>
-<div class="paragraph">
-<p>The convention is such that if you have a contract under (for example)
-<code>src/test/resources/contract/foo/bar/baz/</code> and set the value of the
-<code>packageWithBaseClasses</code> property to <code>com.example.base</code>, then Spring Cloud Contract
-Verifier assumes that there is a <code>BarBazBase</code> class under the <code>com.example.base</code> package.
-In other words, the system takes the last two parts of the package, if they exist, and
-forms a class with a <code>Base</code> suffix. This rule takes precedence over <strong>baseClassForTests</strong>.
-Here is an example of how it works in the <code>contracts</code> closure:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">packageWithBaseClasses = 'com.example.base'</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><strong>By Mapping</strong></p>
-</div>
-<div class="paragraph">
-<p>You can manually map a regular expression of the contract&#8217;s package to fully qualified
-name of the base class for the matched contract. You have to provide a list called
-<code>baseClassMappings</code> that consists <code>baseClassMapping</code> objects that takes a
-<code>contractPackageRegex</code> to <code>baseClassFQN</code> mapping. Consider the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">baseClassForTests = "com.example.FooBase"
-baseClassMappings {
-	baseClassMapping('.*/com/.*', 'com.example.ComBase')
-	baseClassMapping('.*/bar/.*': 'com.example.BarBase')
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Let&#8217;s assume that you have contracts under
- - <code>src/test/resources/contract/com/</code>
- - <code>src/test/resources/contract/foo/</code></p>
-</div>
-<div class="paragraph">
-<p>By providing the <code>baseClassForTests</code>, we have a fallback in case mapping did not succeed.
-(You could also provide the <code>packageWithBaseClasses</code> as a fallback.) That way, the tests
-generated from <code>src/test/resources/contract/com/</code> contracts extend the
-<code>com.example.ComBase</code>, whereas the rest of the tests extend <code>com.example.FooBase</code>.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gradle-invoking-generated-tests"><a class="link" href="#gradle-invoking-generated-tests">4.1.12. Invoking Generated Tests</a></h4>
-<div class="paragraph">
-<p>To ensure that the provider side is compliant with defined contracts, you need to invoke:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">./gradlew generateContractTests test</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gradle-pushing-stubs-to-scm"><a class="link" href="#gradle-pushing-stubs-to-scm">4.1.13. Pushing stubs to SCM</a></h4>
-<div class="paragraph">
-<p>If you&#8217;re using the SCM repository to keep the contracts and
-stubs, you might want to automate the step of pushing stubs to
-the repository. To do that, it&#8217;s enough to call the <code>pushStubsToScm</code>
-task. Example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ ./gradlew pushStubsToScm</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Under <a href="#scm-stub-downloader">Using the SCM Stub Downloader</a> you can find all possible
-configuration options that you can pass either via
-the <code>contractsProperties</code> field e.g. <code>contracts { contractsProperties = [foo:"bar"] }</code>,
-via <code>contractsProperties</code> method e.g. <code>contracts { contractsProperties([foo:"bar"]) }</code>,
-a system property or an environment variable.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="gradle-consumer"><a class="link" href="#gradle-consumer">4.1.14. Spring Cloud Contract Verifier on the Consumer Side</a></h4>
-<div class="paragraph">
-<p>In a consuming service, you need to configure the Spring Cloud Contract Verifier plugin
-in exactly the same way as in case of provider. If you do not want to use Stub Runner
-then you need to copy contracts stored in <code>src/test/resources/contracts</code> and generate
-WireMock JSON stubs using:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">./gradlew generateClientStubs</code></pre>
-</div>
-</div>
-<div class="admonitionblock note">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-note" title="Note"></i>
-</td>
-<td class="content">
-The <code>stubsOutputDir</code> option has to be set for stub generation to work.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>When present, JSON stubs can be used in automated tests of consuming a service.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@ContextConfiguration(loader == SpringApplicationContextLoader, classes == Application)
-class LoanApplicationServiceSpec extends Specification {
-
- @ClassRule
- @Shared
- WireMockClassRule wireMockRule == new WireMockClassRule()
-
- @Autowired
- LoanApplicationService sut
-
- def 'should successfully apply for loan'() {
-   given:
- 	LoanApplication application =
-			new LoanApplication(client: new Client(clientPesel: '12345678901'), amount: 123.123)
-   when:
-	LoanApplicationResult loanApplication == sut.loanApplication(application)
-   then:
-	loanApplication.loanApplicationStatus == LoanApplicationStatus.LOAN_APPLIED
-	loanApplication.rejectionReason == null
- }
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><code>LoanApplication</code> makes a call to <code>FraudDetection</code> service. This request is handled by a
-WireMock server configured with stubs generated by Spring Cloud Contract Verifier.</p>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="maven-project"><a class="link" href="#maven-project">4.2. Maven Project</a></h3>
-<div class="paragraph">
-<p>To learn how to set up the Maven project for Spring Cloud Contract Verifier, read the
-following sections:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="#maven-add-plugin">Add maven plugin</a></p>
-</li>
-<li>
-<p><a href="#maven-rest-assured">Maven and Rest Assured 2.0</a></p>
-</li>
-<li>
-<p><a href="#maven-snapshot-versions">Snapshot versions for Maven</a></p>
-</li>
-<li>
-<p><a href="#maven-add-stubs">Add stubs</a></p>
-</li>
-<li>
-<p><a href="#maven-run-plugin">Run plugin</a></p>
-</li>
-<li>
-<p><a href="#maven-configure-plugin">Configure plugin</a></p>
-</li>
-<li>
-<p><a href="#maven-configuration-options">Configuration Options</a></p>
-</li>
-<li>
-<p><a href="#maven-single-base">Single Base Class for All Tests</a></p>
-</li>
-<li>
-<p><a href="#maven-different-base">Different base classes for contracts</a></p>
-</li>
-<li>
-<p><a href="#maven-invoking-generated-tests">Invoking generated tests</a></p>
-</li>
-<li>
-<p><a href="#maven-pushing-stubs-to-scm">Pushing stubs to SCM</a></p>
-</li>
-<li>
-<p><a href="#maven-sts">Maven Plugin and STS</a></p>
-</li>
-</ul>
-</div>
-<div class="sect3">
-<h4 id="maven-add-plugin"><a class="link" href="#maven-add-plugin">4.2.1. Add maven plugin</a></h4>
-<div class="paragraph">
-<p>Add the Spring Cloud Contract BOM in a fashion similar to this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependencyManagement&gt;
-	&lt;dependencies&gt;
-		&lt;dependency&gt;
-			&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-			&lt;artifactId&gt;spring-cloud-dependencies&lt;/artifactId&gt;
-			&lt;version&gt;${spring-cloud-release.version}&lt;/version&gt;
-			&lt;type&gt;pom&lt;/type&gt;
-			&lt;scope&gt;import&lt;/scope&gt;
-		&lt;/dependency&gt;
-	&lt;/dependencies&gt;
-&lt;/dependencyManagement&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Next, add the <code>Spring Cloud Contract Verifier</code> Maven plugin:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-	&lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-	&lt;extensions&gt;true&lt;/extensions&gt;
-	&lt;configuration&gt;
-		&lt;packageWithBaseClasses&gt;com.example.fraud&lt;/packageWithBaseClasses&gt;
-		&lt;convertToYaml&gt;true&lt;/convertToYaml&gt;
-	&lt;/configuration&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You can read more in the
-<a href="https://cloud.spring.io/spring-cloud-static/spring-cloud-contract/2.0.0.RELEASE/spring-cloud-contract-maven-plugin/">Spring
-Cloud Contract Maven Plugin Documentation (example for <code>2.0.0.RELEASE</code> version)</a>.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="maven-rest-assured"><a class="link" href="#maven-rest-assured">4.2.2. Maven and Rest Assured 2.0</a></h4>
-<div class="paragraph">
-<p>By default, Rest Assured 3.x is added to the classpath. However, you can use Rest
-Assured 2.x by adding it to the plugins classpath, as shown here:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">&lt;plugin&gt;
-    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-    &lt;extensions&gt;true&lt;/extensions&gt;
-    &lt;configuration&gt;
-        &lt;packageWithBaseClasses&gt;com.example&lt;/packageWithBaseClasses&gt;
-    &lt;/configuration&gt;
-    &lt;dependencies&gt;
-        &lt;dependency&gt;
-            &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-            &lt;artifactId&gt;spring-cloud-contract-verifier&lt;/artifactId&gt;
-            &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-        &lt;/dependency&gt;
-        &lt;dependency&gt;
-           &lt;groupId&gt;com.jayway.restassured&lt;/groupId&gt;
-           &lt;artifactId&gt;rest-assured&lt;/artifactId&gt;
-           &lt;version&gt;2.5.0&lt;/version&gt;
-           &lt;scope&gt;compile&lt;/scope&gt;
-        &lt;/dependency&gt;
-        &lt;dependency&gt;
-           &lt;groupId&gt;com.jayway.restassured&lt;/groupId&gt;
-           &lt;artifactId&gt;spring-mock-mvc&lt;/artifactId&gt;
-           &lt;version&gt;2.5.0&lt;/version&gt;
-           &lt;scope&gt;compile&lt;/scope&gt;
-        &lt;/dependency&gt;
-    &lt;/dependencies&gt;
-&lt;/plugin&gt;
-
-&lt;dependencies&gt;
-    &lt;!-- all dependencies --&gt;
-    &lt;!-- you can exclude rest-assured from spring-cloud-contract-verifier --&gt;
-    &lt;dependency&gt;
-       &lt;groupId&gt;com.jayway.restassured&lt;/groupId&gt;
-       &lt;artifactId&gt;rest-assured&lt;/artifactId&gt;
-       &lt;version&gt;2.5.0&lt;/version&gt;
-       &lt;scope&gt;test&lt;/scope&gt;
-    &lt;/dependency&gt;
-    &lt;dependency&gt;
-       &lt;groupId&gt;com.jayway.restassured&lt;/groupId&gt;
-       &lt;artifactId&gt;spring-mock-mvc&lt;/artifactId&gt;
-       &lt;version&gt;2.5.0&lt;/version&gt;
-       &lt;scope&gt;test&lt;/scope&gt;
-    &lt;/dependency&gt;
-&lt;/dependencies&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>That way, the plugin automatically sees that Rest Assured 3.x is present on the classpath
-and modifies the imports accordingly.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="maven-snapshot-versions"><a class="link" href="#maven-snapshot-versions">4.2.3. Snapshot versions for Maven</a></h4>
-<div class="paragraph">
-<p>For Snapshot and Milestone versions, you have to add the following section to your
-<code>pom.xml</code>, as shown here:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;repositories&gt;
-	&lt;repository&gt;
-		&lt;id&gt;spring-snapshots&lt;/id&gt;
-		&lt;name&gt;Spring Snapshots&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;true&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/repository&gt;
-	&lt;repository&gt;
-		&lt;id&gt;spring-milestones&lt;/id&gt;
-		&lt;name&gt;Spring Milestones&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;false&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/repository&gt;
-	&lt;repository&gt;
-		&lt;id&gt;spring-releases&lt;/id&gt;
-		&lt;name&gt;Spring Releases&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;false&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/repository&gt;
-&lt;/repositories&gt;
-&lt;pluginRepositories&gt;
-	&lt;pluginRepository&gt;
-		&lt;id&gt;spring-snapshots&lt;/id&gt;
-		&lt;name&gt;Spring Snapshots&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;true&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/pluginRepository&gt;
-	&lt;pluginRepository&gt;
-		&lt;id&gt;spring-milestones&lt;/id&gt;
-		&lt;name&gt;Spring Milestones&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;false&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/pluginRepository&gt;
-	&lt;pluginRepository&gt;
-		&lt;id&gt;spring-releases&lt;/id&gt;
-		&lt;name&gt;Spring Releases&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;false&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/pluginRepository&gt;
-&lt;/pluginRepositories&gt;</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="maven-add-stubs"><a class="link" href="#maven-add-stubs">4.2.4. Add stubs</a></h4>
-<div class="paragraph">
-<p>By default, Spring Cloud Contract Verifier is looking for stubs in the
-<code>src/test/resources/contracts</code> directory. The directory containing stub definitions is
-treated as a class name, and each stub definition is treated as a single test. We assume
-that it contains at least one directory to be used as test class name. If there is more
-than one level of nested directories, all except the last one is used as package name.
-For example, with following structure:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">src/test/resources/contracts/myservice/shouldCreateUser.groovy
-src/test/resources/contracts/myservice/shouldReturnUser.groovy</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Spring Cloud Contract Verifier creates a test class named <code>defaultBasePackage.MyService</code>
-with two methods</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>shouldCreateUser()</code></p>
-</li>
-<li>
-<p><code>shouldReturnUser()</code></p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect3">
-<h4 id="maven-run-plugin"><a class="link" href="#maven-run-plugin">4.2.5. Run plugin</a></h4>
-<div class="paragraph">
-<p>The plugin goal <code>generateTests</code> is assigned to be invoked in the phase called
-<code>generate-test-sources</code>. If you want it to be part of your build process, you need not do
-anything. If you just want to generate tests, invoke the <code>generateTests</code> goal.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="maven-configure-plugin"><a class="link" href="#maven-configure-plugin">4.2.6. Configure plugin</a></h4>
-<div class="paragraph">
-<p>To change the default configuration, just add a <code>configuration</code> section to the plugin
-definition or the <code>execution</code> definition, as shown here:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-    &lt;executions&gt;
-        &lt;execution&gt;
-            &lt;goals&gt;
-                &lt;goal&gt;convert&lt;/goal&gt;
-                &lt;goal&gt;generateStubs&lt;/goal&gt;
-                &lt;goal&gt;generateTests&lt;/goal&gt;
-            &lt;/goals&gt;
-        &lt;/execution&gt;
-    &lt;/executions&gt;
-    &lt;configuration&gt;
-        &lt;basePackageForTests&gt;org.springframework.cloud.verifier.twitter.place&lt;/basePackageForTests&gt;
-        &lt;baseClassForTests&gt;org.springframework.cloud.verifier.twitter.place.BaseMockMvcSpec&lt;/baseClassForTests&gt;
-    &lt;/configuration&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="maven-configuration-options"><a class="link" href="#maven-configuration-options">4.2.7. Configuration Options</a></h4>
-<div class="ulist">
-<ul>
-<li>
-<p><strong>testMode</strong>: Defines the mode for acceptance tests. By default, the mode is MockMvc,
-which is based on Spring&#8217;s MockMvc. It can also be changed to <strong>WebTestClient</strong>, <strong>JaxRsClient</strong> or to
-<strong>Explicit</strong> for real HTTP calls.</p>
-</li>
-<li>
-<p><strong>basePackageForTests</strong>: Specifies the base package for all generated tests. If not set,
-the value is picked from <code>baseClassForTests&#8217;s package and from `packageWithBaseClasses</code>.
-If neither of these values are set, then the value is set to
-<code>org.springframework.cloud.contract.verifier.tests</code>.</p>
-</li>
-<li>
-<p><strong>ruleClassForTests</strong>: Specifies a rule that should be added to the generated test
-classes.</p>
-</li>
-<li>
-<p><strong>baseClassForTests</strong>: Creates a base class for all generated tests. By default, if you
-use Spock classes, the class is <code>spock.lang.Specification</code>.</p>
-</li>
-<li>
-<p><strong>contractsDirectory</strong>: Specifies a directory containing contracts written with the
-GroovyDSL. The default directory is <code>/src/test/resources/contracts</code>.</p>
-</li>
-<li>
-<p><strong>generatedTestSourcesDir</strong>: Specifies the test source directory where tests generated
-from the Groovy DSL should be placed. By default its value is
-<code>$buildDir/generated-test-sources/contracts</code>.</p>
-</li>
-<li>
-<p><strong>generatedTestResourcesDir</strong>: Specifies the test resource directory where resources used by the tests generated</p>
-</li>
-<li>
-<p><strong>testFramework</strong>: Specifies the target test framework to be used. Currently, Spock, JUnit 4 (<code>TestFramework.JUNIT</code>) and
-JUnit 5 are supported with JUnit 4 being the default framework.</p>
-</li>
-<li>
-<p><strong>packageWithBaseClasses</strong>: Defines a package where all the base classes reside. This
-setting takes precedence over <strong>baseClassForTests</strong>. The convention is such that, if you
-have a contract under (for example) <code>src/test/resources/contract/foo/bar/baz/</code> and set
-the value of the <code>packageWithBaseClasses</code> property to <code>com.example.base</code>, then Spring
-Cloud Contract Verifier assumes that there is a <code>BarBazBase</code> class under the
-<code>com.example.base</code> package. In other words, the system takes the last two parts of the
-package, if they exist, and forms a class with a <code>Base</code> suffix.</p>
-</li>
-<li>
-<p><strong>baseClassMappings</strong>: Specifies a list of base class mappings that provide
-<code>contractPackageRegex</code>, which is checked against the package where the contract is
-located, and <code>baseClassFQN</code>, which maps to the fully qualified name of the base class for
-the matched contract. For example, if you have a contract under
-<code>src/test/resources/contract/foo/bar/baz/</code> and map the property
-<code>.* &#8594; com.example.base.BaseClass</code>, then the test class generated from these contracts
-extends <code>com.example.base.BaseClass</code>. This setting takes precedence over
-<strong>packageWithBaseClasses</strong> and <strong>baseClassForTests</strong>.</p>
-</li>
-<li>
-<p><strong>contractsProperties</strong>: a map containing properties to be passed to Spring Cloud Contract
-components. Those properties might be used by e.g. inbuilt or custom Stub Downloaders.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>If you want to download your contract definitions from a Maven repository, you can use
-the following options:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><strong>contractDependency</strong>: The contract dependency that contains all the packaged contracts.</p>
-</li>
-<li>
-<p><strong>contractsPath</strong>: The path to the concrete contracts in the JAR with packaged contracts.
-Defaults to <code>groupid/artifactid</code> where <code>gropuid</code> is slash separated.</p>
-</li>
-<li>
-<p><strong>contractsMode</strong>: Picks the mode in which stubs will be found and registered</p>
-</li>
-<li>
-<p><strong>deleteStubsAfterTest</strong>: If set to <code>false</code> will not remove any downloaded
-contracts from temporary directories</p>
-</li>
-<li>
-<p><strong>contractsRepositoryUrl</strong>: URL to a repo with the artifacts that have contracts. If it is not provided,
-use the current Maven ones.</p>
-</li>
-<li>
-<p><strong>contractsRepositoryUsername</strong>: The user name to be used to connect to the repo with contracts.</p>
-</li>
-<li>
-<p><strong>contractsRepositoryPassword</strong>: The password to be used to connect to the repo with contracts.</p>
-</li>
-<li>
-<p><strong>contractsRepositoryProxyHost</strong>: The proxy host to be used to connect to the repo with contracts.</p>
-</li>
-<li>
-<p><strong>contractsRepositoryProxyPort</strong>: The proxy port to be used to connect to the repo with contracts.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>We cache only non-snapshot, explicitly provided versions (for example
-<code>+</code> or <code>1.0.0.BUILD-SNAPSHOT</code> won&#8217;t get cached). By default, this feature is turned on.</p>
-</div>
-<div class="paragraph">
-<p>Below you can find a list of experimental features you can turn on via the plugin:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><strong>convertToYaml</strong>: converts all DSLs to the declarative, YAML format. This can be extremely useful when you&#8217;re using external libraries in your Groovy DSLs. By turning this feature on (by setting it to <code>true</code>) you will not need to add the library dependency on the consumer side.</p>
-</li>
-<li>
-<p><strong>assertJsonSize</strong>: You can check the size of JSON arrays in the generated tests. This feature is disabled by default.</p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect3">
-<h4 id="maven-single-base"><a class="link" href="#maven-single-base">4.2.8. Single Base Class for All Tests</a></h4>
-<div class="paragraph">
-<p>When using Spring Cloud Contract Verifier in default MockMvc, you need to create a base
-specification for all generated acceptance tests. In this class, you need to point to an
-endpoint, which should be verified.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package org.mycompany.tests
-
-import org.mycompany.ExampleSpringController
-import com.jayway.restassured.module.mockmvc.RestAssuredMockMvc
-import spock.lang.Specification
-
-class MvcSpec extends Specification {
-  def setup() {
-   RestAssuredMockMvc.standaloneSetup(new ExampleSpringController())
-  }
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You can also setup the whole context if necessary.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import io.restassured.module.mockmvc.RestAssuredMockMvc;
-import org.junit.Before;
-import org.junit.runner.RunWith;
-import org.springframework.beans.factory.annotation.Autowired;
-import org.springframework.boot.test.context.SpringBootTest;
-import org.springframework.test.context.junit4.SpringRunner;
-import org.springframework.web.context.WebApplicationContext;
-
-@RunWith(SpringRunner.class)
-@SpringBootTest(webEnvironment = WebEnvironment.RANDOM_PORT, classes = SomeConfig.class, properties="some=property")
-public abstract class BaseTestClass {
-
-	@Autowired
-	WebApplicationContext context;
-
-	@Before
-	public void setup() {
-		RestAssuredMockMvc.webAppContextSetup(this.context);
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>If you use <code>EXPLICIT</code> mode, you can use a base class to initialize the whole tested app
-similarly, as you might find in regular integration tests.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import io.restassured.RestAssured;
-import org.junit.Before;
-import org.junit.runner.RunWith;
-import org.springframework.beans.factory.annotation.Autowired;
-import org.springframework.boot.test.context.SpringBootTest;
-import org.springframework.boot.web.server.LocalServerPort
-import org.springframework.test.context.junit4.SpringRunner;
-import org.springframework.web.context.WebApplicationContext;
-
-@RunWith(SpringRunner.class)
-@SpringBootTest(webEnvironment = WebEnvironment.RANDOM_PORT, classes = SomeConfig.class, properties="some=property")
-public abstract class BaseTestClass {
-
-	@LocalServerPort
-	int port;
-
-	@Before
-	public void setup() {
-		RestAssured.baseURI = "http://localhost:" + this.port;
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>If you use the <code>JAXRSCLIENT</code> mode, this base class should also contain a <code>protected WebTarget webTarget</code> field. Right
-now, the only option to test the JAX-RS API is to start a web server.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="maven-different-base"><a class="link" href="#maven-different-base">4.2.9. Different base classes for contracts</a></h4>
-<div class="paragraph">
-<p>If your base classes differ between contracts, you can tell the Spring Cloud Contract
-plugin which class should get extended by the autogenerated tests. You have two options:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Follow a convention by providing the <code>packageWithBaseClasses</code></p>
-</li>
-<li>
-<p>provide explicit mapping via <code>baseClassMappings</code></p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p><strong>By Convention</strong></p>
-</div>
-<div class="paragraph">
-<p>The convention is such that if you have a contract under (for example)
-<code>src/test/resources/contract/foo/bar/baz/</code> and set the value of the
-<code>packageWithBaseClasses</code> property to <code>com.example.base</code>, then Spring Cloud Contract
-Verifier assumes that there is a <code>BarBazBase</code> class under the <code>com.example.base</code> package.
-In other words, the system takes the last two parts of the package, if they exist, and
-forms a class with a <code>Base</code> suffix. This rule takes precedence over <strong>baseClassForTests</strong>.
-Here is an example of how it works in the <code>contracts</code> closure:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-	&lt;configuration&gt;
-		&lt;packageWithBaseClasses&gt;hello&lt;/packageWithBaseClasses&gt;
-	&lt;/configuration&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><strong>By Mapping</strong></p>
-</div>
-<div class="paragraph">
-<p>You can manually map a regular expression of the contract&#8217;s package to fully qualified
-name of the base class for the matched contract. You have to provide a list called
-<code>baseClassMappings</code> that consists <code>baseClassMapping</code> objects that takes a
-<code>contractPackageRegex</code> to <code>baseClassFQN</code> mapping. Consider the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-	&lt;configuration&gt;
-		&lt;baseClassForTests&gt;com.example.FooBase&lt;/baseClassForTests&gt;
-		&lt;baseClassMappings&gt;
-			&lt;baseClassMapping&gt;
-				&lt;contractPackageRegex&gt;.*com.*&lt;/contractPackageRegex&gt;
-				&lt;baseClassFQN&gt;com.example.TestBase&lt;/baseClassFQN&gt;
-			&lt;/baseClassMapping&gt;
-		&lt;/baseClassMappings&gt;
-	&lt;/configuration&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Assume that you have contracts under these two locations:
-* <code>src/test/resources/contract/com/</code>
-* <code>src/test/resources/contract/foo/</code></p>
-</div>
-<div class="paragraph">
-<p>By providing the <code>baseClassForTests</code>, we have a fallback in case mapping did not succeed.
-(You can also provide the <code>packageWithBaseClasses</code> as a fallback.) That way, the tests
-generated from <code>src/test/resources/contract/com/</code> contracts extend the
-<code>com.example.ComBase</code>, whereas the rest of the tests extend <code>com.example.FooBase</code>.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="maven-invoking-generated-tests"><a class="link" href="#maven-invoking-generated-tests">4.2.10. Invoking generated tests</a></h4>
-<div class="paragraph">
-<p>The Spring Cloud Contract Maven Plugin generates verification code in a directory called
-<code>/generated-test-sources/contractVerifier</code> and attaches this directory to <code>testCompile</code>
-goal.</p>
-</div>
-<div class="paragraph">
-<p>For Groovy Spock code, use the following:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-	&lt;groupId&gt;org.codehaus.gmavenplus&lt;/groupId&gt;
-	&lt;artifactId&gt;gmavenplus-plugin&lt;/artifactId&gt;
-	&lt;version&gt;1.5&lt;/version&gt;
-	&lt;executions&gt;
-		&lt;execution&gt;
-			&lt;goals&gt;
-				&lt;goal&gt;testCompile&lt;/goal&gt;
-			&lt;/goals&gt;
-		&lt;/execution&gt;
-	&lt;/executions&gt;
-	&lt;configuration&gt;
-		&lt;testSources&gt;
-			&lt;testSource&gt;
-				&lt;directory&gt;${project.basedir}/src/test/groovy&lt;/directory&gt;
-				&lt;includes&gt;
-					&lt;include&gt;**/*.groovy&lt;/include&gt;
-				&lt;/includes&gt;
-			&lt;/testSource&gt;
-			&lt;testSource&gt;
-				&lt;directory&gt;${project.build.directory}/generated-test-sources/contractVerifier&lt;/directory&gt;
-				&lt;includes&gt;
-					&lt;include&gt;**/*.groovy&lt;/include&gt;
-				&lt;/includes&gt;
-			&lt;/testSource&gt;
-		&lt;/testSources&gt;
-	&lt;/configuration&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>To ensure that provider side is compliant with defined contracts, you need to invoke
-<code>mvn generateTest test</code>.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="maven-pushing-stubs-to-scm"><a class="link" href="#maven-pushing-stubs-to-scm">4.2.11. Pushing stubs to SCM</a></h4>
-<div class="paragraph">
-<p>If you&#8217;re using the SCM repository to keep the contracts and
-stubs, you might want to automate the step of pushing stubs to
-the repository. To do that, it&#8217;s enough to add the <code>pushStubsToScm</code>
-goal. Example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-    &lt;extensions&gt;true&lt;/extensions&gt;
-    &lt;configuration&gt;
-        &lt;!-- Base class mappings etc. --&gt;
-
-        &lt;!-- We want to pick contracts from a Git repository --&gt;
-        &lt;contractsRepositoryUrl&gt;git://https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git&lt;/contractsRepositoryUrl&gt;
-
-        &lt;!-- We reuse the contract dependency section to set up the path
-        to the folder that contains the contract definitions. In our case the
-        path will be /groupId/artifactId/version/contracts --&gt;
-        &lt;contractDependency&gt;
-            &lt;groupId&gt;${project.groupId}&lt;/groupId&gt;
-            &lt;artifactId&gt;${project.artifactId}&lt;/artifactId&gt;
-            &lt;version&gt;${project.version}&lt;/version&gt;
-        &lt;/contractDependency&gt;
-
-        &lt;!-- The contracts mode can't be classpath --&gt;
-        &lt;contractsMode&gt;REMOTE&lt;/contractsMode&gt;
-    &lt;/configuration&gt;
-    &lt;executions&gt;
-        &lt;execution&gt;
-            &lt;phase&gt;package&lt;/phase&gt;
-            &lt;goals&gt;
-                &lt;!-- By default we will not push the stubs back to SCM,
-                you have to explicitly add it as a goal --&gt;
-                &lt;goal&gt;pushStubsToScm&lt;/goal&gt;
-            &lt;/goals&gt;
-        &lt;/execution&gt;
-    &lt;/executions&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Under <a href="#scm-stub-downloader">Using the SCM Stub Downloader</a> you can find all possible
-configuration options that you can pass either via
-the <code>&lt;configuration&gt;&lt;contractProperties&gt;</code> map, a system property
-or an environment variable.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="maven-sts"><a class="link" href="#maven-sts">4.2.12. Maven Plugin and STS</a></h4>
-<div class="paragraph">
-<p>If you see the following exception while using STS:</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="https://raw.githubusercontent.com/spring-cloud/spring-cloud-contract/master/docs/src/main/asciidoc/images/sts_exception.png" alt="STS Exception">
-</div>
-</div>
-<div class="paragraph">
-<p>When you click on the error marker you should see something like this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash"> plugin:1.1.0.M1:convert:default-convert:process-test-resources) org.apache.maven.plugin.PluginExecutionException: Execution default-convert of goal org.springframework.cloud:spring-
- cloud-contract-maven-plugin:1.1.0.M1:convert failed. at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145) at
- org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331) at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362) at
-...
- org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.lang.NullPointerException at
- org.eclipse.m2e.core.internal.builder.plexusbuildapi.EclipseIncrementalBuildContext.hasDelta(EclipseIncrementalBuildContext.java:53) at
- org.sonatype.plexus.build.incremental.ThreadBuildContext.hasDelta(ThreadBuildContext.java:59) at</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In order to fix this issue, provide the following section in your <code>pom.xml</code>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;build&gt;
-    &lt;pluginManagement&gt;
-        &lt;plugins&gt;
-            &lt;!--This plugin's configuration is used to store Eclipse m2e settings
-                only. It has no influence on the Maven build itself. --&gt;
-            &lt;plugin&gt;
-                &lt;groupId&gt;org.eclipse.m2e&lt;/groupId&gt;
-                &lt;artifactId&gt;lifecycle-mapping&lt;/artifactId&gt;
-                &lt;version&gt;1.0.0&lt;/version&gt;
-                &lt;configuration&gt;
-                    &lt;lifecycleMappingMetadata&gt;
-                        &lt;pluginExecutions&gt;
-                             &lt;pluginExecution&gt;
-                                &lt;pluginExecutionFilter&gt;
-                                    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-                                    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-                                    &lt;versionRange&gt;[1.0,)&lt;/versionRange&gt;
-                                    &lt;goals&gt;
-                                        &lt;goal&gt;convert&lt;/goal&gt;
-                                    &lt;/goals&gt;
-                                &lt;/pluginExecutionFilter&gt;
-                                &lt;action&gt;
-                                    &lt;execute /&gt;
-                                &lt;/action&gt;
-                             &lt;/pluginExecution&gt;
-                        &lt;/pluginExecutions&gt;
-                    &lt;/lifecycleMappingMetadata&gt;
-                &lt;/configuration&gt;
-            &lt;/plugin&gt;
-        &lt;/plugins&gt;
-    &lt;/pluginManagement&gt;
-&lt;/build&gt;</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_maven_plugin_with_spock_tests"><a class="link" href="#_maven_plugin_with_spock_tests">4.2.13. Maven Plugin with Spock Tests</a></h4>
-<div class="paragraph">
-<p>You can select the <a href="http://spockframework.org/">Spock Framework</a> for creating and executing the auto-generated contract
-verification tests with both Maven and Gradle plugin. However, whereas with Gradle its really straightforward,
-in Maven you will require some additional setup in order to make the tests compile and execute properly.</p>
-</div>
-<div class="paragraph">
-<p>First of all, you will have to use a plugin, such as <a href="https://github.com/groovy/GMavenPlus">GMavenPlus</a> plugin,
-to add Groovy to your project. In GMavenPlus plugin, you will need to explicitly set test sources, including both the
-path where your base test classes are defined and the path were the generated contract tests are added.
-Please refer to the example below:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml"></code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>If you uphold to the Spock convention of ending the test class names with <code>Spec</code>, you will also need to adjust your Maven
-Surefire plugin setup, like in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml"></code></pre>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_stubs_and_transitive_dependencies"><a class="link" href="#_stubs_and_transitive_dependencies">4.3. Stubs and Transitive Dependencies</a></h3>
-<div class="paragraph">
-<p>The Maven and Gradle plugin that add the tasks that create the stubs jar for you. One
-problem that arises is that, when reusing the stubs, you can mistakenly import all of
-that stub&#8217;s dependencies. When building a Maven artifact, even though you have a couple
-of different jars, all of them share one pom:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── github-webhook-0.0.1.BUILD-20160903.075506-1-stubs.jar
-├── github-webhook-0.0.1.BUILD-20160903.075506-1-stubs.jar.sha1
-├── github-webhook-0.0.1.BUILD-20160903.075655-2-stubs.jar
-├── github-webhook-0.0.1.BUILD-20160903.075655-2-stubs.jar.sha1
-├── github-webhook-0.0.1.BUILD-SNAPSHOT.jar
-├── github-webhook-0.0.1.BUILD-SNAPSHOT.pom
-├── github-webhook-0.0.1.BUILD-SNAPSHOT-stubs.jar
-├── ...
-└── ...</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>There are three possibilities of working with those dependencies so as not to have any
-issues with transitive dependencies:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Mark all application dependencies as optional</p>
-</li>
-<li>
-<p>Create a separate artifactid for the stubs</p>
-</li>
-<li>
-<p>Exclude dependencies on the consumer side</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p><strong>Mark all application dependencies as optional</strong></p>
-</div>
-<div class="paragraph">
-<p>If, in the <code>github-webhook</code> application, you mark all of your dependencies as optional,
-when you include the <code>github-webhook</code> stubs in another application (or when that
-dependency gets downloaded by Stub Runner) then, since all of the dependencies are
-optional, they will not get downloaded.</p>
-</div>
-<div class="paragraph">
-<p><strong>Create a separate <code>artifactid</code> for the stubs</strong></p>
-</div>
-<div class="paragraph">
-<p>If you create a separate <code>artifactid</code>, then you can set it up in whatever way you wish.
-For example, you might decide to have no dependencies at all.</p>
-</div>
-<div class="paragraph">
-<p><strong>Exclude dependencies on the consumer side</strong></p>
-</div>
-<div class="paragraph">
-<p>As a consumer, if you add the stub dependency to your classpath, you can explicitly
-exclude the unwanted dependencies.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_scenarios"><a class="link" href="#_scenarios">4.4. Scenarios</a></h3>
-<div class="paragraph">
-<p>You can handle scenarios with Spring Cloud Contract Verifier. All you need to do is to
-stick to the proper naming convention while creating your contracts. The convention
-requires including an order number followed by an underscore. This will work regardles
- of whether you&#8217;re working with YAML or Groovy. Example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code>my_contracts_dir\
-  scenario1\
-    1_login.groovy
-    2_showCart.groovy
-    3_logout.groovy</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Such a tree causes Spring Cloud Contract Verifier to generate WireMock&#8217;s scenario with a
-name of <code>scenario1</code> and the three following steps:</p>
-</div>
-<div class="olist arabic">
-<ol class="arabic">
-<li>
-<p>login marked as <code>Started</code> pointing to&#8230;&#8203;</p>
-</li>
-<li>
-<p>showCart marked as <code>Step1</code> pointing to&#8230;&#8203;</p>
-</li>
-<li>
-<p>logout marked as <code>Step2</code> which will close the scenario.</p>
-</li>
-</ol>
-</div>
-<div class="paragraph">
-<p>More details about WireMock scenarios can be found at
-<a href="https://wiremock.org/docs/stateful-behaviour/">https://wiremock.org/docs/stateful-behaviour/</a></p>
-</div>
-<div class="paragraph">
-<p>Spring Cloud Contract Verifier also generates tests with a guaranteed order of execution.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="docker-project"><a class="link" href="#docker-project">4.5. Docker Project</a></h3>
-<div class="paragraph">
-<p>We&#8217;re publishing a <code>springcloud/spring-cloud-contract</code> Docker image
-that contains a project that will generate tests and execute them in <code>EXPLICIT</code> mode
-against a running application.</p>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-The <code>EXPLICIT</code> mode means that the tests generated from contracts will send
-real requests and not the mocked ones.
-</td>
-</tr>
-</table>
-</div>
-<div class="sect3">
-<h4 id="_short_intro_to_maven_jars_and_binary_storage"><a class="link" href="#_short_intro_to_maven_jars_and_binary_storage">4.5.1. Short intro to Maven, JARs and Binary storage</a></h4>
-<div class="paragraph">
-<p>Since the Docker image can be used by non JVM projects, it&#8217;s good to
-explain the basic terms behind Spring Cloud Contract packaging defaults.</p>
-</div>
-<div class="paragraph">
-<p>Part of the following definitions were taken from the <a href="https://maven.apache.org/glossary.html">Maven Glossary</a></p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>Project</code>: Maven thinks in terms of projects. Everything that you
-will build are projects. Those projects follow a well defined
-“Project Object Model”. Projects can depend on other projects,
-in which case the latter are called “dependencies”. A project may
-consistent of several subprojects, however these subprojects are still
-treated equally as projects.</p>
-</li>
-<li>
-<p><code>Artifact</code>: An artifact is something that is either produced or used
-by a project. Examples of artifacts produced by Maven for a project
-include: JARs, source and binary distributions. Each artifact
-is uniquely identified by a group id and an artifact ID which is
-unique within a group.</p>
-</li>
-<li>
-<p><code>JAR</code>: JAR stands for Java ARchive. It&#8217;s a format based on
-the ZIP file format. Spring Cloud Contract packages the contracts and generated
-stubs in a JAR file.</p>
-</li>
-<li>
-<p><code>GroupId</code>: A group ID is a universally unique identifier for a project.
-While this is often just the project name (eg. commons-collections),
-it is helpful to use a fully-qualified package name to distinguish it
-from other projects with a similar name (eg. org.apache.maven).
-Typically, when published to the Artifact Manager, the <code>GroupId</code> will get
-slash separated and form part of the URL. E.g. for group id <code>com.example</code>
-and artifact id <code>application</code> would be <code>/com/example/application/</code>.</p>
-</li>
-<li>
-<p><code>Classifier</code>: The Maven dependency notation looks as follows:
-<code>groupId:artifactId:version:classifier</code>. The classifier is additional suffix
-passed to the dependency. E.g. <code>stubs</code>, <code>sources</code>. The same dependency
-e.g. <code>com.example:application</code> can produce multiple artifacts that
-differ from each other with the classifier.</p>
-</li>
-<li>
-<p><code>Artifact manager</code>: When you generate binaries / sources / packages, you would
-like them to be available for others to download / reference or reuse. In case
-of the JVM world those artifacts would be JARs, for Ruby these are gems
-and for Docker those would be Docker images. You can store those artifacts
-in a manager. Examples of such managers can be <a href="https://jfrog.com/artifactory/">Artifactory</a>
-or <a href="https://www.sonatype.org/nexus/">Nexus</a>.</p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_how_it_works_2"><a class="link" href="#_how_it_works_2">4.5.2. How it works</a></h4>
-<div class="paragraph">
-<p>The image searches for contracts under the <code>/contracts</code> folder.
-The output from running the tests will be available under
-<code>/spring-cloud-contract/build</code> folder (it&#8217;s useful for debugging
-purposes).</p>
-</div>
-<div class="paragraph">
-<p>It&#8217;s enough for you to mount your contracts, pass the environment variables
- and the image will:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>generate the contract tests</p>
-</li>
-<li>
-<p>execute the tests against the provided URL</p>
-</li>
-<li>
-<p>generate the <a href="https://github.com/tomakehurst/wiremock">WireMock</a> stubs</p>
-</li>
-<li>
-<p>(optional - turned on by default) publish the stubs to a Artifact Manager</p>
-</li>
-</ul>
-</div>
-<div class="sect4">
-<h5 id="_environment_variables"><a class="link" href="#_environment_variables">Environment Variables</a></h5>
-<div class="paragraph">
-<p>The Docker image requires some environment variables to point to
-your running application, to the Artifact manager instance etc.</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>PROJECT_GROUP</code> - your project&#8217;s group id. Defaults to <code>com.example</code></p>
-</li>
-<li>
-<p><code>PROJECT_VERSION</code> - your project&#8217;s version. Defaults to <code>0.0.1-SNAPSHOT</code></p>
-</li>
-<li>
-<p><code>PROJECT_NAME</code> - artifact id. Defaults to <code>example</code></p>
-</li>
-<li>
-<p><code>PRODUCER_STUBS_CLASSIFIER</code> - archive classifier used for generated producer stubs, defaults to <code>stubs</code>.</p>
-</li>
-<li>
-<p><code>REPO_WITH_BINARIES_URL</code> - URL of your Artifact Manager. Defaults to <code><a href="http://localhost:8081/artifactory/libs-release-local" class="bare">http://localhost:8081/artifactory/libs-release-local</a></code>
-which is the default URL of <a href="https://jfrog.com/artifactory/">Artifactory</a> running locally</p>
-</li>
-<li>
-<p><code>REPO_WITH_BINARIES_USERNAME</code> - (optional) username when the Artifact Manager is secured, defaults to <code>admin</code>.</p>
-</li>
-<li>
-<p><code>REPO_WITH_BINARIES_PASSWORD</code> - (optional) password when the Artifact Manager is secured, defaults to <code>password</code>.</p>
-</li>
-<li>
-<p><code>PUBLISH_ARTIFACTS</code> - if set to <code>true</code> then will publish artifact to binary storage. Defaults to <code>true</code>.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>These environment variables are used when contracts lay in an external repository. To enable
-this feature you must set the <code>EXTERNAL_CONTRACTS_ARTIFACT_ID</code> environment variable.</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>EXTERNAL_CONTRACTS_GROUP_ID</code> - group id of the project with contracts. Defaults to <code>com.example</code></p>
-</li>
-<li>
-<p><code>EXTERNAL_CONTRACTS_ARTIFACT_ID</code>- artifact id of the project with contracts.</p>
-</li>
-<li>
-<p><code>EXTERNAL_CONTRACTS_CLASSIFIER</code>- classifier of the project with contracts. Empty by default</p>
-</li>
-<li>
-<p><code>EXTERNAL_CONTRACTS_VERSION</code> - version of the project with contracts. Defaults to <code>+</code>, equivalent to picking the latest</p>
-</li>
-<li>
-<p><code>EXTERNAL_CONTRACTS_REPO_WITH_BINARIES_URL</code> - URL of your Artifact Manager. Defaults to value of <code>REPO_WITH_BINARIES_URL</code> env var.
-If that&#8217;s not set, defaults to <code><a href="http://localhost:8081/artifactory/libs-release-local" class="bare">http://localhost:8081/artifactory/libs-release-local</a></code>
-which is the default URL of <a href="https://jfrog.com/artifactory/">Artifactory</a> running locally</p>
-</li>
-<li>
-<p><code>EXTERNAL_CONTRACTS_REPO_WITH_BINARIES_USERNAME</code> - (optional) username if the <code>EXTERNAL_CONTRACTS_REPO_WITH_BINARIES_URL</code>
-requires authentication, defaults to <code>REPO_WITH_BINARIES_USERNAME</code>. If that&#8217;s not set defaults to <code>admin</code>.</p>
-</li>
-<li>
-<p><code>EXTERNAL_CONTRACTS_REPO_WITH_BINARIES_PASSWORD</code> - (optional) password if the <code>EXTERNAL_CONTRACTS_REPO_WITH_BINARIES_URL</code>
-requires authentication, defaults to <code>REPO_WITH_BINARIES_PASSWORD</code>. If that&#8217;s not set defaults to <code>password</code>.</p>
-</li>
-<li>
-<p><code>EXTERNAL_CONTRACTS_PATH</code> - path to contracts for the given project, inside the project with contracts.
-Defaults to slash separated <code>EXTERNAL_CONTRACTS_GROUP_ID</code> concatenated with <code>/</code> and <code>EXTERNAL_CONTRACTS_ARTIFACT_ID</code>. E.g.
-for group id <code>foo.bar</code> and artifact id <code>baz</code>, would result in <code>foo/bar/baz</code> contracts path.</p>
-</li>
-<li>
-<p><code>EXTERNAL_CONTRACTS_WORK_OFFLINE</code> - if set to <code>true</code> then will retrieve artifact with contracts
-from the container&#8217;s <code>.m2</code>. Mount your local <code>.m2</code> as a volume available at the container&#8217;s <code>/root/.m2</code> path.
-You must not set both <code>EXTERNAL_CONTRACTS_WORK_OFFLINE</code> and <code>EXTERNAL_CONTRACTS_REPO_WITH_BINARIES_URL</code>.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>These environment variables are used when tests are executed:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>APPLICATION_BASE_URL</code> - url against which tests should be executed.
-Remember that it has to be accessible from the Docker container (e.g. <code>localhost</code>
-will not work)</p>
-</li>
-<li>
-<p><code>APPLICATION_USERNAME</code> - (optional) username for basic authentication to your application</p>
-</li>
-<li>
-<p><code>APPLICATION_PASSWORD</code> - (optional) password for basic authentication to your application</p>
-</li>
-</ul>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_example_of_usage"><a class="link" href="#_example_of_usage">4.5.3. Example of usage</a></h4>
-<div class="paragraph">
-<p>Let&#8217;s take a look at a simple MVC application</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ git clone https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs
-$ cd bookstore</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The contracts are available under <code>/contracts</code> folder.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="docker-server-side"><a class="link" href="#docker-server-side">4.5.4. Server side (nodejs)</a></h4>
-<div class="paragraph">
-<p>Since we want to run tests, we could just execute:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ npm test</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>however, for learning purposes, let&#8217;s split it into pieces:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash"># Stop docker infra (nodejs, artifactory)
-$ ./stop_infra.sh
-# Start docker infra (nodejs, artifactory)
-$ ./setup_infra.sh
-
-# Kill &amp; Run app
-$ pkill -f "node app"
-$ nohup node app &amp;
-
-# Prepare environment variables
-$ SC_CONTRACT_DOCKER_VERSION="..."
-$ APP_IP="192.168.0.100"
-$ APP_PORT="3000"
-$ ARTIFACTORY_PORT="8081"
-$ APPLICATION_BASE_URL="http://${APP_IP}:${APP_PORT}"
-$ ARTIFACTORY_URL="http://${APP_IP}:${ARTIFACTORY_PORT}/artifactory/libs-release-local"
-$ CURRENT_DIR="$( pwd )"
-$ CURRENT_FOLDER_NAME=${PWD##*/}
-$ PROJECT_VERSION="0.0.1.RELEASE"
-
-# Execute contract tests
-$ docker run  --rm -e "APPLICATION_BASE_URL=${APPLICATION_BASE_URL}" -e "PUBLISH_ARTIFACTS=true" -e "PROJECT_NAME=${CURRENT_FOLDER_NAME}" -e "REPO_WITH_BINARIES_URL=${ARTIFACTORY_URL}" -e "PROJECT_VERSION=${PROJECT_VERSION}" -v "${CURRENT_DIR}/contracts/:/contracts:ro" -v "${CURRENT_DIR}/node_modules/spring-cloud-contract/output:/spring-cloud-contract-output/" springcloud/spring-cloud-contract:"${SC_CONTRACT_DOCKER_VERSION}"
-
-# Kill app
-$ pkill -f "node app"</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>What will happen is that via bash scripts:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>infrastructure will be set up (MongoDb, Artifactory).
-In real life scenario you would just run the NodeJS application
-with mocked database. In this example we want to show how we can
-benefit from Spring Cloud Contract in no time.</p>
-</li>
-<li>
-<p>due to those constraints the contracts also represent the
-stateful situation</p>
-<div class="ulist">
-<ul>
-<li>
-<p>first request is a <code>POST</code> that causes data to get inserted to the database</p>
-</li>
-<li>
-<p>second request is a <code>GET</code> that returns a list of data with 1 previously inserted element</p>
-</li>
-</ul>
-</div>
-</li>
-<li>
-<p>the NodeJS application will be started (on port <code>3000</code>)</p>
-</li>
-<li>
-<p>contract tests will be generated via Docker and tests
-will be executed against the running application</p>
-<div class="ulist">
-<ul>
-<li>
-<p>the contracts will be taken from <code>/contracts</code> folder.</p>
-</li>
-<li>
-<p>the output of the test execution is available under
-<code>node_modules/spring-cloud-contract/output</code>.</p>
-</li>
-</ul>
-</div>
-</li>
-<li>
-<p>the stubs will be uploaded to Artifactory. You can check them out
-under <a href="http://localhost:8081/artifactory/libs-release-local/com/example/bookstore/0.0.1.RELEASE/" class="bare">http://localhost:8081/artifactory/libs-release-local/com/example/bookstore/0.0.1.RELEASE/</a> .
-The stubs will be here <a href="http://localhost:8081/artifactory/libs-release-local/com/example/bookstore/0.0.1.RELEASE/bookstore-0.0.1.RELEASE-stubs.jar" class="bare">http://localhost:8081/artifactory/libs-release-local/com/example/bookstore/0.0.1.RELEASE/bookstore-0.0.1.RELEASE-stubs.jar</a>.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>To see how the client side looks like check out the <a href="#stubrunner-docker">Stub Runner Docker</a> section.</p>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_spring_cloud_contract_verifier_messaging"><a class="link" href="#_spring_cloud_contract_verifier_messaging">5. Spring Cloud Contract Verifier Messaging</a></h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>Spring Cloud Contract Verifier lets you verify applications that use messaging as a
-means of communication. All of the integrations shown in this document work with Spring,
-but you can also create one of your own and use that.</p>
-</div>
-<div class="sect2">
-<h3 id="_integrations"><a class="link" href="#_integrations">5.1. Integrations</a></h3>
-<div class="paragraph">
-<p>You can use one of the following four integration configurations:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Apache Camel</p>
-</li>
-<li>
-<p>Spring Integration</p>
-</li>
-<li>
-<p>Spring Cloud Stream</p>
-</li>
-<li>
-<p>Spring AMQP</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Since we use Spring Boot, if you have added one of these libraries to the classpath, all
-the messaging configuration is automatically set up.</p>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-Remember to put <code>@AutoConfigureMessageVerifier</code> on the base class of your
-generated tests. Otherwise, messaging part of Spring Cloud Contract Verifier does not
-work.
-</td>
-</tr>
-</table>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-If you want to use Spring Cloud Stream, remember to add a dependency on
-<code>org.springframework.cloud:spring-cloud-stream-test-support</code>, as shown here:
-</td>
-</tr>
-</table>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
-    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-    &lt;artifactId&gt;spring-cloud-stream-test-support&lt;/artifactId&gt;
-    &lt;scope&gt;test&lt;/scope&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">testCompile "org.springframework.cloud:spring-cloud-stream-test-support"</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_manual_integration_testing"><a class="link" href="#_manual_integration_testing">5.2. Manual Integration Testing</a></h3>
-<div class="paragraph">
-<p>The main interface used by the tests is
-<code>org.springframework.cloud.contract.verifier.messaging.MessageVerifier</code>.
-It defines how to send and receive messages. You can create your own implementation to
-achieve the same goal.</p>
-</div>
-<div class="paragraph">
-<p>In a test, you can inject a <code>ContractVerifierMessageExchange</code> to send and receive
-messages that follow the contract. Then add <code>@AutoConfigureMessageVerifier</code> to your test.
-Here&#8217;s an example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringTestRunner.class)
-@SpringBootTest
-@AutoConfigureMessageVerifier
-public static class MessagingContractTests {
-
-  @Autowired
-  private MessageVerifier verifier;
-  ...
-}</code></pre>
-</div>
-</div>
-<div class="admonitionblock note">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-note" title="Note"></i>
-</td>
-<td class="content">
-If your tests require stubs as well, then <code>@AutoConfigureStubRunner</code> includes the
-messaging configuration, so you only need the one annotation.
-</td>
-</tr>
-</table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_publisher_side_test_generation"><a class="link" href="#_publisher_side_test_generation">5.3. Publisher-Side Test Generation</a></h3>
-<div class="paragraph">
-<p>Having the <code>input</code> or <code>outputMessage</code> sections in your DSL results in creation of tests
-on the publisher&#8217;s side. By default, JUnit 4 tests are created. However, there is also a
-possibility to create JUnit 5, TestNG or Spock tests.</p>
-</div>
-<div class="paragraph">
-<p>There are 3 main scenarios that we should take into consideration:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Scenario 1: There is no input message that produces an output message. The output
-message  is triggered by a component inside the application (for example, scheduler).</p>
-</li>
-<li>
-<p>Scenario 2: The input message triggers an output message.</p>
-</li>
-<li>
-<p>Scenario 3: The input message is consumed and there is no output message.</p>
-</li>
-</ul>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-The destination passed to <code>messageFrom</code> or <code>sentTo</code> can have different
-meanings for different messaging implementations. For <strong>Stream</strong> and <strong>Integration</strong> it is
-first resolved as a <code>destination</code> of a channel. Then, if there is no such <code>destination</code>
-it is resolved as a channel name. For <strong>Camel</strong>, that&#8217;s a certain component (for example,
-<code>jms</code>).
-</td>
-</tr>
-</table>
-</div>
-<div class="sect3">
-<h4 id="_scenario_1_no_input_message"><a class="link" href="#_scenario_1_no_input_message">5.3.1. Scenario 1: No Input Message</a></h4>
-<div class="paragraph">
-<p>For the given contract:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">			def contractDsl = Contract.make {
-				name "foo"
-				label 'some_label'
-				input {
-					triggeredBy('bookReturnedTriggered()')
-				}
-				outputMessage {
-					sentTo('activemq:output')
-					body('''{ "bookName" : "foo" }''')
-					headers {
-						header('BOOK-NAME', 'foo')
-						messagingContentType(applicationJson())
-					}
-				}
-			}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">label: some_label
-input:
-  triggeredBy: bookReturnedTriggered
-outputMessage:
-  sentTo: activemq:output
-  body:
-    bookName: foo
-  headers:
-    BOOK-NAME: foo
-    contentType: application/json</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following JUnit test is created:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">					'''\
-package com.example;
-
-import com.jayway.jsonpath.DocumentContext;
-import com.jayway.jsonpath.JsonPath;
-import org.junit.Test;
-import org.junit.Rule;
-import javax.inject.Inject;
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierObjectMapper;
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessage;
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessaging;
-
-import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat;
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*;
-import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson;
-import static org.springframework.cloud.contract.verifier.messaging.util.ContractVerifierMessagingUtil.headers;
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.fileToBytes;
-
-@SuppressWarnings("rawtypes")
-public class FooTest {
-\t@Inject ContractVerifierMessaging contractVerifierMessaging;
-\t@Inject ContractVerifierObjectMapper contractVerifierObjectMapper;
-
-\t@Test
-\tpublic void validate_foo() throws Exception {
-\t\t// when:
-\t\t\tbookReturnedTriggered();
-
-\t\t// then:
-\t\t\tContractVerifierMessage response = contractVerifierMessaging.receive("activemq:output");
-\t\t\tassertThat(response).isNotNull();
-
-\t\t// and:
-\t\t\tassertThat(response.getHeader("BOOK-NAME")).isNotNull();
-\t\t\tassertThat(response.getHeader("BOOK-NAME").toString()).isEqualTo("foo");
-\t\t\tassertThat(response.getHeader("contentType")).isNotNull();
-\t\t\tassertThat(response.getHeader("contentType").toString()).isEqualTo("application/json");
-
-\t\t// and:
-\t\t\tDocumentContext parsedJson = JsonPath.parse(contractVerifierObjectMapper.writeValueAsString(response.getPayload()));
-\t\t\tassertThatJson(parsedJson).field("['bookName']").isEqualTo("foo");
-\t}
-
-}
-
-'''</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>And the following Spock test would be created:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">					'''\
-package com.example
-
-import com.jayway.jsonpath.DocumentContext
-import com.jayway.jsonpath.JsonPath
-import spock.lang.Specification
-import javax.inject.Inject
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierObjectMapper
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessage
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessaging
-
-import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*
-import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson
-import static org.springframework.cloud.contract.verifier.messaging.util.ContractVerifierMessagingUtil.headers
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.fileToBytes
-
-@SuppressWarnings("rawtypes")
-class FooSpec extends Specification {
-\t@Inject ContractVerifierMessaging contractVerifierMessaging
-\t@Inject ContractVerifierObjectMapper contractVerifierObjectMapper
-
-\tdef validate_foo() throws Exception {
-\t\twhen:
-\t\t\tbookReturnedTriggered()
-
-\t\tthen:
-\t\t\tContractVerifierMessage response = contractVerifierMessaging.receive("activemq:output")
-\t\t\tresponse != null
-
-\t\tand:
-\t\t\tresponse.getHeader("BOOK-NAME") != null
-\t\t\tresponse.getHeader("BOOK-NAME").toString() == 'foo'
-\t\t\tresponse.getHeader("contentType") != null
-\t\t\tresponse.getHeader("contentType").toString() == 'application/json'
-
-\t\tand:
-\t\t\tDocumentContext parsedJson = JsonPath.parse(contractVerifierObjectMapper.writeValueAsString(response.getPayload()))
-\t\t\tassertThatJson(parsedJson).field("['bookName']").isEqualTo("foo")
-\t}
-
-}
-
-'''</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_scenario_2_output_triggered_by_input"><a class="link" href="#_scenario_2_output_triggered_by_input">5.3.2. Scenario 2: Output Triggered by Input</a></h4>
-<div class="paragraph">
-<p>For the given contract:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">			def contractDsl = Contract.make {
-				name "foo"
-				label 'some_label'
-				input {
-					messageFrom('jms:input')
-					messageBody([
-							bookName: 'foo'
-					])
-					messageHeaders {
-						header('sample', 'header')
-					}
-				}
-				outputMessage {
-					sentTo('jms:output')
-					body([
-							bookName: 'foo'
-					])
-					headers {
-						header('BOOK-NAME', 'foo')
-					}
-				}
-			}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">label: some_label
-input:
-  messageFrom: jms:input
-  messageBody:
-    bookName: 'foo'
-  messageHeaders:
-    sample: header
-outputMessage:
-  sentTo: jms:output
-  body:
-    bookName: foo
-  headers:
-    BOOK-NAME: foo</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following JUnit test is created:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">					'''\
-package com.example;
-
-import com.jayway.jsonpath.DocumentContext;
-import com.jayway.jsonpath.JsonPath;
-import org.junit.Test;
-import org.junit.Rule;
-import javax.inject.Inject;
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierObjectMapper;
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessage;
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessaging;
-
-import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat;
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*;
-import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson;
-import static org.springframework.cloud.contract.verifier.messaging.util.ContractVerifierMessagingUtil.headers;
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.fileToBytes;
-
-@SuppressWarnings("rawtypes")
-public class FooTest {
-\t@Inject ContractVerifierMessaging contractVerifierMessaging;
-\t@Inject ContractVerifierObjectMapper contractVerifierObjectMapper;
-
-\t@Test
-\tpublic void validate_foo() throws Exception {
-\t\t// given:
-\t\t\tContractVerifierMessage inputMessage = contractVerifierMessaging.create(
-\t\t\t\t\t"{\\"bookName\\":\\"foo\\"}"
-\t\t\t\t\t\t, headers()
-\t\t\t\t\t\t\t.header("sample", "header")
-\t\t\t);
-
-\t\t// when:
-\t\t\tcontractVerifierMessaging.send(inputMessage, "jms:input");
-
-\t\t// then:
-\t\t\tContractVerifierMessage response = contractVerifierMessaging.receive("jms:output");
-\t\t\tassertThat(response).isNotNull();
-
-\t\t// and:
-\t\t\tassertThat(response.getHeader("BOOK-NAME")).isNotNull();
-\t\t\tassertThat(response.getHeader("BOOK-NAME").toString()).isEqualTo("foo");
-
-\t\t// and:
-\t\t\tDocumentContext parsedJson = JsonPath.parse(contractVerifierObjectMapper.writeValueAsString(response.getPayload()));
-\t\t\tassertThatJson(parsedJson).field("['bookName']").isEqualTo("foo");
-\t}
-
-}
-
-'''</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>And the following Spock test would be created:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">					"""\
-package com.example
-
-import com.jayway.jsonpath.DocumentContext
-import com.jayway.jsonpath.JsonPath
-import spock.lang.Specification
-import javax.inject.Inject
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierObjectMapper
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessage
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessaging
-
-import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*
-import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson
-import static org.springframework.cloud.contract.verifier.messaging.util.ContractVerifierMessagingUtil.headers
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.fileToBytes
-
-@SuppressWarnings("rawtypes")
-class FooSpec extends Specification {
-\t@Inject ContractVerifierMessaging contractVerifierMessaging
-\t@Inject ContractVerifierObjectMapper contractVerifierObjectMapper
-
-\tdef validate_foo() throws Exception {
-\t\tgiven:
-\t\t\tContractVerifierMessage inputMessage = contractVerifierMessaging.create(
-\t\t\t\t\t'''{"bookName":"foo"}'''
-\t\t\t\t\t\t, headers()
-\t\t\t\t\t\t\t.header("sample", "header")
-\t\t\t)
-
-\t\twhen:
-\t\t\tcontractVerifierMessaging.send(inputMessage, "jms:input")
-
-\t\tthen:
-\t\t\tContractVerifierMessage response = contractVerifierMessaging.receive("jms:output")
-\t\t\tresponse != null
-
-\t\tand:
-\t\t\tresponse.getHeader("BOOK-NAME") != null
-\t\t\tresponse.getHeader("BOOK-NAME").toString() == 'foo'
-
-\t\tand:
-\t\t\tDocumentContext parsedJson = JsonPath.parse(contractVerifierObjectMapper.writeValueAsString(response.getPayload()))
-\t\t\tassertThatJson(parsedJson).field("['bookName']").isEqualTo("foo")
-\t}
-
-}
-
-"""</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_scenario_3_no_output_message"><a class="link" href="#_scenario_3_no_output_message">5.3.3. Scenario 3: No Output Message</a></h4>
-<div class="paragraph">
-<p>For the given contract:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">			def contractDsl = Contract.make {
-				name "foo"
-				label 'some_label'
-				input {
-					messageFrom('jms:delete')
-					messageBody([
-							bookName: 'foo'
-					])
-					messageHeaders {
-						header('sample', 'header')
-					}
-					assertThat('bookWasDeleted()')
-				}
-			}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">label: some_label
-input:
-  messageFrom: jms:delete
-  messageBody:
-    bookName: 'foo'
-  messageHeaders:
-    sample: header
-  assertThat: bookWasDeleted()</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following JUnit test is created:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">					"""\
-package com.example;
-
-import com.jayway.jsonpath.DocumentContext;
-import com.jayway.jsonpath.JsonPath;
-import org.junit.Test;
-import org.junit.Rule;
-import javax.inject.Inject;
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierObjectMapper;
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessage;
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessaging;
-
-import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat;
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*;
-import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson;
-import static org.springframework.cloud.contract.verifier.messaging.util.ContractVerifierMessagingUtil.headers;
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.fileToBytes;
-
-@SuppressWarnings("rawtypes")
-public class FooTest {
-\t@Inject ContractVerifierMessaging contractVerifierMessaging;
-\t@Inject ContractVerifierObjectMapper contractVerifierObjectMapper;
-
-\t@Test
-\tpublic void validate_foo() throws Exception {
-\t\t// given:
-\t\t\tContractVerifierMessage inputMessage = contractVerifierMessaging.create(
-\t\t\t\t\t"{\\"bookName\\":\\"foo\\"}"
-\t\t\t\t\t\t, headers()
-\t\t\t\t\t\t\t.header("sample", "header")
-\t\t\t);
-
-\t\t// when:
-\t\t\tcontractVerifierMessaging.send(inputMessage, "jms:delete");
-\t\t\tbookWasDeleted();
-
-\t}
-
-}
-
-"""</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>And the following Spock test would be created:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">					"""\
-package com.example
-
-import com.jayway.jsonpath.DocumentContext
-import com.jayway.jsonpath.JsonPath
-import spock.lang.Specification
-import javax.inject.Inject
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierObjectMapper
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessage
-import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessaging
-
-import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*
-import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson
-import static org.springframework.cloud.contract.verifier.messaging.util.ContractVerifierMessagingUtil.headers
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.fileToBytes
-
-@SuppressWarnings("rawtypes")
-class FooSpec extends Specification {
-\t@Inject ContractVerifierMessaging contractVerifierMessaging
-\t@Inject ContractVerifierObjectMapper contractVerifierObjectMapper
-
-\tdef validate_foo() throws Exception {
-\t\tgiven:
-\t\t\tContractVerifierMessage inputMessage = contractVerifierMessaging.create(
-\t\t\t\t\t'''{"bookName":"foo"}'''
-\t\t\t\t\t\t, headers()
-\t\t\t\t\t\t\t.header("sample", "header")
-\t\t\t)
-
-\t\twhen:
-\t\t\tcontractVerifierMessaging.send(inputMessage, "jms:delete")
-\t\t\tbookWasDeleted()
-
-\t\tthen:
-\t\t\tnoExceptionThrown()
-\t}
-
-}
-"""</code></pre>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_consumer_stub_generation"><a class="link" href="#_consumer_stub_generation">5.4. Consumer Stub Generation</a></h3>
-<div class="paragraph">
-<p>Unlike the HTTP part, in messaging, we need to publish the Groovy DSL inside the JAR with
-a stub. Then it is parsed on the consumer side and proper stubbed routes are created.</p>
-</div>
-<div class="paragraph">
-<p>For more information, see <a href="#stub-runner-for-messaging">Stub Runner for Messaging</a> section.</p>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependencies&gt;
-	&lt;dependency&gt;
-		&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-		&lt;artifactId&gt;spring-cloud-starter-stream-rabbit&lt;/artifactId&gt;
-	&lt;/dependency&gt;
-
-	&lt;dependency&gt;
-		&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-		&lt;artifactId&gt;spring-cloud-starter-contract-stub-runner&lt;/artifactId&gt;
-		&lt;scope&gt;test&lt;/scope&gt;
-	&lt;/dependency&gt;
-	&lt;dependency&gt;
-		&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-		&lt;artifactId&gt;spring-cloud-stream-test-support&lt;/artifactId&gt;
-		&lt;scope&gt;test&lt;/scope&gt;
-	&lt;/dependency&gt;
-&lt;/dependencies&gt;
-
-&lt;dependencyManagement&gt;
-	&lt;dependencies&gt;
-		&lt;dependency&gt;
-			&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-			&lt;artifactId&gt;spring-cloud-dependencies&lt;/artifactId&gt;
-			&lt;version&gt;Hoxton.BUILD-SNAPSHOT&lt;/version&gt;
-			&lt;type&gt;pom&lt;/type&gt;
-			&lt;scope&gt;import&lt;/scope&gt;
-		&lt;/dependency&gt;
-	&lt;/dependencies&gt;
-&lt;/dependencyManagement&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">ext {
-	contractsDir = file("mappings")
-	stubsOutputDirRoot = file("${project.buildDir}/production/${project.name}-stubs/")
-}
-
-// Automatically added by plugin:
-// copyContracts - copies contracts to the output folder from which JAR will be created
-// verifierStubsJar - JAR with a provided stub suffix
-// the presented publication is also added by the plugin but you can modify it as you wish
-
-publishing {
-	publications {
-		stubs(MavenPublication) {
-			artifactId "${project.name}-stubs"
-			artifact verifierStubsJar
-		}
-	}
-}</code></pre>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_spring_cloud_contract_stub_runner"><a class="link" href="#_spring_cloud_contract_stub_runner">6. Spring Cloud Contract Stub Runner</a></h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>One of the issues that you might encounter while using Spring Cloud Contract Verifier is
-passing the generated WireMock JSON stubs from the server side to the client side (or to
-various clients). The same takes place in terms of client-side generation for messaging.</p>
-</div>
-<div class="paragraph">
-<p>Copying the JSON files and setting the client side for messaging manually is out of the
-question. That is why we introduced Spring Cloud Contract Stub Runner. It can
-automatically download and run the stubs for you.</p>
-</div>
-<div class="sect2">
-<h3 id="_snapshot_versions"><a class="link" href="#_snapshot_versions">6.1. Snapshot versions</a></h3>
-<div class="paragraph">
-<p>Add the additional snapshot repository to your <code>build.gradle</code> file to use snapshot
-versions, which are automatically uploaded after every successful build:</p>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;repositories&gt;
-	&lt;repository&gt;
-		&lt;id&gt;spring-snapshots&lt;/id&gt;
-		&lt;name&gt;Spring Snapshots&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;true&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/repository&gt;
-	&lt;repository&gt;
-		&lt;id&gt;spring-milestones&lt;/id&gt;
-		&lt;name&gt;Spring Milestones&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;false&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/repository&gt;
-	&lt;repository&gt;
-		&lt;id&gt;spring-releases&lt;/id&gt;
-		&lt;name&gt;Spring Releases&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;false&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/repository&gt;
-&lt;/repositories&gt;
-&lt;pluginRepositories&gt;
-	&lt;pluginRepository&gt;
-		&lt;id&gt;spring-snapshots&lt;/id&gt;
-		&lt;name&gt;Spring Snapshots&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;true&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/pluginRepository&gt;
-	&lt;pluginRepository&gt;
-		&lt;id&gt;spring-milestones&lt;/id&gt;
-		&lt;name&gt;Spring Milestones&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;false&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/pluginRepository&gt;
-	&lt;pluginRepository&gt;
-		&lt;id&gt;spring-releases&lt;/id&gt;
-		&lt;name&gt;Spring Releases&lt;/name&gt;
-		&lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
-		&lt;snapshots&gt;
-			&lt;enabled&gt;false&lt;/enabled&gt;
-		&lt;/snapshots&gt;
-	&lt;/pluginRepository&gt;
-&lt;/pluginRepositories&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">buildscript {
-	repositories {
-		mavenCentral()
-		mavenLocal()
-		maven { url "https://repo.spring.io/snapshot" }
-		maven { url "https://repo.spring.io/milestone" }
-		maven { url "https://repo.spring.io/release" }
-	}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="publishing-stubs-as-jars"><a class="link" href="#publishing-stubs-as-jars">6.2. Publishing Stubs as JARs</a></h3>
-<div class="paragraph">
-<p>The easiest approach would be to centralize the way stubs are kept. For example, you can
-keep them as jars in a Maven repository.</p>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-For both Maven and Gradle, the setup comes ready to work. However, you can customize
-it if you want to.
-</td>
-</tr>
-</table>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;!-- First disable the default jar setup in the properties section --&gt;
-&lt;!-- we don't want the verifier to do a jar for us --&gt;
-&lt;spring.cloud.contract.verifier.skip&gt;true&lt;/spring.cloud.contract.verifier.skip&gt;
-
-&lt;!-- Next add the assembly plugin to your build --&gt;
-&lt;!-- we want the assembly plugin to generate the JAR --&gt;
-&lt;plugin&gt;
-	&lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
-	&lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
-	&lt;executions&gt;
-		&lt;execution&gt;
-			&lt;id&gt;stub&lt;/id&gt;
-			&lt;phase&gt;prepare-package&lt;/phase&gt;
-			&lt;goals&gt;
-				&lt;goal&gt;single&lt;/goal&gt;
-			&lt;/goals&gt;
-			&lt;inherited&gt;false&lt;/inherited&gt;
-			&lt;configuration&gt;
-				&lt;attach&gt;true&lt;/attach&gt;
-				&lt;descriptors&gt;
-					${basedir}/src/assembly/stub.xml
-				&lt;/descriptors&gt;
-			&lt;/configuration&gt;
-		&lt;/execution&gt;
-	&lt;/executions&gt;
-&lt;/plugin&gt;
-
-&lt;!-- Finally setup your assembly. Below you can find the contents of src/main/assembly/stub.xml --&gt;
-&lt;assembly
-	xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3"
-	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-	xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3 https://maven.apache.org/xsd/assembly-1.1.3.xsd"&gt;
-	&lt;id&gt;stubs&lt;/id&gt;
-	&lt;formats&gt;
-		&lt;format&gt;jar&lt;/format&gt;
-	&lt;/formats&gt;
-	&lt;includeBaseDirectory&gt;false&lt;/includeBaseDirectory&gt;
-	&lt;fileSets&gt;
-		&lt;fileSet&gt;
-			&lt;directory&gt;src/main/java&lt;/directory&gt;
-			&lt;outputDirectory&gt;/&lt;/outputDirectory&gt;
-			&lt;includes&gt;
-				&lt;include&gt;**com/example/model/*.*&lt;/include&gt;
-			&lt;/includes&gt;
-		&lt;/fileSet&gt;
-		&lt;fileSet&gt;
-			&lt;directory&gt;${project.build.directory}/classes&lt;/directory&gt;
-			&lt;outputDirectory&gt;/&lt;/outputDirectory&gt;
-			&lt;includes&gt;
-				&lt;include&gt;**com/example/model/*.*&lt;/include&gt;
-			&lt;/includes&gt;
-		&lt;/fileSet&gt;
-		&lt;fileSet&gt;
-			&lt;directory&gt;${project.build.directory}/snippets/stubs&lt;/directory&gt;
-			&lt;outputDirectory&gt;META-INF/${project.groupId}/${project.artifactId}/${project.version}/mappings&lt;/outputDirectory&gt;
-			&lt;includes&gt;
-				&lt;include&gt;**/*&lt;/include&gt;
-			&lt;/includes&gt;
-		&lt;/fileSet&gt;
-		&lt;fileSet&gt;
-			&lt;directory&gt;${basedir}/src/test/resources/contracts&lt;/directory&gt;
-			&lt;outputDirectory&gt;META-INF/${project.groupId}/${project.artifactId}/${project.version}/contracts&lt;/outputDirectory&gt;
-			&lt;includes&gt;
-				&lt;include&gt;**/*.groovy&lt;/include&gt;
-			&lt;/includes&gt;
-		&lt;/fileSet&gt;
-	&lt;/fileSets&gt;
-&lt;/assembly&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">ext {
-	contractsDir = file("mappings")
-	stubsOutputDirRoot = file("${project.buildDir}/production/${project.name}-stubs/")
-}
-
-// Automatically added by plugin:
-// copyContracts - copies contracts to the output folder from which JAR will be created
-// verifierStubsJar - JAR with a provided stub suffix
-// the presented publication is also added by the plugin but you can modify it as you wish
-
-publishing {
-	publications {
-		stubs(MavenPublication) {
-			artifactId "${project.name}-stubs"
-			artifact verifierStubsJar
-		}
-	}
-}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_stub_runner_core"><a class="link" href="#_stub_runner_core">6.3. Stub Runner Core</a></h3>
-<div class="paragraph">
-<p>Runs stubs for service collaborators. Treating stubs as contracts of services allows to use stub-runner as an implementation of
-<a href="https://martinfowler.com/articles/consumerDrivenContracts.html">Consumer Driven Contracts</a>.</p>
-</div>
-<div class="paragraph">
-<p>Stub Runner allows you to automatically download the stubs of the provided dependencies (or pick those from the classpath), start WireMock servers for them and feed them with proper stub definitions.
-For messaging, special stub routes are defined.</p>
-</div>
-<div class="sect3">
-<h4 id="_retrieving_stubs"><a class="link" href="#_retrieving_stubs">6.3.1. Retrieving stubs</a></h4>
-<div class="paragraph">
-<p>You can pick the following options of acquiring stubs</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Aether based solution that downloads JARs with stubs from Artifactory / Nexus</p>
-</li>
-<li>
-<p>Classpath scanning solution that searches classpath via pattern to retrieve stubs</p>
-</li>
-<li>
-<p>Write your own implementation of the <code>org.springframework.cloud.contract.stubrunner.StubDownloaderBuilder</code> for full customization</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>The latter example is described in the <a href="#custom_stub_runner">Custom Stub Runner</a> section.</p>
-</div>
-<div class="sect4">
-<h5 id="_stub_downloading"><a class="link" href="#_stub_downloading">Stub downloading</a></h5>
-<div class="paragraph">
-<p>You can control the stub downloading via the <code>stubsMode</code> switch. It picks value from the
-<code>StubRunnerProperties.StubsMode</code> enum. You can use the following options</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>StubRunnerProperties.StubsMode.CLASSPATH</code> (default value) - will pick stubs from the classpath</p>
-</li>
-<li>
-<p><code>StubRunnerProperties.StubsMode.LOCAL</code> - will pick stubs from a local storage (e.g. <code>.m2</code>)</p>
-</li>
-<li>
-<p><code>StubRunnerProperties.StubsMode.REMOTE</code> - will pick stubs from a remote location</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(repositoryRoot="https://foo.bar", ids = "com.example:beer-api-producer:+:stubs:8095", stubsMode = StubRunnerProperties.StubsMode.LOCAL)</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_classpath_scanning"><a class="link" href="#_classpath_scanning">Classpath scanning</a></h5>
-<div class="paragraph">
-<p>If you set the <code>stubsMode</code> property to <code>StubRunnerProperties.StubsMode.CLASSPATH</code>
-(or set nothing since <code>CLASSPATH</code> is the default value) then classpath will get scanned.
-Let&#8217;s look at the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(ids = {
-    "com.example:beer-api-producer:+:stubs:8095",
-    "com.example.foo:bar:1.0.0:superstubs:8096"
-})</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>If you&#8217;ve added the dependencies to your classpath</p>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
-    &lt;groupId&gt;com.example&lt;/groupId&gt;
-    &lt;artifactId&gt;beer-api-producer-restdocs&lt;/artifactId&gt;
-    &lt;classifier&gt;stubs&lt;/classifier&gt;
-    &lt;version&gt;0.0.1-SNAPSHOT&lt;/version&gt;
-    &lt;scope&gt;test&lt;/scope&gt;
-    &lt;exclusions&gt;
-        &lt;exclusion&gt;
-            &lt;groupId&gt;*&lt;/groupId&gt;
-            &lt;artifactId&gt;*&lt;/artifactId&gt;
-        &lt;/exclusion&gt;
-    &lt;/exclusions&gt;
-&lt;/dependency&gt;
-&lt;dependency&gt;
-    &lt;groupId&gt;com.example.foo&lt;/groupId&gt;
-    &lt;artifactId&gt;bar&lt;/artifactId&gt;
-    &lt;classifier&gt;superstubs&lt;/classifier&gt;
-    &lt;version&gt;1.0.0&lt;/version&gt;
-    &lt;scope&gt;test&lt;/scope&gt;
-    &lt;exclusions&gt;
-        &lt;exclusion&gt;
-            &lt;groupId&gt;*&lt;/groupId&gt;
-            &lt;artifactId&gt;*&lt;/artifactId&gt;
-        &lt;/exclusion&gt;
-    &lt;/exclusions&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">testCompile("com.example:beer-api-producer-restdocs:0.0.1-SNAPSHOT:stubs") {
-    transitive = false
-}
-testCompile("com.example.foo:bar:1.0.0:superstubs") {
-    transitive = false
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Then the following locations on your classpath will get scanned. For <code>com.example:beer-api-producer-restdocs</code></p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>/META-INF/com.example/beer-api-producer-restdocs/<strong>*/</strong>.*</p>
-</li>
-<li>
-<p>/contracts/com.example/beer-api-producer-restdocs/<strong>*/</strong>.*</p>
-</li>
-<li>
-<p>/mappings/com.example/beer-api-producer-restdocs/<strong>*/</strong>.*</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>and <code>com.example.foo:bar</code></p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>/META-INF/com.example.foo/bar/<strong>*/</strong>.*</p>
-</li>
-<li>
-<p>/contracts/com.example.foo/bar/<strong>*/</strong>.*</p>
-</li>
-<li>
-<p>/mappings/com.example.foo/bar/<strong>*/</strong>.*</p>
-</li>
-</ul>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-As you can see you have to explicitly provide the group and artifact ids when packaging the
-producer stubs.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>The producer would setup the contracts like this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── src
-    └── test
-        └── resources
-            └── contracts
-                └── com.example
-                    └── beer-api-producer-restdocs
-                        └── nested
-                            └── contract3.groovy</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>To achieve proper stub packaging.</p>
-</div>
-<div class="paragraph">
-<p>Or using the <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/blob/2.2.x/producer_with_restdocs/pom.xml">Maven <code>assembly</code> plugin</a> or
-<a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/blob/2.2.x/producer_with_restdocs/build.gradle">Gradle Jar</a> task you have to create the following
-structure in your stubs jar.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── META-INF
-    └── com.example
-        └── beer-api-producer-restdocs
-            └── 2.0.0
-                ├── contracts
-                │   └── nested
-                │       └── contract2.groovy
-                └── mappings
-                    └── mapping.json</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>By maintaining this structure classpath gets scanned and you can profit from the messaging /
-HTTP stubs without the need to download artifacts.</p>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_configuring_http_server_stubs"><a class="link" href="#_configuring_http_server_stubs">Configuring HTTP Server Stubs</a></h5>
-<div class="paragraph">
-<p>Stub Runner has a notion of a <code>HttpServerStub</code> that abstracts the underlaying
-concrete implementation of the HTTP server (e.g. WireMock is one of the implementations).
-Sometimes, you need to perform some additional tuning of the stub servers,
-that is concrete for the given implementation. To do that, Stub Runner gives you
-the <code>httpServerStubConfigurer</code> property that is available in the annotation,
-JUnit rule, and is accessible via system properties, where you can provide
-your implementation of the <code>org.springframework.cloud.contract.stubrunner.HttpServerStubConfigurer</code> interface. The implementations can alter
-the configuration files for the given HTTP server stub.</p>
-</div>
-<div class="paragraph">
-<p>Spring Cloud Contract Stub Runner comes with an implementation that you
-can extend, for WireMock - <code>org.springframework.cloud.contract.stubrunner.provider.wiremock.WireMockHttpServerStubConfigurer</code>. In the <code>configure</code> method
-you can provide your own, custom configuration for the given stub. The use
-case might be starting WireMock for the given artifact id, on an HTTPs port. Example:</p>
-</div>
-<div class="listingblock">
-<div class="title">WireMockHttpServerStubConfigurer implementation</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@CompileStatic
-static class HttpsForFraudDetection extends WireMockHttpServerStubConfigurer {
-
-	private static final Log log = LogFactory.getLog(HttpsForFraudDetection)
-
-	@Override
-	WireMockConfiguration configure(WireMockConfiguration httpStubConfiguration, HttpServerStubConfiguration httpServerStubConfiguration) {
-		if (httpServerStubConfiguration.stubConfiguration.artifactId == "fraudDetectionServer") {
-			int httpsPort = SocketUtils.findAvailableTcpPort()
-			log.info("Will set HTTPs port [" + httpsPort + "] for fraud detection server")
-			return httpStubConfiguration
-					.httpsPort(httpsPort)
-		}
-		return httpStubConfiguration
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You can then reuse it via the annotation</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@AutoConfigureStubRunner(mappingsOutputFolder = "target/outputmappings/",
-		httpServerStubConfigurer = HttpsForFraudDetection)</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Whenever an https port is found, it will take precedence over the http one.</p>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_running_stubs"><a class="link" href="#_running_stubs">6.3.2. Running stubs</a></h4>
-<div class="sect4">
-<h5 id="_running_using_main_app"><a class="link" href="#_running_using_main_app">Running using main app</a></h5>
-<div class="paragraph">
-<p>You can set the following options to the main class:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">-c, --classifier                Suffix for the jar containing stubs (e.
-                                  g. 'stubs' if the stub jar would
-                                  have a 'stubs' classifier for stubs:
-                                  foobar-stubs ). Defaults to 'stubs'
-                                  (default: stubs)
---maxPort, --maxp &lt;Integer&gt;     Maximum port value to be assigned to
-                                  the WireMock instance. Defaults to
-                                  15000 (default: 15000)
---minPort, --minp &lt;Integer&gt;     Minimum port value to be assigned to
-                                  the WireMock instance. Defaults to
-                                  10000 (default: 10000)
--p, --password                  Password to user when connecting to
-                                  repository
---phost, --proxyHost            Proxy host to use for repository
-                                  requests
---pport, --proxyPort [Integer]  Proxy port to use for repository
-                                  requests
--r, --root                      Location of a Jar containing server
-                                  where you keep your stubs (e.g. http:
-                                  //nexus.
-                                  net/content/repositories/repository)
--s, --stubs                     Comma separated list of Ivy
-                                  representation of jars with stubs.
-                                  Eg. groupid:artifactid1,groupid2:
-                                  artifactid2:classifier
---sm, --stubsMode               Stubs mode to be used. Acceptable values
-                                  [CLASSPATH, LOCAL, REMOTE]
--u, --username                  Username to user when connecting to
-                                  repository</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_http_stubs"><a class="link" href="#_http_stubs">HTTP Stubs</a></h5>
-<div class="paragraph">
-<p>Stubs are defined in JSON documents, whose syntax is defined in <a href="http://wiremock.org/stubbing.html">WireMock documentation</a></p>
-</div>
-<div class="paragraph">
-<p>Example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-javascript hljs" data-lang="javascript">{
-    "request": {
-        "method": "GET",
-        "url": "/ping"
-    },
-    "response": {
-        "status": 200,
-        "body": "pong",
-        "headers": {
-            "Content-Type": "text/plain"
-        }
-    }
-}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_viewing_registered_mappings"><a class="link" href="#_viewing_registered_mappings">Viewing registered mappings</a></h5>
-<div class="paragraph">
-<p>Every stubbed collaborator exposes list of defined mappings under <code>__/admin/</code> endpoint.</p>
-</div>
-<div class="paragraph">
-<p>You can also use the <code>mappingsOutputFolder</code> property to dump the mappings to files.
- For annotation based approach it would look like this</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(ids="a.b.c:loanIssuance,a.b.c:fraudDetectionServer",
-mappingsOutputFolder = "target/outputmappings/")</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>and for the JUnit approach like this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ClassRule @Shared StubRunnerRule rule = new StubRunnerRule()
-			.repoRoot("https://some_url")
-			.downloadStub("a.b.c", "loanIssuance")
-			.downloadStub("a.b.c:fraudDetectionServer")
-			.withMappingsOutputFolder("target/outputmappings")</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Then if you check out the folder <code>target/outputmappings</code> you would see the following structure</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">.
-├── fraudDetectionServer_13705
-└── loanIssuance_12255</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>That means that there were two stubs registered. <code>fraudDetectionServer</code> was registered at port <code>13705</code>
-and <code>loanIssuance</code> at port <code>12255</code>. If we take a look at one of the files we would see (for WireMock)
-mappings available for the given server:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">[{
-  "id" : "f9152eb9-bf77-4c38-8289-90be7d10d0d7",
-  "request" : {
-    "url" : "/name",
-    "method" : "GET"
-  },
-  "response" : {
-    "status" : 200,
-    "body" : "fraudDetectionServer"
-  },
-  "uuid" : "f9152eb9-bf77-4c38-8289-90be7d10d0d7"
-},
-...
-]</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_messaging_stubs"><a class="link" href="#_messaging_stubs">Messaging Stubs</a></h5>
-<div class="paragraph">
-<p>Depending on the provided Stub Runner dependency and the DSL the messaging routes are automatically set up.</p>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_stub_runner_junit_rule_and_stub_runner_junit5_extension"><a class="link" href="#_stub_runner_junit_rule_and_stub_runner_junit5_extension">6.4. Stub Runner JUnit Rule and Stub Runner JUnit5 Extension</a></h3>
-<div class="paragraph">
-<p>Stub Runner comes with a JUnit rule thanks to which you can very easily download and run stubs for given group and artifact id:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ClassRule
-public static StubRunnerRule rule = new StubRunnerRule().repoRoot(repoRoot())
-		.stubsMode(StubRunnerProperties.StubsMode.REMOTE)
-		.downloadStub("org.springframework.cloud.contract.verifier.stubs",
-				"loanIssuance")
-		.downloadStub(
-				"org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer");
-
-@BeforeClass
-@AfterClass
-public static void setupProps() {
-	System.clearProperty("stubrunner.repository.root");
-	System.clearProperty("stubrunner.classifier");
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>There&#8217;s also a <code>StubRunnerExtension</code> available for JUnit 5. <code>StubRunnerRule</code> and <code>StubRunnerExtension</code> work in a very
-similar fashion. After the rule/ extension is executed, Stub Runner connects to your Maven repository and for the given list of dependencies tries to:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>download them</p>
-</li>
-<li>
-<p>cache them locally</p>
-</li>
-<li>
-<p>unzip them to a temporary folder</p>
-</li>
-<li>
-<p>start a WireMock server for each Maven dependency on a random port from the provided range of ports / provided port</p>
-</li>
-<li>
-<p>feed the WireMock server with all JSON files that are valid WireMock definitions</p>
-</li>
-<li>
-<p>can also send messages (remember to pass an implementation of <code>MessageVerifier</code> interface)</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Stub Runner uses <a href="https://wiki.eclipse.org/Aether">Eclipse Aether</a> mechanism to download the Maven dependencies.
-Check their <a href="https://wiki.eclipse.org/Aether">docs</a> for more information.</p>
-</div>
-<div class="paragraph">
-<p>Since the <code>StubRunnerRule</code> and <code>StubRunnerExtension</code> implement the <code>StubFinder</code> they allow you to find the started stubs:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package org.springframework.cloud.contract.stubrunner;
-
-import java.net.URL;
-import java.util.Collection;
-import java.util.Map;
-
-import org.springframework.cloud.contract.spec.Contract;
-
-/**
- * Contract for finding registered stubs.
- *
- * @author Marcin Grzejszczak
- */
-public interface StubFinder extends StubTrigger {
-
-	/**
-	 * For the given groupId and artifactId tries to find the matching URL of the running
-	 * stub.
-	 * @param groupId - might be null. In that case a search only via artifactId takes
-	 * place
-	 * @param artifactId - artifact id of the stub
-	 * @return URL of a running stub or throws exception if not found
-	 * @throws StubNotFoundException in case of not finding a stub
-	 */
-	URL findStubUrl(String groupId, String artifactId) throws StubNotFoundException;
-
-	/**
-	 * For the given Ivy notation {@code [groupId]:artifactId:[version]:[classifier]}
-	 * tries to find the matching URL of the running stub. You can also pass only
-	 * {@code artifactId}.
-	 * @param ivyNotation - Ivy representation of the Maven artifact
-	 * @return URL of a running stub or throws exception if not found
-	 * @throws StubNotFoundException in case of not finding a stub
-	 */
-	URL findStubUrl(String ivyNotation) throws StubNotFoundException;
-
-	/**
-	 * @return all running stubs
-	 */
-	RunningStubs findAllRunningStubs();
-
-	/**
-	 * @return the list of Contracts
-	 */
-	Map&lt;StubConfiguration, Collection&lt;Contract&gt;&gt; getContracts();
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Example of usage in Spock tests:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@ClassRule
-@Shared
-StubRunnerRule rule = new StubRunnerRule()
-		.stubsMode(StubRunnerProperties.StubsMode.REMOTE)
-		.repoRoot(StubRunnerRuleSpec.getResource("/m2repo/repository").toURI().toString())
-		.downloadStub("org.springframework.cloud.contract.verifier.stubs", "loanIssuance")
-		.downloadStub("org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer")
-		.withMappingsOutputFolder("target/outputmappingsforrule")
-
-
-def 'should start WireMock servers'() {
-	expect: 'WireMocks are running'
-		rule.findStubUrl('org.springframework.cloud.contract.verifier.stubs', 'loanIssuance') != null
-		rule.findStubUrl('loanIssuance') != null
-		rule.findStubUrl('loanIssuance') == rule.findStubUrl('org.springframework.cloud.contract.verifier.stubs', 'loanIssuance')
-		rule.findStubUrl('org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer') != null
-	and:
-		rule.findAllRunningStubs().isPresent('loanIssuance')
-		rule.findAllRunningStubs().isPresent('org.springframework.cloud.contract.verifier.stubs', 'fraudDetectionServer')
-		rule.findAllRunningStubs().isPresent('org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer')
-	and: 'Stubs were registered'
-		"${rule.findStubUrl('loanIssuance').toString()}/name".toURL().text == 'loanIssuance'
-		"${rule.findStubUrl('fraudDetectionServer').toString()}/name".toURL().text == 'fraudDetectionServer'
-}
-
-def 'should output mappings to output folder'() {
-	when:
-		def url = rule.findStubUrl('fraudDetectionServer')
-	then:
-		new File("target/outputmappingsforrule", "fraudDetectionServer_${url.port}").exists()
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Example of usage in JUnit tests:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">	@Test
-	public void should_start_wiremock_servers() throws Exception {
-		// expect: 'WireMocks are running'
-		then(rule.findStubUrl("org.springframework.cloud.contract.verifier.stubs",
-				"loanIssuance")).isNotNull();
-		then(rule.findStubUrl("loanIssuance")).isNotNull();
-		then(rule.findStubUrl("loanIssuance")).isEqualTo(rule.findStubUrl(
-				"org.springframework.cloud.contract.verifier.stubs", "loanIssuance"));
-		then(rule.findStubUrl(
-				"org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer"))
-						.isNotNull();
-		// and:
-		then(rule.findAllRunningStubs().isPresent("loanIssuance")).isTrue();
-		then(rule.findAllRunningStubs().isPresent(
-				"org.springframework.cloud.contract.verifier.stubs",
-				"fraudDetectionServer")).isTrue();
-		then(rule.findAllRunningStubs().isPresent(
-				"org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer"))
-						.isTrue();
-		// and: 'Stubs were registered'
-		then(httpGet(rule.findStubUrl("loanIssuance").toString() + "/name"))
-				.isEqualTo("loanIssuance");
-		then(httpGet(rule.findStubUrl("fraudDetectionServer").toString() + "/name"))
-				.isEqualTo("fraudDetectionServer");
-	}
-
-	private String httpGet(String url) throws Exception {
-		try (InputStream stream = URI.create(url).toURL().openStream()) {
-			return StreamUtils.copyToString(stream, Charset.forName("UTF-8"));
-		}
-	}
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>JUnit 5 Extension example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">// Visible for Junit
-@RegisterExtension
-static StubRunnerExtension stubRunnerExtension = new StubRunnerExtension()
-		.repoRoot(repoRoot()).stubsMode(StubRunnerProperties.StubsMode.REMOTE)
-		.downloadStub("org.springframework.cloud.contract.verifier.stubs",
-				"loanIssuance")
-		.downloadStub(
-				"org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer")
-		.withMappingsOutputFolder("target/outputmappingsforrule");
-
-@BeforeAll
-@AfterAll
-static void setupProps() {
-	System.clearProperty("stubrunner.repository.root");
-	System.clearProperty("stubrunner.classifier");
-}
-
-private static String repoRoot() {
-	try {
-		return StubRunnerRuleJUnitTest.class.getResource("/m2repo/repository/")
-				.toURI().toString();
-	}
-	catch (Exception e) {
-		return "";
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Check the <strong>Common properties for JUnit and Spring</strong> for more information on how to apply global configuration of Stub Runner.</p>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-To use the JUnit rule or JUnit 5 extension together with messaging, you have to provide an implementation of the
-<code>MessageVerifier</code> interface to the rule builder (e.g. <code>rule.messageVerifier(new MyMessageVerifier())</code>).
-If you don&#8217;t do this, then whenever you try to send a message an exception will be thrown.
-</td>
-</tr>
-</table>
-</div>
-<div class="sect3">
-<h4 id="_maven_settings"><a class="link" href="#_maven_settings">6.4.1. Maven settings</a></h4>
-<div class="paragraph">
-<p>The stub downloader honors Maven settings for a different local repository folder.
-Authentication details for repositories and profiles are currently not taken into account, so you need to specify it using the properties mentioned above.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_providing_fixed_ports"><a class="link" href="#_providing_fixed_ports">6.4.2. Providing fixed ports</a></h4>
-<div class="paragraph">
-<p>You can also run your stubs on fixed ports. You can do it in two different ways. One is to pass it in the properties, and the other via fluent API of
-JUnit rule.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_fluent_api"><a class="link" href="#_fluent_api">6.4.3. Fluent API</a></h4>
-<div class="paragraph">
-<p>When using the <code>StubRunnerRule</code> or <code>StubRunnerExtension</code> you can add a stub to download and then pass the port for the last downloaded stub.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ClassRule
-public static StubRunnerRule rule = new StubRunnerRule().repoRoot(repoRoot())
-		.stubsMode(StubRunnerProperties.StubsMode.REMOTE)
-		.downloadStub("org.springframework.cloud.contract.verifier.stubs",
-				"loanIssuance")
-		.withPort(12345).downloadStub(
-				"org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer:12346");
-
-@BeforeClass
-@AfterClass
-public static void setupProps() {
-	System.clearProperty("stubrunner.repository.root");
-	System.clearProperty("stubrunner.classifier");
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You can see that for this example the following test is valid:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">then(rule.findStubUrl("loanIssuance"))
-		.isEqualTo(URI.create("http://localhost:12345").toURL());
-then(rule.findStubUrl("fraudDetectionServer"))
-		.isEqualTo(URI.create("http://localhost:12346").toURL());</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_stub_runner_with_spring"><a class="link" href="#_stub_runner_with_spring">6.4.4. Stub Runner with Spring</a></h4>
-<div class="paragraph">
-<p>Sets up Spring configuration of the Stub Runner project.</p>
-</div>
-<div class="paragraph">
-<p>By providing a list of stubs inside your configuration file the Stub Runner automatically downloads
-and registers in WireMock the selected stubs.</p>
-</div>
-<div class="paragraph">
-<p>If you want to find the URL of your stubbed dependency you can autowire the <code>StubFinder</code> interface and use
-its methods as presented below:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@ContextConfiguration(classes = Config, loader = SpringBootContextLoader)
-@SpringBootTest(properties = [" stubrunner.cloud.enabled=false",
-		'foo=${stubrunner.runningstubs.fraudDetectionServer.port}',
-		'fooWithGroup=${stubrunner.runningstubs.org.springframework.cloud.contract.verifier.stubs.fraudDetectionServer.port}'])
-@AutoConfigureStubRunner(mappingsOutputFolder = "target/outputmappings/",
-		httpServerStubConfigurer = HttpsForFraudDetection)
-@ActiveProfiles("test")
-class StubRunnerConfigurationSpec extends Specification {
-
-	@Autowired
-	StubFinder stubFinder
-	@Autowired
-	Environment environment
-	@StubRunnerPort("fraudDetectionServer")
-	int fraudDetectionServerPort
-	@StubRunnerPort("org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer")
-	int fraudDetectionServerPortWithGroupId
-	@Value('${foo}')
-	Integer foo
-
-	@BeforeClass
-	@AfterClass
-	void setupProps() {
-		System.clearProperty("stubrunner.repository.root")
-		System.clearProperty("stubrunner.classifier")
-	}
-
-	def 'should start WireMock servers'() {
-		expect: 'WireMocks are running'
-			stubFinder.findStubUrl('org.springframework.cloud.contract.verifier.stubs', 'loanIssuance') != null
-			stubFinder.findStubUrl('loanIssuance') != null
-			stubFinder.findStubUrl('loanIssuance') == stubFinder.findStubUrl('org.springframework.cloud.contract.verifier.stubs', 'loanIssuance')
-			stubFinder.findStubUrl('loanIssuance') == stubFinder.findStubUrl('org.springframework.cloud.contract.verifier.stubs:loanIssuance')
-			stubFinder.findStubUrl('org.springframework.cloud.contract.verifier.stubs:loanIssuance:0.0.1-SNAPSHOT') == stubFinder.findStubUrl('org.springframework.cloud.contract.verifier.stubs:loanIssuance:0.0.1-SNAPSHOT:stubs')
-			stubFinder.findStubUrl('org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer') != null
-		and:
-			stubFinder.findAllRunningStubs().isPresent('loanIssuance')
-			stubFinder.findAllRunningStubs().isPresent('org.springframework.cloud.contract.verifier.stubs', 'fraudDetectionServer')
-			stubFinder.findAllRunningStubs().isPresent('org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer')
-		and: 'Stubs were registered'
-			"${stubFinder.findStubUrl('loanIssuance').toString()}/name".toURL().text == 'loanIssuance'
-			"${stubFinder.findStubUrl('fraudDetectionServer').toString()}/name".toURL().text == 'fraudDetectionServer'
-		and: 'Fraud Detection is an HTTPS endpoint'
-			stubFinder.findStubUrl('fraudDetectionServer').toString().startsWith("https")
-	}
-
-	def 'should throw an exception when stub is not found'() {
-		when:
-			stubFinder.findStubUrl('nonExistingService')
-		then:
-			thrown(StubNotFoundException)
-		when:
-			stubFinder.findStubUrl('nonExistingGroupId', 'nonExistingArtifactId')
-		then:
-			thrown(StubNotFoundException)
-	}
-
-	def 'should register started servers as environment variables'() {
-		expect:
-			environment.getProperty("stubrunner.runningstubs.loanIssuance.port") != null
-			stubFinder.findAllRunningStubs().getPort("loanIssuance") == (environment.getProperty("stubrunner.runningstubs.loanIssuance.port") as Integer)
-		and:
-			environment.getProperty("stubrunner.runningstubs.fraudDetectionServer.port") != null
-			stubFinder.findAllRunningStubs().getPort("fraudDetectionServer") == (environment.getProperty("stubrunner.runningstubs.fraudDetectionServer.port") as Integer)
-		and:
-			environment.getProperty("stubrunner.runningstubs.fraudDetectionServer.port") != null
-			stubFinder.findAllRunningStubs().getPort("fraudDetectionServer") == (environment.getProperty("stubrunner.runningstubs.org.springframework.cloud.contract.verifier.stubs.fraudDetectionServer.port") as Integer)
-	}
-
-	def 'should be able to interpolate a running stub in the passed test property'() {
-		given:
-			int fraudPort = stubFinder.findAllRunningStubs().getPort("fraudDetectionServer")
-		expect:
-			fraudPort &gt; 0
-			environment.getProperty("foo", Integer) == fraudPort
-			environment.getProperty("fooWithGroup", Integer) == fraudPort
-			foo == fraudPort
-	}
-
-	@Issue("#573")
-	def 'should be able to retrieve the port of a running stub via an annotation'() {
-		given:
-			int fraudPort = stubFinder.findAllRunningStubs().getPort("fraudDetectionServer")
-		expect:
-			fraudPort &gt; 0
-			fraudDetectionServerPort == fraudPort
-			fraudDetectionServerPortWithGroupId == fraudPort
-	}
-
-	def 'should dump all mappings to a file'() {
-		when:
-			def url = stubFinder.findStubUrl("fraudDetectionServer")
-		then:
-			new File("target/outputmappings/", "fraudDetectionServer_${url.port}").exists()
-	}
-
-	@Configuration
-	@EnableAutoConfiguration
-	static class Config {}
-
-	@CompileStatic
-	static class HttpsForFraudDetection extends WireMockHttpServerStubConfigurer {
-
-		private static final Log log = LogFactory.getLog(HttpsForFraudDetection)
-
-		@Override
-		WireMockConfiguration configure(WireMockConfiguration httpStubConfiguration, HttpServerStubConfiguration httpServerStubConfiguration) {
-			if (httpServerStubConfiguration.stubConfiguration.artifactId == "fraudDetectionServer") {
-				int httpsPort = SocketUtils.findAvailableTcpPort()
-				log.info("Will set HTTPs port [" + httpsPort + "] for fraud detection server")
-				return httpStubConfiguration
-						.httpsPort(httpsPort)
-			}
-			return httpStubConfiguration
-		}
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>for the following configuration file:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">stubrunner:
-  repositoryRoot: classpath:m2repo/repository/
-  ids:
-    - org.springframework.cloud.contract.verifier.stubs:loanIssuance
-    - org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer
-    - org.springframework.cloud.contract.verifier.stubs:bootService
-  stubs-mode: remote</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Instead of using the properties you can also use the properties inside the <code>@AutoConfigureStubRunner</code>.
-Below you can find an example of achieving the same result by setting values on the annotation.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@AutoConfigureStubRunner(
-		ids = ["org.springframework.cloud.contract.verifier.stubs:loanIssuance",
-				"org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer",
-				"org.springframework.cloud.contract.verifier.stubs:bootService"],
-		stubsMode = StubRunnerProperties.StubsMode.REMOTE,
-		repositoryRoot = "classpath:m2repo/repository/")</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Stub Runner Spring registers environment variables in the following manner
-for every registered WireMock server. Example for Stub Runner ids
- <code>com.example:foo</code>, <code>com.example:bar</code>.</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>stubrunner.runningstubs.foo.port</code></p>
-</li>
-<li>
-<p><code>stubrunner.runningstubs.com.example.foo.port</code></p>
-</li>
-<li>
-<p><code>stubrunner.runningstubs.bar.port</code></p>
-</li>
-<li>
-<p><code>stubrunner.runningstubs.com.example.bar.port</code></p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Which you can reference in your code.</p>
-</div>
-<div class="paragraph">
-<p>You can also use the <code>@StubRunnerPort</code> annotation to inject the port of a running stub.
-Value of the annotation can be the <code>groupid:artifactid</code> or just the <code>artifactid</code>. Example for Stub Runner ids
-<code>com.example:foo</code>, <code>com.example:bar</code>.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@StubRunnerPort("foo")
-int fooPort;
-@StubRunnerPort("com.example:bar")
-int barPort;</code></pre>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_stub_runner_spring_cloud"><a class="link" href="#_stub_runner_spring_cloud">6.5. Stub Runner Spring Cloud</a></h3>
-<div class="paragraph">
-<p>Stub Runner can integrate with Spring Cloud.</p>
-</div>
-<div class="paragraph">
-<p>For real life examples you can check the</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x/producer">producer app sample</a></p>
-</li>
-<li>
-<p><a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x/consumer_with_discovery">consumer app sample</a></p>
-</li>
-</ul>
-</div>
-<div class="sect3">
-<h4 id="_stubbing_service_discovery"><a class="link" href="#_stubbing_service_discovery">6.5.1. Stubbing Service Discovery</a></h4>
-<div class="paragraph">
-<p>The most important feature of <code>Stub Runner Spring Cloud</code> is the fact that it&#8217;s stubbing</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>DiscoveryClient</code></p>
-</li>
-<li>
-<p><code>Ribbon</code> <code>ServerList</code></p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>that means that regardless of the fact whether you&#8217;re using Zookeeper, Consul, Eureka or anything else, you don&#8217;t need that in your tests.
-We&#8217;re starting WireMock instances of your dependencies and we&#8217;re telling your application whenever you&#8217;re using <code>Feign</code>, load balanced <code>RestTemplate</code>
-or <code>DiscoveryClient</code> directly, to call those stubbed servers instead of calling the real Service Discovery tool.</p>
-</div>
-<div class="paragraph">
-<p>For example this test will pass</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">def 'should make service discovery work'() {
-	expect: 'WireMocks are running'
-		"${stubFinder.findStubUrl('loanIssuance').toString()}/name".toURL().text == 'loanIssuance'
-		"${stubFinder.findStubUrl('fraudDetectionServer').toString()}/name".toURL().text == 'fraudDetectionServer'
-	and: 'Stubs can be reached via load service discovery'
-		restTemplate.getForObject('http://loanIssuance/name', String) == 'loanIssuance'
-		restTemplate.getForObject('http://someNameThatShouldMapFraudDetectionServer/name', String) == 'fraudDetectionServer'
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>for the following configuration file</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">stubrunner:
-  idsToServiceIds:
-    ivyNotation: someValueInsideYourCode
-    fraudDetectionServer: someNameThatShouldMapFraudDetectionServer</code></pre>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_test_profiles_and_service_discovery"><a class="link" href="#_test_profiles_and_service_discovery">Test profiles and service discovery</a></h5>
-<div class="paragraph">
-<p>In your integration tests you typically don&#8217;t want to call neither a discovery service (e.g. Eureka)
-or Config Server. That&#8217;s why you create an additional test configuration in which you want to disable
-these features.</p>
-</div>
-<div class="paragraph">
-<p>Due to certain limitations of <a href="https://github.com/spring-cloud/spring-cloud-commons/issues/156"><code>spring-cloud-commons</code></a> to achieve this you have disable these properties
-via a static block like presented below (example for Eureka)</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">    //Hack to work around https://github.com/spring-cloud/spring-cloud-commons/issues/156
-    static {
-        System.setProperty("eureka.client.enabled", "false");
-        System.setProperty("spring.cloud.config.failFast", "false");
-    }</code></pre>
-</div>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_additional_configuration"><a class="link" href="#_additional_configuration">6.5.2. Additional Configuration</a></h4>
-<div class="paragraph">
-<p>You can match the artifactId of the stub with the name of your app by using the <code>stubrunner.idsToServiceIds:</code> map.
-You can disable Stub Runner Ribbon support by providing: <code>stubrunner.cloud.ribbon.enabled</code> equal to <code>false</code>
-You can disable Stub Runner support by providing: <code>stubrunner.cloud.enabled</code> equal to <code>false</code></p>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-By default all service discovery will be stubbed. That means that regardless of the fact if you have
-an existing <code>DiscoveryClient</code> its results will be ignored. However, if you want to reuse it, just set
- <code>stubrunner.cloud.delegate.enabled</code> to <code>true</code> and then your existing <code>DiscoveryClient</code> results will be
- merged with the stubbed ones.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>The default Maven configuration used by Stub Runner can be tweaked either
-via the following system properties or environment variables</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>maven.repo.local</code> - path to the custom maven local repository location</p>
-</li>
-<li>
-<p><code>org.apache.maven.user-settings</code> - path to custom maven user settings location</p>
-</li>
-<li>
-<p><code>org.apache.maven.global-settings</code> - path to maven global settings location</p>
-</li>
-</ul>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_stub_runner_boot_application"><a class="link" href="#_stub_runner_boot_application">6.6. Stub Runner Boot Application</a></h3>
-<div class="paragraph">
-<p>Spring Cloud Contract Stub Runner Boot is a Spring Boot application that exposes REST endpoints to
-trigger the messaging labels and to access started WireMock servers.</p>
-</div>
-<div class="paragraph">
-<p>One of the use-cases is to run some smoke (end to end) tests on a deployed application.
-You can check out the <a href="https://github.com/spring-cloud/spring-cloud-pipelines">Spring Cloud Pipelines</a>
-project for more information.</p>
-</div>
-<div class="sect3">
-<h4 id="_how_to_use_it"><a class="link" href="#_how_to_use_it">6.6.1. How to use it?</a></h4>
-<div class="sect4">
-<h5 id="_stub_runner_server"><a class="link" href="#_stub_runner_server">Stub Runner Server</a></h5>
-<div class="paragraph">
-<p>Just add the</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">compile "org.springframework.cloud:spring-cloud-starter-stub-runner"</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Annotate a class with <code>@EnableStubRunnerServer</code>, build a fat-jar and you&#8217;re ready to go!</p>
-</div>
-<div class="paragraph">
-<p>For the properties check the <strong>Stub Runner Spring</strong> section.</p>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_stub_runner_server_fat_jar"><a class="link" href="#_stub_runner_server_fat_jar">Stub Runner Server Fat Jar</a></h5>
-<div class="paragraph">
-<p>You can download a standalone JAR from Maven (e.g. for version 2.0.1.RELEASE), as follows:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ wget -O stub-runner.jar 'https://search.maven.org/remotecontent?filepath=org/springframework/cloud/spring-cloud-contract-stub-runner-boot/2.0.1.RELEASE/spring-cloud-contract-stub-runner-boot-2.0.1.RELEASE.jar'
-$ java -jar stub-runner.jar --stubrunner.ids=... --stubrunner.repositoryRoot=...</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_spring_cloud_cli"><a class="link" href="#_spring_cloud_cli">Spring Cloud CLI</a></h5>
-<div class="paragraph">
-<p>Starting from <code>1.4.0.RELEASE</code> version of the <a href="https://cloud.spring.io/spring-cloud-cli">Spring Cloud CLI</a>
-project you can start Stub Runner Boot by executing <code>spring cloud stubrunner</code>.</p>
-</div>
-<div class="paragraph">
-<p>In order to pass the configuration just create a <code>stubrunner.yml</code> file in the current working directory
-or a subdirectory called <code>config</code> or in <code>~/.spring-cloud</code>. The file could look like this
-(example for running stubs installed locally)</p>
-</div>
-<div class="listingblock">
-<div class="title">stubrunner.yml</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">stubrunner:
-  stubsMode: LOCAL
-  ids:
-    - com.example:beer-api-producer:+:9876</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>and then just call <code>spring cloud stubrunner</code> from your terminal window to start
-the Stub Runner server. It will be available at port <code>8750</code>.</p>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_endpoints"><a class="link" href="#_endpoints">6.6.2. Endpoints</a></h4>
-<div class="sect4">
-<h5 id="_http"><a class="link" href="#_http">HTTP</a></h5>
-<div class="ulist">
-<ul>
-<li>
-<p>GET <code>/stubs</code> - returns a list of all running stubs in <code>ivy:integer</code> notation</p>
-</li>
-<li>
-<p>GET <code>/stubs/{ivy}</code> - returns a port for the given <code>ivy</code> notation (when calling the endpoint <code>ivy</code> can also be <code>artifactId</code> only)</p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_messaging"><a class="link" href="#_messaging">Messaging</a></h5>
-<div class="paragraph">
-<p>For Messaging</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>GET <code>/triggers</code> - returns a list of all running labels in <code>ivy : [ label1, label2 &#8230;&#8203;]</code> notation</p>
-</li>
-<li>
-<p>POST <code>/triggers/{label}</code> - executes a trigger with <code>label</code></p>
-</li>
-<li>
-<p>POST <code>/triggers/{ivy}/{label}</code> - executes a trigger with <code>label</code> for the given <code>ivy</code> notation (when calling the endpoint <code>ivy</code> can also be <code>artifactId</code> only)</p>
-</li>
-</ul>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_example"><a class="link" href="#_example">6.6.3. Example</a></h4>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@ContextConfiguration(classes = StubRunnerBoot, loader = SpringBootContextLoader)
-@SpringBootTest(properties = "spring.cloud.zookeeper.enabled=false")
-@ActiveProfiles("test")
-class StubRunnerBootSpec extends Specification {
-
-	@Autowired
-	StubRunning stubRunning
-
-	def setup() {
-		RestAssuredMockMvc.standaloneSetup(new HttpStubsController(stubRunning),
-				new TriggerController(stubRunning))
-	}
-
-	def 'should return a list of running stub servers in "full ivy:port" notation'() {
-		when:
-			String response = RestAssuredMockMvc.get('/stubs').body.asString()
-		then:
-			def root = new JsonSlurper().parseText(response)
-			root.'org.springframework.cloud.contract.verifier.stubs:bootService:0.0.1-SNAPSHOT:stubs' instanceof Integer
-	}
-
-	def 'should return a port on which a [#stubId] stub is running'() {
-		when:
-			def response = RestAssuredMockMvc.get("/stubs/${stubId}")
-		then:
-			response.statusCode == 200
-			Integer.valueOf(response.body.asString()) &gt; 0
-		where:
-			stubId &lt;&lt; ['org.springframework.cloud.contract.verifier.stubs:bootService:+:stubs',
-					   'org.springframework.cloud.contract.verifier.stubs:bootService:0.0.1-SNAPSHOT:stubs',
-					   'org.springframework.cloud.contract.verifier.stubs:bootService:+',
-					   'org.springframework.cloud.contract.verifier.stubs:bootService',
-					   'bootService']
-	}
-
-	def 'should return 404 when missing stub was called'() {
-		when:
-			def response = RestAssuredMockMvc.get("/stubs/a:b:c:d")
-		then:
-			response.statusCode == 404
-	}
-
-	def 'should return a list of messaging labels that can be triggered when version and classifier are passed'() {
-		when:
-			String response = RestAssuredMockMvc.get('/triggers').body.asString()
-		then:
-			def root = new JsonSlurper().parseText(response)
-			root.'org.springframework.cloud.contract.verifier.stubs:bootService:0.0.1-SNAPSHOT:stubs'?.containsAll(["delete_book", "return_book_1", "return_book_2"])
-	}
-
-	def 'should trigger a messaging label'() {
-		given:
-			StubRunning stubRunning = Mock()
-			RestAssuredMockMvc.standaloneSetup(new HttpStubsController(stubRunning), new TriggerController(stubRunning))
-		when:
-			def response = RestAssuredMockMvc.post("/triggers/delete_book")
-		then:
-			response.statusCode == 200
-		and:
-			1 * stubRunning.trigger('delete_book')
-	}
-
-	def 'should trigger a messaging label for a stub with [#stubId] ivy notation'() {
-		given:
-			StubRunning stubRunning = Mock()
-			RestAssuredMockMvc.standaloneSetup(new HttpStubsController(stubRunning), new TriggerController(stubRunning))
-		when:
-			def response = RestAssuredMockMvc.post("/triggers/$stubId/delete_book")
-		then:
-			response.statusCode == 200
-		and:
-			1 * stubRunning.trigger(stubId, 'delete_book')
-		where:
-			stubId &lt;&lt; ['org.springframework.cloud.contract.verifier.stubs:bootService:stubs', 'org.springframework.cloud.contract.verifier.stubs:bootService', 'bootService']
-	}
-
-	def 'should throw exception when trigger is missing'() {
-		when:
-			RestAssuredMockMvc.post("/triggers/missing_label")
-		then:
-			Exception e = thrown(Exception)
-			e.message.contains("Exception occurred while trying to return [missing_label] label.")
-			e.message.contains("Available labels are")
-			e.message.contains("org.springframework.cloud.contract.verifier.stubs:loanIssuance:0.0.1-SNAPSHOT:stubs=[]")
-			e.message.contains("org.springframework.cloud.contract.verifier.stubs:bootService:0.0.1-SNAPSHOT:stubs=")
-	}
-
-}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_stub_runner_boot_with_service_discovery"><a class="link" href="#_stub_runner_boot_with_service_discovery">6.6.4. Stub Runner Boot with Service Discovery</a></h4>
-<div class="paragraph">
-<p>One of the possibilities of using Stub Runner Boot is to use it as a feed of stubs for "smoke-tests". What does it mean?
- Let&#8217;s assume that you don&#8217;t want to deploy 50 microservice to a test environment in order
- to check if your application is working fine. You&#8217;ve already executed a suite of tests during the build process
- but you would also like to ensure that the packaging of your application is fine. What you can do
- is to deploy your application to an environment, start it and run a couple of tests on it to see if
- it&#8217;s working fine. We can call those tests smoke-tests since their idea is to check only a handful
- of testing scenarios.</p>
-</div>
-<div class="paragraph">
-<p>The problem with this approach is such that if you&#8217;re doing microservices most likely you&#8217;re
- using a service discovery tool. Stub Runner Boot allows you to solve this issue by starting the
- required stubs and register them in a service discovery tool. Let&#8217;s take a look at an example of
- such a setup with Eureka. Let&#8217;s assume that Eureka was already running.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@SpringBootApplication
-@EnableStubRunnerServer
-@EnableEurekaClient
-@AutoConfigureStubRunner
-public class StubRunnerBootEurekaExample {
-
-	public static void main(String[] args) {
-		SpringApplication.run(StubRunnerBootEurekaExample.class, args);
-	}
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>As you can see we want to start a Stub Runner Boot server <code>@EnableStubRunnerServer</code>, enable Eureka client <code>@EnableEurekaClient</code>
-and we want to have the stub runner feature turned on <code>@AutoConfigureStubRunner</code>.</p>
-</div>
-<div class="paragraph">
-<p>Now let&#8217;s assume that we want to start this application so that the stubs get automatically registered.
- We can do it by running the app <code>java -jar ${SYSTEM_PROPS} stub-runner-boot-eureka-example.jar</code> where
- <code>${SYSTEM_PROPS}</code> would contain the following list of properties</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">* -Dstubrunner.repositoryRoot=https://repo.spring.io/snapshot (1)
-* -Dstubrunner.cloud.stubbed.discovery.enabled=false (2)
-* -Dstubrunner.ids=org.springframework.cloud.contract.verifier.stubs:loanIssuance,org.
-* springframework.cloud.contract.verifier.stubs:fraudDetectionServer,org.springframework.
-* cloud.contract.verifier.stubs:bootService (3)
-* -Dstubrunner.idsToServiceIds.fraudDetectionServer=
-* someNameThatShouldMapFraudDetectionServer (4)
-*
-* (1) - we tell Stub Runner where all the stubs reside (2) - we don't want the default
-* behaviour where the discovery service is stubbed. That's why the stub registration will
-* be picked (3) - we provide a list of stubs to download (4) - we provide a list of</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>That way your deployed application can send requests to started WireMock servers via the service
-discovery. Most likely points 1-3 could be set by default in <code>application.yml</code> cause they are not
-likely to change. That way you can provide only the list of stubs to download whenever you start
-the Stub Runner Boot.</p>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_stubs_per_consumer"><a class="link" href="#_stubs_per_consumer">6.7. Stubs Per Consumer</a></h3>
-<div class="paragraph">
-<p>There are cases in which 2 consumers of the same endpoint want to have 2 different responses.</p>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-This approach also allows you to immediately know which consumer is using which part of your API.
-You can remove part of a response that your API produces and you can see which of your autogenerated tests
-fails. If none fails then you can safely delete that part of the response cause nobody is using it.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>Let&#8217;s look at the following example for contract defined for the producer called <code>producer</code>.
-There are 2 consumers: <code>foo-consumer</code> and <code>bar-consumer</code>.</p>
-</div>
-<div class="paragraph">
-<p><strong>Consumer <code>foo-service</code></strong></p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">request {
-   url '/foo'
-   method GET()
-}
-response {
-    status OK()
-    body(
-       foo: "foo"
-    }
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><strong>Consumer <code>bar-service</code></strong></p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">request {
-   url '/foo'
-   method GET()
-}
-response {
-    status OK()
-    body(
-       bar: "bar"
-    }
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You can&#8217;t produce for the same request 2 different responses. That&#8217;s why you can properly package the
-contracts and then profit from the <code>stubsPerConsumer</code> feature.</p>
-</div>
-<div class="paragraph">
-<p>On the producer side the consumers can have a folder that contains contracts related only to them.
-By setting the <code>stubrunner.stubs-per-consumer</code> flag to <code>true</code> we no longer register all stubs but only those that
-correspond to the consumer application&#8217;s name. In other words we&#8217;ll scan the path of every stub and
-if it contains the subfolder with name of the consumer in the path only then will it get registered.</p>
-</div>
-<div class="paragraph">
-<p>On the <code>foo</code> producer side the contracts would look like this</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">.
-└── contracts
-    ├── bar-consumer
-    │   ├── bookReturnedForBar.groovy
-    │   └── shouldCallBar.groovy
-    └── foo-consumer
-        ├── bookReturnedForFoo.groovy
-        └── shouldCallFoo.groovy</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Being the <code>bar-consumer</code> consumer you can either set the <code>spring.application.name</code> or the <code>stubrunner.consumer-name</code> to <code>bar-consumer</code>
-Or set the test as follows:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@ContextConfiguration(classes = Config, loader = SpringBootContextLoader)
-@SpringBootTest(properties = ["spring.application.name=bar-consumer"])
-@AutoConfigureStubRunner(ids = "org.springframework.cloud.contract.verifier.stubs:producerWithMultipleConsumers",
-		repositoryRoot = "classpath:m2repo/repository/",
-		stubsMode = StubRunnerProperties.StubsMode.REMOTE,
-		stubsPerConsumer = true)
-class StubRunnerStubsPerConsumerSpec extends Specification {
-...
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Then only the stubs registered under a path that contains the <code>bar-consumer</code> in its name (i.e. those from the
-<code>src/test/resources/contracts/bar-consumer/some/contracts/&#8230;&#8203;</code> folder) will be allowed to be referenced.</p>
-</div>
-<div class="paragraph">
-<p>Or set the consumer name explicitly</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@ContextConfiguration(classes = Config, loader = SpringBootContextLoader)
-@SpringBootTest
-@AutoConfigureStubRunner(ids = "org.springframework.cloud.contract.verifier.stubs:producerWithMultipleConsumers",
-		repositoryRoot = "classpath:m2repo/repository/",
-		consumerName = "foo-consumer",
-		stubsMode = StubRunnerProperties.StubsMode.REMOTE,
-		stubsPerConsumer = true)
-class StubRunnerStubsPerConsumerWithConsumerNameSpec extends Specification {
-...
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Then only the stubs registered under a path that contains the <code>foo-consumer</code> in its name (i.e. those from the
-<code>src/test/resources/contracts/foo-consumer/some/contracts/&#8230;&#8203;</code> folder) will be allowed to be referenced.</p>
-</div>
-<div class="paragraph">
-<p>You can check out <a href="https://github.com/spring-cloud/spring-cloud-contract/issues/224">issue 224</a> for more
-information about the reasons behind this change.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_common"><a class="link" href="#_common">6.8. Common</a></h3>
-<div class="paragraph">
-<p>This section briefly describes common properties, including:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="#common-properties-junit-spring">Common Properties for JUnit and Spring</a></p>
-</li>
-<li>
-<p><a href="#stub-runner-stub-ids">Stub Runner Stubs IDs</a></p>
-</li>
-</ul>
-</div>
-<div class="sect3">
-<h4 id="common-properties-junit-spring"><a class="link" href="#common-properties-junit-spring">6.8.1. Common Properties for JUnit and Spring</a></h4>
-<div class="paragraph">
-<p>You can set repetitive properties by using system properties or Spring configuration
-properties. Here are their names with their default values:</p>
-</div>
-<table class="tableblock frame-topbot grid-all stretch">
-<colgroup>
-<col style="width: 33.3333%;">
-<col style="width: 33.3333%;">
-<col style="width: 33.3334%;">
-</colgroup>
-<thead>
-<tr>
-<th class="tableblock halign-left valign-top">Property name</th>
-<th class="tableblock halign-left valign-top">Default value</th>
-<th class="tableblock halign-left valign-top">Description</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.minPort</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">10000</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Minimum value of a port for a started WireMock with stubs.</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.maxPort</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">15000</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Maximum value of a port for a started WireMock with stubs.</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.repositoryRoot</p></td>
-<td class="tableblock halign-left valign-top"></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Maven repo URL. If blank, then call the local maven repo.</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.classifier</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">stubs</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Default classifier for the stub artifacts.</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.stubsMode</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">CLASSPATH</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">The way you want to fetch and register the stubs</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.ids</p></td>
-<td class="tableblock halign-left valign-top"></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Array of Ivy notation stubs to download.</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.username</p></td>
-<td class="tableblock halign-left valign-top"></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Optional username to access the tool that stores the JARs with
-stubs.</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.password</p></td>
-<td class="tableblock halign-left valign-top"></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Optional password to access the tool that stores the JARs with
-stubs.</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.stubsPerConsumer</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">false</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Set to <code>true</code> if you want to use different stubs for
-each consumer instead of registering all stubs for every consumer.</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.consumerName</p></td>
-<td class="tableblock halign-left valign-top"></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">If you want to use a stub for each consumer and want to
-override the consumer name just change this value.</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="sect3">
-<h4 id="stub-runner-stub-ids"><a class="link" href="#stub-runner-stub-ids">6.8.2. Stub Runner Stubs IDs</a></h4>
-<div class="paragraph">
-<p>You can provide the stubs to download via the <code>stubrunner.ids</code> system property. They
-follow this pattern:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">groupId:artifactId:version:classifier:port</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Note that <code>version</code>, <code>classifier</code> and <code>port</code> are optional.</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>If you do not provide the <code>port</code>, a random one will be picked.</p>
-</li>
-<li>
-<p>If you do not provide the <code>classifier</code>, the default is used. (Note that you can
-pass an empty classifier this way: <code>groupId:artifactId:version:</code>).</p>
-</li>
-<li>
-<p>If you do not provide the <code>version</code>, then the <code>+</code> will be passed and the latest one is
-downloaded.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p><code>port</code> means the port of the WireMock server.</p>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-Starting with version 1.0.4, you can provide a range of versions that you
-would like the Stub Runner to take into consideration. You can read more about the
-<a href="https://wiki.eclipse.org/Aether/New_and_Noteworthy#Version_Ranges">Aether versioning
-ranges here</a>.
-</td>
-</tr>
-</table>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="stubrunner-docker"><a class="link" href="#stubrunner-docker">6.9. Stub Runner Docker</a></h3>
-<div class="paragraph">
-<p>We&#8217;re publishing a <code>spring-cloud/spring-cloud-contract-stub-runner</code> Docker image
-that will start the standalone version of Stub Runner.</p>
-</div>
-<div class="paragraph">
-<p>If you want to learn more about the basics of Maven, artifact ids,
-group ids, classifiers and Artifact Managers, just click here <a href="#docker-project">Docker Project</a>.</p>
-</div>
-<div class="sect3">
-<h4 id="_how_to_use_it_2"><a class="link" href="#_how_to_use_it_2">6.9.1. How to use it</a></h4>
-<div class="paragraph">
-<p>Just execute the docker image. You can pass any of the <a href="#common-properties-junit-spring">Common Properties for JUnit and Spring</a>
-as environment variables. The convention is that all the
-letters should be upper case. The camel case notation should
-and the dot (<code>.</code>) should be separated via underscore (<code>_</code>). E.g.
- the <code>stubrunner.repositoryRoot</code> property should be represented
-  as a <code>STUBRUNNER_REPOSITORY_ROOT</code> environment variable.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_example_of_client_side_usage_in_a_non_jvm_project"><a class="link" href="#_example_of_client_side_usage_in_a_non_jvm_project">6.9.2. Example of client side usage in a non JVM project</a></h4>
-<div class="paragraph">
-<p>We&#8217;d like to use the stubs created in this <a href="#docker-server-side">Server side (nodejs)</a> step.
-Let&#8217;s assume that we want to run the stubs on port <code>9876</code>. The NodeJS code
-is available here:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ git clone https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs
-$ cd bookstore</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Let&#8217;s run the Stub Runner Boot application with the stubs.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash"># Provide the Spring Cloud Contract Docker version
-$ SC_CONTRACT_DOCKER_VERSION="..."
-# The IP at which the app is running and Docker container can reach it
-$ APP_IP="192.168.0.100"
-# Spring Cloud Contract Stub Runner properties
-$ STUBRUNNER_PORT="8083"
-# Stub coordinates 'groupId:artifactId:version:classifier:port'
-$ STUBRUNNER_IDS="com.example:bookstore:0.0.1.RELEASE:stubs:9876"
-$ STUBRUNNER_REPOSITORY_ROOT="http://${APP_IP}:8081/artifactory/libs-release-local"
-# Run the docker with Stub Runner Boot
-$ docker run  --rm -e "STUBRUNNER_IDS=${STUBRUNNER_IDS}" -e "STUBRUNNER_REPOSITORY_ROOT=${STUBRUNNER_REPOSITORY_ROOT}" -e "STUBRUNNER_STUBS_MODE=REMOTE" -p "${STUBRUNNER_PORT}:${STUBRUNNER_PORT}" -p "9876:9876" springcloud/spring-cloud-contract-stub-runner:"${SC_CONTRACT_DOCKER_VERSION}"</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>What&#8217;s happening is that</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>a standalone Stub Runner application got started</p>
-</li>
-<li>
-<p>it downloaded the stub with coordinates <code>com.example:bookstore:0.0.1.RELEASE:stubs</code> on port <code>9876</code></p>
-</li>
-<li>
-<p>it got downloaded from Artifactory running at <code><a href="http://192.168.0.100:8081/artifactory/libs-release-local" class="bare">http://192.168.0.100:8081/artifactory/libs-release-local</a></code></p>
-</li>
-<li>
-<p>after a while Stub Runner will be running on port <code>8083</code></p>
-</li>
-<li>
-<p>and the stubs will be running at port <code>9876</code></p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>On the server side we built a stateful stub. Let&#8217;s use curl to assert
-that the stubs are setup properly.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash"># let's execute the first request (no response is returned)
-$ curl -H "Content-Type:application/json" -X POST --data '{ "title" : "Title", "genre" : "Genre", "description" : "Description", "author" : "Author", "publisher" : "Publisher", "pages" : 100, "image_url" : "https://d213dhlpdb53mu.cloudfront.net/assets/pivotal-square-logo-41418bd391196c3022f3cd9f3959b3f6d7764c47873d858583384e759c7db435.svg", "buy_url" : "https://pivotal.io" }' http://localhost:9876/api/books
-# Now time for the second request
-$ curl -X GET http://localhost:9876/api/books
-# You will receive contents of the JSON</code></pre>
-</div>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-If you want use the stubs that you have built locally, on your host,
-then you should pass the environment variable <code>-e STUBRUNNER_STUBS_MODE=LOCAL</code> and mount
-the volume of your local m2 <code>-v "${HOME}/.m2/:/root/.m2:ro"</code>
-</td>
-</tr>
-</table>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="stub-runner-for-messaging"><a class="link" href="#stub-runner-for-messaging">7. Stub Runner for Messaging</a></h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>Stub Runner can run the published stubs in memory. It can integrate with the following
-frameworks:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Spring Integration</p>
-</li>
-<li>
-<p>Spring Cloud Stream</p>
-</li>
-<li>
-<p>Apache Camel</p>
-</li>
-<li>
-<p>Spring AMQP</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>It also provides entry points to integrate with any other solution on the market.</p>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-If you have multiple frameworks on the classpath Stub Runner will need to
-define which one should be used. Let&#8217;s assume that you have both AMQP, Spring Cloud Stream and Spring Integration
-on the classpath. Then you need to set <code>stubrunner.stream.enabled=false</code> and <code>stubrunner.integration.enabled=false</code>.
-That way the only remaining framework is Spring AMQP.
-</td>
-</tr>
-</table>
-</div>
-<div class="sect2">
-<h3 id="_stub_triggering"><a class="link" href="#_stub_triggering">7.1. Stub triggering</a></h3>
-<div class="paragraph">
-<p>To trigger a message, use the <code>StubTrigger</code> interface:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package org.springframework.cloud.contract.stubrunner;
-
-import java.util.Collection;
-import java.util.Map;
-
-/**
- * Contract for triggering stub messages.
- *
- * @author Marcin Grzejszczak
- */
-public interface StubTrigger {
-
-	/**
-	 * Triggers an event by a given label for a given {@code groupid:artifactid} notation.
-	 * You can use only {@code artifactId} too.
-	 *
-	 * Feature related to messaging.
-	 * @param ivyNotation ivy notation of a stub
-	 * @param labelName name of the label to trigger
-	 * @return true - if managed to run a trigger
-	 */
-	boolean trigger(String ivyNotation, String labelName);
-
-	/**
-	 * Triggers an event by a given label.
-	 *
-	 * Feature related to messaging.
-	 * @param labelName name of the label to trigger
-	 * @return true - if managed to run a trigger
-	 */
-	boolean trigger(String labelName);
-
-	/**
-	 * Triggers all possible events.
-	 *
-	 * Feature related to messaging.
-	 * @return true - if managed to run a trigger
-	 */
-	boolean trigger();
-
-	/**
-	 * Feature related to messaging.
-	 * @return a mapping of ivy notation of a dependency to all the labels it has.
-	 */
-	Map&lt;String, Collection&lt;String&gt;&gt; labels();
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>For convenience, the <code>StubFinder</code> interface extends <code>StubTrigger</code>, so you only need one
-or the other in your tests.</p>
-</div>
-<div class="paragraph">
-<p><code>StubTrigger</code> gives you the following options to trigger a message:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="#trigger-label">Trigger by Label</a></p>
-</li>
-<li>
-<p><a href="#trigger-group-artifact-ids">Trigger by Group and Artifact Ids</a></p>
-</li>
-<li>
-<p><a href="#trigger-artifact-ids">Trigger by Artifact Ids</a></p>
-</li>
-<li>
-<p><a href="#trigger-all-messages">Trigger All Messages</a></p>
-</li>
-</ul>
-</div>
-<div class="sect3">
-<h4 id="trigger-label"><a class="link" href="#trigger-label">7.1.1. Trigger by Label</a></h4>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('return_book_1')</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="trigger-group-artifact-ids"><a class="link" href="#trigger-group-artifact-ids">7.1.2. Trigger by Group and Artifact Ids</a></h4>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('org.springframework.cloud.contract.verifier.stubs:streamService', 'return_book_1')</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="trigger-artifact-ids"><a class="link" href="#trigger-artifact-ids">7.1.3. Trigger by Artifact Ids</a></h4>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('streamService', 'return_book_1')</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="trigger-all-messages"><a class="link" href="#trigger-all-messages">7.1.4. Trigger All Messages</a></h4>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger()</code></pre>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_stub_runner_camel"><a class="link" href="#_stub_runner_camel">7.2. Stub Runner Camel</a></h3>
-<div class="paragraph">
-<p>Spring Cloud Contract Verifier Stub Runner&#8217;s messaging module gives you an easy way to integrate with Apache Camel.
-For the provided artifacts it will automatically download the stubs and register the required
-routes.</p>
-</div>
-<div class="sect3">
-<h4 id="_adding_it_to_the_project"><a class="link" href="#_adding_it_to_the_project">7.2.1. Adding it to the project</a></h4>
-<div class="paragraph">
-<p>It&#8217;s enough to have both Apache Camel and Spring Cloud Contract Stub Runner on classpath.
-Remember to annotate your test class with <code>@AutoConfigureStubRunner</code>.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_disabling_the_functionality"><a class="link" href="#_disabling_the_functionality">7.2.2. Disabling the functionality</a></h4>
-<div class="paragraph">
-<p>If you need to disable this functionality just pass <code>stubrunner.camel.enabled=false</code> property.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_examples"><a class="link" href="#_examples">7.2.3. Examples</a></h4>
-<div class="sect4">
-<h5 id="_stubs_structure"><a class="link" href="#_stubs_structure">Stubs structure</a></h5>
-<div class="paragraph">
-<p>Let us assume that we have the following Maven repository with a deployed stubs for the
-<code>camelService</code> application.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── .m2
-    └── repository
-        └── io
-            └── codearte
-                └── accurest
-                    └── stubs
-                        └── camelService
-                            ├── 0.0.1-SNAPSHOT
-                            │   ├── camelService-0.0.1-SNAPSHOT.pom
-                            │   ├── camelService-0.0.1-SNAPSHOT-stubs.jar
-                            │   └── maven-metadata-local.xml
-                            └── maven-metadata-local.xml</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>And the stubs contain the following structure:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── META-INF
-│   └── MANIFEST.MF
-└── repository
-    ├── accurest
-    │   ├── bookDeleted.groovy
-    │   ├── bookReturned1.groovy
-    │   └── bookReturned2.groovy
-    └── mappings</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Let&#8217;s consider the following contracts (let' number it with <strong>1</strong>):</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
-	label 'return_book_1'
-	input {
-		triggeredBy('bookReturnedTriggered()')
-	}
-	outputMessage {
-		sentTo('jms:output')
-		body('''{ "bookName" : "foo" }''')
-		headers {
-			header('BOOK-NAME', 'foo')
-		}
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>and number <strong>2</strong></p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
-	label 'return_book_2'
-	input {
-		messageFrom('jms:input')
-		messageBody([
-				bookName: 'foo'
-		])
-		messageHeaders {
-			header('sample', 'header')
-		}
-	}
-	outputMessage {
-		sentTo('jms:output')
-		body([
-				bookName: 'foo'
-		])
-		headers {
-			header('BOOK-NAME', 'foo')
-		}
-	}
-}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_scenario_1_no_input_message_2"><a class="link" href="#_scenario_1_no_input_message_2">Scenario 1 (no input message)</a></h5>
-<div class="paragraph">
-<p>So as to trigger a message via the <code>return_book_1</code> label we&#8217;ll use the <code>StubTigger</code> interface as follows</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('return_book_1')</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Next we&#8217;ll want to listen to the output of the message sent to <code>jms:output</code></p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Exchange receivedMessage = consumerTemplate.receive('jms:output', 5000)</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>And the received message would pass the following assertions</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
-assertThatBodyContainsBookNameFoo(receivedMessage.in.body)
-receivedMessage.in.headers.get('BOOK-NAME') == 'foo'</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_scenario_2_output_triggered_by_input_2"><a class="link" href="#_scenario_2_output_triggered_by_input_2">Scenario 2 (output triggered by input)</a></h5>
-<div class="paragraph">
-<p>Since the route is set for you it&#8217;s enough to just send a message to the <code>jms:output</code> destination.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">producerTemplate.
-		sendBodyAndHeaders('jms:input', new BookReturned('foo'), [sample: 'header'])</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Next we&#8217;ll want to listen to the output of the message sent to <code>jms:output</code></p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Exchange receivedMessage = consumerTemplate.receive('jms:output', 5000)</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>And the received message would pass the following assertions</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
-assertThatBodyContainsBookNameFoo(receivedMessage.in.body)
-receivedMessage.in.headers.get('BOOK-NAME') == 'foo'</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_scenario_3_input_with_no_output"><a class="link" href="#_scenario_3_input_with_no_output">Scenario 3 (input with no output)</a></h5>
-<div class="paragraph">
-<p>Since the route is set for you it&#8217;s enough to just send a message to the <code>jms:output</code> destination.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">producerTemplate.
-		sendBodyAndHeaders('jms:delete', new BookReturned('foo'), [sample: 'header'])</code></pre>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_stub_runner_integration"><a class="link" href="#_stub_runner_integration">7.3. Stub Runner Integration</a></h3>
-<div class="paragraph">
-<p>Spring Cloud Contract Verifier Stub Runner&#8217;s messaging module gives you an easy way to
-integrate with Spring Integration. For the provided artifacts, it automatically downloads
-the stubs and registers the required routes.</p>
-</div>
-<div class="sect3">
-<h4 id="_adding_the_runner_to_the_project"><a class="link" href="#_adding_the_runner_to_the_project">7.3.1. Adding the Runner to the Project</a></h4>
-<div class="paragraph">
-<p>You can have both Spring Integration and Spring Cloud Contract Stub Runner on the
-classpath. Remember to annotate your test class with <code>@AutoConfigureStubRunner</code>.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_disabling_the_functionality_2"><a class="link" href="#_disabling_the_functionality_2">7.3.2. Disabling the functionality</a></h4>
-<div class="paragraph">
-<p>If you need to disable this functionality, set the
-<code>stubrunner.integration.enabled=false</code> property.</p>
-</div>
-<div class="paragraph">
-<p>Assume that you have the following Maven repository with deployed stubs for the
-<code>integrationService</code> application:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── .m2
-    └── repository
-        └── io
-            └── codearte
-                └── accurest
-                    └── stubs
-                        └── integrationService
-                            ├── 0.0.1-SNAPSHOT
-                            │   ├── integrationService-0.0.1-SNAPSHOT.pom
-                            │   ├── integrationService-0.0.1-SNAPSHOT-stubs.jar
-                            │   └── maven-metadata-local.xml
-                            └── maven-metadata-local.xml</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Further assume the stubs contain the following structure:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── META-INF
-│   └── MANIFEST.MF
-└── repository
-    ├── accurest
-    │   ├── bookDeleted.groovy
-    │   ├── bookReturned1.groovy
-    │   └── bookReturned2.groovy
-    └── mappings</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Consider the following contracts (numbered <strong>1</strong>):</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
-	label 'return_book_1'
-	input {
-		triggeredBy('bookReturnedTriggered()')
-	}
-	outputMessage {
-		sentTo('output')
-		body('''{ "bookName" : "foo" }''')
-		headers {
-			header('BOOK-NAME', 'foo')
-		}
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Now consider <strong>2</strong>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
-	label 'return_book_2'
-	input {
-		messageFrom('input')
-		messageBody([
-				bookName: 'foo'
-		])
-		messageHeaders {
-			header('sample', 'header')
-		}
-	}
-	outputMessage {
-		sentTo('output')
-		body([
-				bookName: 'foo'
-		])
-		headers {
-			header('BOOK-NAME', 'foo')
-		}
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>and the following Spring Integration Route:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;beans:beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-			 xmlns:beans="http://www.springframework.org/schema/beans"
-			 xmlns="http://www.springframework.org/schema/integration"
-			 xsi:schemaLocation="http://www.springframework.org/schema/beans
-			https://www.springframework.org/schema/beans/spring-beans.xsd
-			http://www.springframework.org/schema/integration
-			http://www.springframework.org/schema/integration/spring-integration.xsd"&gt;
-
-
-	&lt;!-- REQUIRED FOR TESTING --&gt;
-	&lt;bridge input-channel="output"
-			output-channel="outputTest"/&gt;
-
-	&lt;channel id="outputTest"&gt;
-		&lt;queue/&gt;
-	&lt;/channel&gt;
-
-&lt;/beans:beans&gt;</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>These examples lend themselves to three scenarios:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="#integration-scenario-1">Scenario 1 (no input message)</a></p>
-</li>
-<li>
-<p><a href="#integration-scenario-2">Scenario 2 (output triggered by input)</a></p>
-</li>
-<li>
-<p><a href="#integration-scenario-3">Scenario 3 (input with no output)</a></p>
-</li>
-</ul>
-</div>
-<div class="sect4">
-<h5 id="integration-scenario-1"><a class="link" href="#integration-scenario-1">Scenario 1 (no input message)</a></h5>
-<div class="paragraph">
-<p>To trigger a message via the <code>return_book_1</code> label, use the <code>StubTigger</code> interface, as
-follows:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('return_book_1')</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>To listen to the output of the message sent to <code>output</code>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Message&lt;?&gt; receivedMessage = messaging.receive('outputTest')</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The received message would pass the following assertions:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
-assertJsons(receivedMessage.payload)
-receivedMessage.headers.get('BOOK-NAME') == 'foo'</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="integration-scenario-2"><a class="link" href="#integration-scenario-2">Scenario 2 (output triggered by input)</a></h5>
-<div class="paragraph">
-<p>Since the route is set for you, you can send a message to the <code>output</code>
-destination:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">messaging.send(new BookReturned('foo'), [sample: 'header'], 'input')</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>To listen to the output of the message sent to <code>output</code>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Message&lt;?&gt; receivedMessage = messaging.receive('outputTest')</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The received message passes the following assertions:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
-assertJsons(receivedMessage.payload)
-receivedMessage.headers.get('BOOK-NAME') == 'foo'</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="integration-scenario-3"><a class="link" href="#integration-scenario-3">Scenario 3 (input with no output)</a></h5>
-<div class="paragraph">
-<p>Since the route is set for you, you can send a message to the <code>input</code> destination:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">messaging.send(new BookReturned('foo'), [sample: 'header'], 'delete')</code></pre>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_stub_runner_stream"><a class="link" href="#_stub_runner_stream">7.4. Stub Runner Stream</a></h3>
-<div class="paragraph">
-<p>Spring Cloud Contract Verifier Stub Runner&#8217;s messaging module gives you an easy way to
-integrate with Spring Stream. For the provided artifacts, it automatically downloads the
-stubs and registers the required routes.</p>
-</div>
-<div class="admonitionblock warning">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-warning" title="Warning"></i>
-</td>
-<td class="content">
-If Stub Runner&#8217;s integration with Stream the <code>messageFrom</code> or <code>sentTo</code> Strings
-are resolved first as a <code>destination</code> of a channel and no such <code>destination</code> exists, the
-destination is resolved as a channel name.
-</td>
-</tr>
-</table>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-If you want to use Spring Cloud Stream remember, to add a dependency on
-<code>org.springframework.cloud:spring-cloud-stream-test-support</code>.
-</td>
-</tr>
-</table>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
-    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-    &lt;artifactId&gt;spring-cloud-stream-test-support&lt;/artifactId&gt;
-    &lt;scope&gt;test&lt;/scope&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">testCompile "org.springframework.cloud:spring-cloud-stream-test-support"</code></pre>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_adding_the_runner_to_the_project_2"><a class="link" href="#_adding_the_runner_to_the_project_2">7.4.1. Adding the Runner to the Project</a></h4>
-<div class="paragraph">
-<p>You can have both Spring Cloud Stream and Spring Cloud Contract Stub Runner on the
-classpath. Remember to annotate your test class with <code>@AutoConfigureStubRunner</code>.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_disabling_the_functionality_3"><a class="link" href="#_disabling_the_functionality_3">7.4.2. Disabling the functionality</a></h4>
-<div class="paragraph">
-<p>If you need to disable this functionality, set the <code>stubrunner.stream.enabled=false</code>
-property.</p>
-</div>
-<div class="paragraph">
-<p>Assume that you have the following Maven repository with a deployed stubs for the
-<code>streamService</code> application:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── .m2
-    └── repository
-        └── io
-            └── codearte
-                └── accurest
-                    └── stubs
-                        └── streamService
-                            ├── 0.0.1-SNAPSHOT
-                            │   ├── streamService-0.0.1-SNAPSHOT.pom
-                            │   ├── streamService-0.0.1-SNAPSHOT-stubs.jar
-                            │   └── maven-metadata-local.xml
-                            └── maven-metadata-local.xml</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Further assume the stubs contain the following structure:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── META-INF
-│   └── MANIFEST.MF
-└── repository
-    ├── accurest
-    │   ├── bookDeleted.groovy
-    │   ├── bookReturned1.groovy
-    │   └── bookReturned2.groovy
-    └── mappings</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Consider the following contracts (numbered <strong>1</strong>):</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
-	label 'return_book_1'
-	input { triggeredBy('bookReturnedTriggered()') }
-	outputMessage {
-		sentTo('returnBook')
-		body('''{ "bookName" : "foo" }''')
-		headers { header('BOOK-NAME', 'foo') }
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Now consider <strong>2</strong>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
-	label 'return_book_2'
-	input {
-		messageFrom('bookStorage')
-		messageBody([
-				bookName: 'foo'
-		])
-		messageHeaders { header('sample', 'header') }
-	}
-	outputMessage {
-		sentTo('returnBook')
-		body([
-				bookName: 'foo'
-		])
-		headers { header('BOOK-NAME', 'foo') }
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Now consider the following Spring configuration:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">stubrunner.repositoryRoot: classpath:m2repo/repository/
-stubrunner.ids: org.springframework.cloud.contract.verifier.stubs:streamService:0.0.1-SNAPSHOT:stubs
-stubrunner.stubs-mode: remote
-spring:
-  cloud:
-    stream:
-      bindings:
-        output:
-          destination: returnBook
-        input:
-          destination: bookStorage
-
-server:
-  port: 0
-
-debug: true</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>These examples lend themselves to three scenarios:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="#stream-scenario-1">Scenario 1 (no input message)</a></p>
-</li>
-<li>
-<p><a href="#stream-scenario-2">Scenario 2 (output triggered by input)</a></p>
-</li>
-<li>
-<p><a href="#stream-scenario-3">Scenario 3 (input with no output)</a></p>
-</li>
-</ul>
-</div>
-<div class="sect4">
-<h5 id="stream-scenario-1"><a class="link" href="#stream-scenario-1">Scenario 1 (no input message)</a></h5>
-<div class="paragraph">
-<p>To trigger a message via the <code>return_book_1</code> label, use the <code>StubTrigger</code> interface as
-follows:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('return_book_1')</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>To listen to the output of the message sent to a channel whose <code>destination</code> is
-<code>returnBook</code>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Message&lt;?&gt; receivedMessage = messaging.receive('returnBook')</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The received message passes the following assertions:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
-assertJsons(receivedMessage.payload)
-receivedMessage.headers.get('BOOK-NAME') == 'foo'</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="stream-scenario-2"><a class="link" href="#stream-scenario-2">Scenario 2 (output triggered by input)</a></h5>
-<div class="paragraph">
-<p>Since the route is set for you, you can send a message to the <code>bookStorage</code>
-<code>destination</code>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">messaging.send(new BookReturned('foo'), [sample: 'header'], 'bookStorage')</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>To listen to the output of the message sent to <code>returnBook</code>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Message&lt;?&gt; receivedMessage = messaging.receive('returnBook')</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The received message passes the following assertions:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
-assertJsons(receivedMessage.payload)
-receivedMessage.headers.get('BOOK-NAME') == 'foo'</code></pre>
-</div>
-</div>
-</div>
-<div class="sect4">
-<h5 id="stream-scenario-3"><a class="link" href="#stream-scenario-3">Scenario 3 (input with no output)</a></h5>
-<div class="paragraph">
-<p>Since the route is set for you, you can send a message to the <code>output</code>
-destination:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">messaging.send(new BookReturned('foo'), [sample: 'header'], 'delete')</code></pre>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_stub_runner_spring_amqp"><a class="link" href="#_stub_runner_spring_amqp">7.5. Stub Runner Spring AMQP</a></h3>
-<div class="paragraph">
-<p>Spring Cloud Contract Verifier Stub Runner&#8217;s messaging module provides an easy way to
-integrate with Spring AMQP&#8217;s Rabbit Template. For the provided artifacts, it
-automatically downloads the stubs and registers the required routes.</p>
-</div>
-<div class="paragraph">
-<p>The integration tries to work standalone (that is, without interaction with a running
-RabbitMQ message broker). It expects a <code>RabbitTemplate</code> on the application context and
-uses it as a spring boot test named <code>@SpyBean</code>. As a result, it can use the mockito spy
-functionality to verify and inspect messages sent by the application.</p>
-</div>
-<div class="paragraph">
-<p>On the message consumer side, the stub runner considers all <code>@RabbitListener</code> annotated
-endpoints and all <code>SimpleMessageListenerContainer</code> objects on the application context.</p>
-</div>
-<div class="paragraph">
-<p>As messages are usually sent to exchanges in AMQP, the message contract contains the
-exchange name as the destination. Message listeners on the other side are bound to
-queues. Bindings connect an exchange to a queue. If message contracts are triggered, the
-Spring AMQP stub runner integration looks for bindings on the application context that
-match this exchange. Then it collects the queues from the Spring exchanges and tries to
-find message listeners bound to these queues. The message is triggered for all matching
-message listeners.</p>
-</div>
-<div class="paragraph">
-<p>If you need to work with routing keys, it&#8217;s enough to pass them via the <code>amqp_receivedRoutingKey</code>
-messaging header.</p>
-</div>
-<div class="sect3">
-<h4 id="_adding_the_runner_to_the_project_3"><a class="link" href="#_adding_the_runner_to_the_project_3">7.5.1. Adding the Runner to the Project</a></h4>
-<div class="paragraph">
-<p>You can have both Spring AMQP and Spring Cloud Contract Stub Runner on the classpath and
-set the property <code>stubrunner.amqp.enabled=true</code>. Remember to annotate your test class
-with <code>@AutoConfigureStubRunner</code>.</p>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-If you already have Stream and Integration on the classpath, you need
-to disable them explicitly by setting the  <code>stubrunner.stream.enabled=false</code> and
-<code>stubrunner.integration.enabled=false</code> properties.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>Assume that you have the following Maven repository with a deployed stubs for the
-<code>spring-cloud-contract-amqp-test</code> application.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── .m2
-    └── repository
-        └── com
-            └── example
-                └── spring-cloud-contract-amqp-test
-                    ├── 0.4.0-SNAPSHOT
-                    │   ├── spring-cloud-contract-amqp-test-0.4.0-SNAPSHOT.pom
-                    │   ├── spring-cloud-contract-amqp-test-0.4.0-SNAPSHOT-stubs.jar
-                    │   └── maven-metadata-local.xml
-                    └── maven-metadata-local.xml</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Further assume that the stubs contain the following structure:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── META-INF
-│   └── MANIFEST.MF
-└── contracts
-    └── shouldProduceValidPersonData.groovy</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Consider the following contract:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
-	// Human readable description
-	description 'Should produce valid person data'
-	// Label by means of which the output message can be triggered
-	label 'contract-test.person.created.event'
-	// input to the contract
-	input {
-		// the contract will be triggered by a method
-		triggeredBy('createPerson()')
-	}
-	// output message of the contract
-	outputMessage {
-		// destination to which the output message will be sent
-		sentTo 'contract-test.exchange'
-		headers {
-			header('contentType': 'application/json')
-			header('__TypeId__': 'org.springframework.cloud.contract.stubrunner.messaging.amqp.Person')
-		}
-		// the body of the output message
-		body([
-				id  : $(consumer(9), producer(regex("[0-9]+"))),
-				name: "me"
-		])
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Now consider the following Spring configuration:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">stubrunner:
-  repositoryRoot: classpath:m2repo/repository/
-  ids: org.springframework.cloud.contract.verifier.stubs.amqp:spring-cloud-contract-amqp-test:0.4.0-SNAPSHOT:stubs
-  stubs-mode: remote
-  amqp:
-    enabled: true
-server:
-  port: 0</code></pre>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_triggering_the_message"><a class="link" href="#_triggering_the_message">Triggering the message</a></h5>
-<div class="paragraph">
-<p>To trigger a message using the contract above, use the <code>StubTrigger</code> interface as
-follows:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubTrigger.trigger("contract-test.person.created.event")</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The message has a destination of <code>contract-test.exchange</code>, so the Spring AMQP stub runner
-integration looks for bindings related to this exchange.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Bean
-public Binding binding() {
-	return BindingBuilder.bind(new Queue("test.queue"))
-			.to(new DirectExchange("contract-test.exchange")).with("#");
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The binding definition binds the queue <code>test.queue</code>. As a result, the following listener
-definition is matched and invoked with the contract message.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Bean
-public SimpleMessageListenerContainer simpleMessageListenerContainer(
-		ConnectionFactory connectionFactory,
-		MessageListenerAdapter listenerAdapter) {
-	SimpleMessageListenerContainer container = new SimpleMessageListenerContainer();
-	container.setConnectionFactory(connectionFactory);
-	container.setQueueNames("test.queue");
-	container.setMessageListener(listenerAdapter);
-
-	return container;
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Also, the following annotated listener matches and is invoked:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RabbitListener(bindings = @QueueBinding(value = @Queue("test.queue"),
-		exchange = @Exchange(value = "contract-test.exchange",
-				ignoreDeclarationExceptions = "true")))
-public void handlePerson(Person person) {
-	this.person = person;
-}</code></pre>
-</div>
-</div>
-<div class="admonitionblock note">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-note" title="Note"></i>
-</td>
-<td class="content">
-The message is directly handed over to the <code>onMessage</code> method of the
-<code>MessageListener</code> associated with the matching <code>SimpleMessageListenerContainer</code>.
-</td>
-</tr>
-</table>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_spring_amqp_test_configuration"><a class="link" href="#_spring_amqp_test_configuration">Spring AMQP Test Configuration</a></h5>
-<div class="paragraph">
-<p>In order to avoid Spring AMQP trying to connect to a running broker during our tests
-configure a mock <code>ConnectionFactory</code>.</p>
-</div>
-<div class="paragraph">
-<p>To disable the mocked ConnectionFactory, set the following property:
-<code>stubrunner.amqp.mockConnection=false</code></p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">stubrunner:
-  amqp:
-    mockConnection: false</code></pre>
-</div>
-</div>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="contract-dsl"><a class="link" href="#contract-dsl">8. Contract DSL</a></h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>Spring Cloud Contract supports out of the box 2 types of DSL. One written in
-<code>Groovy</code> and one written in <code>YAML</code>.</p>
-</div>
-<div class="paragraph">
-<p>If you decide to write the contract in Groovy, do not be alarmed if you have not used Groovy
-before. Knowledge of the language is not really needed, as the Contract DSL uses only a
-tiny subset of it (only literals, method calls and closures). Also, the DSL is statically
-typed, to make it programmer-readable without any knowledge of the DSL itself.</p>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-Remember that, inside the Groovy contract file, you have to provide the fully
-qualified name to the <code>Contract</code> class and <code>make</code> static imports, such as
-<code>org.springframework.cloud.spec.Contract.make { &#8230;&#8203; }</code>. You can also provide an import to
-the <code>Contract</code> class: <code>import org.springframework.cloud.spec.Contract</code> and then call
-<code>Contract.make { &#8230;&#8203; }</code>.
-</td>
-</tr>
-</table>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-Spring Cloud Contract supports defining multiple contracts in a single file.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>The following is a complete example of a Groovy contract definition:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy"></code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following is a complete example of a YAML contract definition:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">description: Some description
-name: some name
-priority: 8
-ignored: true
-request:
-  url: /foo
-  queryParameters:
-    a: b
-    b: c
-  method: PUT
-  headers:
-    foo: bar
-    fooReq: baz
-  body:
-    foo: bar
-  matchers:
-    body:
-      - path: $.foo
-        type: by_regex
-        value: bar
-    headers:
-      - key: foo
-        regex: bar
-response:
-  status: 200
-  headers:
-    foo2: bar
-    foo3: foo33
-    fooRes: baz
-  body:
-    foo2: bar
-    foo3: baz
-    nullValue: null
-  matchers:
-    body:
-      - path: $.foo2
-        type: by_regex
-        value: bar
-      - path: $.foo3
-        type: by_command
-        value: executeMe($it)
-      - path: $.nullValue
-        type: by_null
-        value: null
-    headers:
-      - key: foo2
-        regex: bar
-      - key: foo3
-        command: andMeToo($it)</code></pre>
-</div>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-You can compile contracts to stubs mapping using standalone maven command:
-<code>mvn org.springframework.cloud:spring-cloud-contract-maven-plugin:convert</code>
-</td>
-</tr>
-</table>
-</div>
-<div class="sect2">
-<h3 id="_limitations"><a class="link" href="#_limitations">8.1. Limitations</a></h3>
-<div class="admonitionblock warning">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-warning" title="Warning"></i>
-</td>
-<td class="content">
-Spring Cloud Contract Verifier does not properly support XML. Please use JSON or
-help us implement this feature.
-</td>
-</tr>
-</table>
-</div>
-<div class="admonitionblock warning">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-warning" title="Warning"></i>
-</td>
-<td class="content">
-The support for verifying the size of JSON arrays is experimental. If you want
-to turn it on, please set the value of the following system property to <code>true</code>:
-<code>spring.cloud.contract.verifier.assert.size</code>. By default, this feature is set to <code>false</code>.
-You can also provide the <code>assertJsonSize</code> property in the plugin configuration.
-</td>
-</tr>
-</table>
-</div>
-<div class="admonitionblock warning">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-warning" title="Warning"></i>
-</td>
-<td class="content">
-Because JSON structure can have any form, it can be impossible to parse it
-properly when using the Groovy DSL and the <code>value(consumer(&#8230;&#8203;), producer(&#8230;&#8203;))</code> notation in <code>GString</code>. That
-is why you should use the Groovy Map notation.
-</td>
-</tr>
-</table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_common_top_level_elements"><a class="link" href="#_common_top_level_elements">8.2. Common Top-Level elements</a></h3>
-<div class="paragraph">
-<p>The following sections describe the most common top-level elements:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="#contract-dsl-description">Description</a></p>
-</li>
-<li>
-<p><a href="#contract-dsl-name">Name</a></p>
-</li>
-<li>
-<p><a href="#contract-dsl-ignoring-contracts">Ignoring Contracts</a></p>
-</li>
-<li>
-<p><a href="#contract-dsl-passing-values-from-files">Passing Values from Files</a></p>
-</li>
-<li>
-<p><a href="#contract-dsl-http-top-level-elements">HTTP Top-Level Elements</a></p>
-</li>
-</ul>
-</div>
-<div class="sect3">
-<h4 id="contract-dsl-description"><a class="link" href="#contract-dsl-description">8.2.1. Description</a></h4>
-<div class="paragraph">
-<p>You can add a <code>description</code> to your contract. The description is arbitrary text. The
-following code shows an example:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">			org.springframework.cloud.contract.spec.Contract.make {
-				description('''
-given:
-	An input
-when:
-	Sth happens
-then:
-	Output
-''')
-			}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">description: Some description
-name: some name
-priority: 8
-ignored: true
-request:
-  url: /foo
-  queryParameters:
-    a: b
-    b: c
-  method: PUT
-  headers:
-    foo: bar
-    fooReq: baz
-  body:
-    foo: bar
-  matchers:
-    body:
-      - path: $.foo
-        type: by_regex
-        value: bar
-    headers:
-      - key: foo
-        regex: bar
-response:
-  status: 200
-  headers:
-    foo2: bar
-    foo3: foo33
-    fooRes: baz
-  body:
-    foo2: bar
-    foo3: baz
-    nullValue: null
-  matchers:
-    body:
-      - path: $.foo2
-        type: by_regex
-        value: bar
-      - path: $.foo3
-        type: by_command
-        value: executeMe($it)
-      - path: $.nullValue
-        type: by_null
-        value: null
-    headers:
-      - key: foo2
-        regex: bar
-      - key: foo3
-        command: andMeToo($it)</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="contract-dsl-name"><a class="link" href="#contract-dsl-name">8.2.2. Name</a></h4>
-<div class="paragraph">
-<p>You can provide a name for your contract. Assume that you provided the following name:
-<code>should register a user</code>. If you do so, the name of the autogenerated test is
-<code>validate_should_register_a_user</code>. Also, the name of the stub in a WireMock stub is
-<code>should_register_a_user.json</code>.</p>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-You must ensure that the name does not contain any characters that make the
-generated test not compile. Also, remember that, if you provide the same name for
-multiple contracts, your autogenerated tests fail to compile and your generated stubs
-override each other.
-</td>
-</tr>
-</table>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	name("some_special_name")
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">name: some name</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="contract-dsl-ignoring-contracts"><a class="link" href="#contract-dsl-ignoring-contracts">8.2.3. Ignoring Contracts</a></h4>
-<div class="paragraph">
-<p>If you want to ignore a contract, you can either set a value of ignored contracts in the
-plugin configuration or set the <code>ignored</code> property on the contract itself:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	ignored()
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">ignored: true</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="contract-dsl-passing-values-from-files"><a class="link" href="#contract-dsl-passing-values-from-files">8.2.4. Passing Values from Files</a></h4>
-<div class="paragraph">
-<p>Starting with version <code>1.2.0</code>, you can pass values from files. Assume that you have the
-following resources in our project.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── src
-    └── test
-        └── resources
-            └── contracts
-                ├── readFromFile.groovy
-                ├── request.json
-                └── response.json</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Further assume that your contract is as follows:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">/*
- * Copyright 2013-2019 the original author or authors.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *      https://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
-import org.springframework.cloud.contract.spec.Contract
-
-Contract.make {
-	request {
-		method('PUT')
-		headers {
-			contentType(applicationJson())
-		}
-		body(file("request.json"))
-		url("/1")
-	}
-	response {
-		status OK()
-		body(file("response.json"))
-		headers {
-			contentType(applicationJson())
-		}
-	}
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
-  method: GET
-  url: /foo
-  bodyFromFile: request.json
-response:
-  status: 200
-  bodyFromFile: response.json</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Further assume that the JSON files is as follows:</p>
-</div>
-<div class="paragraph">
-<p><strong>request.json</strong></p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
-  "status": "REQUEST"
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><strong>response.json</strong></p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
-  "status": "RESPONSE"
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>When test or stub generation takes place, the contents of the file is passed to the body
-of a request or a response. The name of the file needs to be a file with location
-relative to the folder in which the contract lays.</p>
-</div>
-<div class="paragraph">
-<p>If you need to pass the contents of a file in a binary form
-it&#8217;s enough for you to use the <code>fileAsBytes</code> method in Groovy DSL or <code>bodyFromFileAsBytes</code> field in YAML.</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">import org.springframework.cloud.contract.spec.Contract
-
-Contract.make {
-	request {
-		url("/1")
-		method(PUT())
-		headers {
-			contentType(applicationOctetStream())
-		}
-		body(fileAsBytes("request.pdf"))
-	}
-	response {
-		status 200
-		body(fileAsBytes("response.pdf"))
-		headers {
-			contentType(applicationOctetStream())
-		}
-	}
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
-  url: /1
-  method: PUT
-  headers:
-    Content-Type: application/octet-stream
-  bodyFromFileAsBytes: request.pdf
-response:
-  status: 200
-  bodyFromFileAsBytes: response.pdf
-  headers:
-    Content-Type: application/octet-stream</code></pre>
-</div>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-You should use this approach whenever you want to work with binary payloads both for HTTP and messaging.
-</td>
-</tr>
-</table>
-</div>
-</div>
-<div class="sect3">
-<h4 id="contract-dsl-http-top-level-elements"><a class="link" href="#contract-dsl-http-top-level-elements">8.2.5. HTTP Top-Level Elements</a></h4>
-<div class="paragraph">
-<p>The following methods can be called in the top-level closure of a contract definition.
-<code>request</code> and <code>response</code> are mandatory. <code>priority</code> is optional.</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	// Definition of HTTP request part of the contract
-	// (this can be a valid request or invalid depending
-	// on type of contract being specified).
-	request {
-		method GET()
-		url "/foo"
-		//...
-	}
-
-	// Definition of HTTP response part of the contract
-	// (a service implementing this contract should respond
-	// with following response after receiving request
-	// specified in "request" part above).
-	response {
-		status 200
-		//...
-	}
-
-	// Contract priority, which can be used for overriding
-	// contracts (1 is highest). Priority is optional.
-	priority 1
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">priority: 8
-request:
-...
-response:
-...</code></pre>
-</div>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-If you want to make your contract have a <strong>higher</strong> value of priority
-you need to pass a <strong>lower</strong> number to the <code>priority</code> tag / method. E.g. <code>priority</code> with
-value <code>5</code> has <strong>higher</strong> priority than <code>priority</code> with value <code>10</code>.
-</td>
-</tr>
-</table>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_request"><a class="link" href="#_request">8.3. Request</a></h3>
-<div class="paragraph">
-<p>The HTTP protocol requires only <strong>method and url</strong> to be specified in a request. The
-same information is mandatory in request definition of the Contract.</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	request {
-		// HTTP request method (GET/POST/PUT/DELETE).
-		method 'GET'
-
-		// Path component of request URL is specified as follows.
-		urlPath('/users')
-	}
-
-	response {
-		//...
-		status 200
-	}
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">method: PUT
-url: /foo</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>It is possible to specify an absolute rather than relative <code>url</code>, but using <code>urlPath</code> is
-the recommended way, as doing so makes the tests <strong>host-independent</strong>.</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	request {
-		method 'GET'
-
-		// Specifying `url` and `urlPath` in one contract is illegal.
-		url('http://localhost:8888/users')
-	}
-
-	response {
-		//...
-		status 200
-	}
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
-  method: PUT
-  urlPath: /foo</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><code>request</code> may contain <strong>query parameters</strong>.</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	request {
-		//...
-		method GET()
-
-		urlPath('/users') {
-
-			// Each parameter is specified in form
-			// `'paramName' : paramValue` where parameter value
-			// may be a simple literal or one of matcher functions,
-			// all of which are used in this example.
-			queryParameters {
-
-				// If a simple literal is used as value
-				// default matcher function is used (equalTo)
-				parameter 'limit': 100
-
-				// `equalTo` function simply compares passed value
-				// using identity operator (==).
-				parameter 'filter': equalTo("email")
-
-				// `containing` function matches strings
-				// that contains passed substring.
-				parameter 'gender': value(consumer(containing("[mf]")), producer('mf'))
-
-				// `matching` function tests parameter
-				// against passed regular expression.
-				parameter 'offset': value(consumer(matching("[0-9]+")), producer(123))
-
-				// `notMatching` functions tests if parameter
-				// does not match passed regular expression.
-				parameter 'loginStartsWith': value(consumer(notMatching(".{0,2}")), producer(3))
-			}
-		}
-
-		//...
-	}
-
-	response {
-		//...
-		status 200
-	}
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
-...
-  queryParameters:
-    a: b
-    b: c
-  headers:
-    foo: bar
-    fooReq: baz
-  cookies:
-    foo: bar
-    fooReq: baz
-  body:
-    foo: bar
-  matchers:
-    body:
-      - path: $.foo
-        type: by_regex
-        value: bar
-    headers:
-      - key: foo
-        regex: bar
-response:
-  status: 200
-  fixedDelayMilliseconds: 1000
-  headers:
-    foo2: bar
-    foo3: foo33
-    fooRes: baz
-  body:
-    foo2: bar
-    foo3: baz
-    nullValue: null
-  matchers:
-    body:
-      - path: $.foo2
-        type: by_regex
-        value: bar
-      - path: $.foo3
-        type: by_command
-        value: executeMe($it)
-      - path: $.nullValue
-        type: by_null
-        value: null
-    headers:
-      - key: foo2
-        regex: bar
-      - key: foo3
-        command: andMeToo($it)
-    cookies:
-      - key: foo2
-        regex: bar
-      - key: foo3
-        predefined:</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><code>request</code> may contain additional <strong>request headers</strong>, as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	request {
-		//...
-		method GET()
-		url "/foo"
-
-		// Each header is added in form `'Header-Name' : 'Header-Value'`.
-		// there are also some helper methods
-		headers {
-			header 'key': 'value'
-			contentType(applicationJson())
-		}
-
-		//...
-	}
-
-	response {
-		//...
-		status 200
-	}
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
-...
-headers:
-  foo: bar
-  fooReq: baz</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><code>request</code> may contain additional <strong>request cookies</strong>, as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	request {
-		//...
-		method GET()
-		url "/foo"
-
-		// Each Cookies is added in form `'Cookie-Key' : 'Cookie-Value'`.
-		// there are also some helper methods
-		cookies {
-			cookie 'key': 'value'
-			cookie('another_key', 'another_value')
-		}
-
-		//...
-	}
-
-	response {
-		//...
-		status 200
-	}
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
-...
-cookies:
-  foo: bar
-  fooReq: baz</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><code>request</code> may contain a <strong>request body</strong>:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	request {
-		//...
-		method GET()
-		url "/foo"
-
-		// Currently only JSON format of request body is supported.
-		// Format will be determined from a header or body's content.
-		body '''{ "login" : "john", "name": "John The Contract" }'''
-	}
-
-	response {
-		//...
-		status 200
-	}
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
-...
-body:
-  foo: bar</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><code>request</code> may contain <strong>multipart</strong> elements. To include multipart elements, use the
-<code>multipart</code> method/section, as shown in the following examples</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy"></code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
-  method: PUT
-  url: /multipart
-  headers:
-    Content-Type: multipart/form-data;boundary=AaB03x
-  multipart:
-    params:
-      # key (parameter name), value (parameter value) pair
-      formParameter: '"formParameterValue"'
-      someBooleanParameter: true
-    named:
-      - paramName: file
-        fileName: filename.csv
-        fileContent: file content
-  matchers:
-    multipart:
-      params:
-        - key: formParameter
-          regex: ".+"
-        - key: someBooleanParameter
-          predefined: any_boolean
-      named:
-        - paramName: file
-          fileName:
-            predefined: non_empty
-          fileContent:
-            predefined: non_empty
-response:
-  status: 200</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In the preceding example, we define parameters in either of two ways:</p>
-</div>
-<div class="ulist">
-<div class="title">Groovy DSL</div>
-<ul>
-<li>
-<p>Directly, by using the map notation, where the value can be a dynamic property (such as
-<code>formParameter: $(consumer(&#8230;&#8203;), producer(&#8230;&#8203;))</code>).</p>
-</li>
-<li>
-<p>By using the <code>named(&#8230;&#8203;)</code> method that lets you set a named parameter. A named parameter
-can set a <code>name</code> and <code>content</code>. You can call it either via a method with two  arguments,
-such as <code>named("fileName", "fileContent")</code>, or via a map notation, such as
-<code>named(name: "fileName", content: "fileContent")</code>.</p>
-</li>
-</ul>
-</div>
-<div class="ulist">
-<div class="title">YAML</div>
-<ul>
-<li>
-<p>The multipart parameters are set via <code>multipart.params</code> section</p>
-</li>
-<li>
-<p>The named parameters (the <code>fileName</code> and <code>fileContent</code> for a given parameter name)
-can be set via the <code>multipart.named</code> section. That section contains
-the <code>paramName</code> (name of the parameter), <code>fileName</code> (name of the file),
-<code>fileContent</code> (content of the file) fields</p>
-</li>
-<li>
-<p>The dynamic bits can be set via the <code>matchers.multipart</code> section</p>
-<div class="ulist">
-<ul>
-<li>
-<p>for parameters use the <code>params</code> section that can accept
-<code>regex</code> or a <code>predefined</code> regular expression</p>
-</li>
-<li>
-<p>for named params use the <code>named</code> section where first you
-define the parameter name via <code>paramName</code> and then you can pass the
-parametrization of either <code>fileName</code> or <code>fileContent</code> via
-<code>regex</code> or a <code>predefined</code> regular expression</p>
-</li>
-</ul>
-</div>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>From this contract, the generated test is as follows:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">// given:
- MockMvcRequestSpecification request = given()
-   .header("Content-Type", "multipart/form-data;boundary=AaB03x")
-   .param("formParameter", "\"formParameterValue\"")
-   .param("someBooleanParameter", "true")
-   .multiPart("file", "filename.csv", "file content".getBytes());
-
-// when:
- ResponseOptions response = given().spec(request)
-   .put("/multipart");
-
-// then:
- assertThat(response.statusCode()).isEqualTo(200);</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The WireMock stub is as follows:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">			'''
-{
-  "request" : {
-	"url" : "/multipart",
-	"method" : "PUT",
-	"headers" : {
-	  "Content-Type" : {
-		"matches" : "multipart/form-data;boundary=AaB03x.*"
-	  }
-	},
-	"bodyPatterns" : [ {
-		"matches" : ".*--(.*)\\r\\nContent-Disposition: form-data; name=\\"formParameter\\"\\r\\n(Content-Type: .*\\r\\n)?(Content-Transfer-Encoding: .*\\r\\n)?(Content-Length: \\\\d+\\r\\n)?\\r\\n\\".+\\"\\r\\n--\\\\1.*"
-  		}, {
-    			"matches" : ".*--(.*)\\r\\nContent-Disposition: form-data; name=\\"someBooleanParameter\\"\\r\\n(Content-Type: .*\\r\\n)?(Content-Transfer-Encoding: .*\\r\\n)?(Content-Length: \\\\d+\\r\\n)?\\r\\n(true|false)\\r\\n--\\\\1.*"
-  		}, {
-	  "matches" : ".*--(.*)\\r\\nContent-Disposition: form-data; name=\\"file\\"; filename=\\"[\\\\S\\\\s]+\\"\\r\\n(Content-Type: .*\\r\\n)?(Content-Transfer-Encoding: .*\\r\\n)?(Content-Length: \\\\d+\\r\\n)?\\r\\n[\\\\S\\\\s]+\\r\\n--\\\\1.*"
-	} ]
-  },
-  "response" : {
-	"status" : 200,
-	"transformers" : [ "response-template", "foo-transformer" ]
-  }
-}
-	'''</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_response"><a class="link" href="#_response">8.4. Response</a></h3>
-<div class="paragraph">
-<p>The response must contain an <strong>HTTP status code</strong> and may contain other information. The
-following code shows an example:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	request {
-		//...
-		method GET()
-		url "/foo"
-	}
-	response {
-		// Status code sent by the server
-		// in response to request specified above.
-		status OK()
-	}
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">response:
-...
-status: 200</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Besides status, the response may contain <strong>headers</strong>, <strong>cookies</strong> and a <strong>body</strong>, both of which are
-specified the same way as in the request (see the previous paragraph).</p>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-Via the Groovy DSL you can reference the <code>org.springframework.cloud.contract.spec.internal.HttpStatus</code>
-methods to provide a meaningful status instead of a digit. E.g. you can call
-<code>OK()</code> for a status <code>200</code> or <code>BAD_REQUEST()</code> for <code>400</code>.
-</td>
-</tr>
-</table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_dynamic_properties"><a class="link" href="#_dynamic_properties">8.5. Dynamic properties</a></h3>
-<div class="paragraph">
-<p>The contract can contain some dynamic properties: timestamps, IDs, and so on. You do not
-want to force the consumers to stub their clocks to always return the same value of time
-so that it gets matched by the stub.</p>
-</div>
-<div class="paragraph">
-<p>For Groovy DSL you can provide the dynamic parts in your contracts
-in two ways: pass them directly in the body or set them in a separate section called
-<code>bodyMatchers</code>.</p>
-</div>
-<div class="admonitionblock note">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-note" title="Note"></i>
-</td>
-<td class="content">
-Before 2.0.0 these were set using <code>testMatchers</code> and <code>stubMatchers</code>,
-check out the <a href="https://github.com/spring-cloud/spring-cloud-contract/wiki/Spring-Cloud-Contract-2.0-Migration-Guide">migration guide</a> for more information.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>For YAML you can only use the <code>matchers</code> section.</p>
-</div>
-<div class="sect3">
-<h4 id="_dynamic_properties_inside_the_body"><a class="link" href="#_dynamic_properties_inside_the_body">8.5.1. Dynamic properties inside the body</a></h4>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-This section is valid only for Groovy DSL. Check out the
-<a href="#contract-matchers">Dynamic Properties in the Matchers Sections</a> section for YAML examples of a similar feature.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>You can set the properties inside the body either with the <code>value</code> method or, if you use
-the Groovy map notation, with <code>$()</code>. The following example shows how to set dynamic
-properties with the value method:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">value(consumer(...), producer(...))
-value(c(...), p(...))
-value(stub(...), test(...))
-value(client(...), server(...))</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following example shows how to set dynamic properties with <code>$()</code>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">$(consumer(...), producer(...))
-$(c(...), p(...))
-$(stub(...), test(...))
-$(client(...), server(...))</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Both approaches work equally well. <code>stub</code> and <code>client</code> methods are aliases over the <code>consumer</code>
-method. Subsequent sections take a closer look at what you can do with those values.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_regular_expressions"><a class="link" href="#_regular_expressions">8.5.2. Regular expressions</a></h4>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-This section is valid only for Groovy DSL. Check out the
-<a href="#contract-matchers">Dynamic Properties in the Matchers Sections</a> section for YAML examples of a similar feature.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>You can use regular expressions to write your requests in Contract DSL. Doing so is
-particularly useful when you want to indicate that a given response should be provided
-for requests that follow a given pattern. Also, you can use regular expressions when you
-need to use patterns and not exact values both for your test and your server side tests.</p>
-</div>
-<div class="paragraph">
-<p>Make sure that regex matches a whole region of a sequence as internally a call to
-<a href="https://docs.oracle.com/javase/8/docs/api/java/util/regex/Matcher.html#matches--">Pattern.matches()</a>
-is called. For instance, <code>abc</code> pattern doesn&#8217;t match <code>aabc</code> string but <code>.abc</code> does.
-There are several additional <a href="#regex-limitations">known limitations</a> as well.</p>
-</div>
-<div class="paragraph">
-<p>The following example shows how to use regular expressions to write a request:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	request {
-		method('GET')
-		url $(consumer(~/\/[0-9]{2}/), producer('/12'))
-	}
-	response {
-		status OK()
-		body(
-				id: $(anyNumber()),
-				surname: $(
-						consumer('Kowalsky'),
-						producer(regex('[a-zA-Z]+'))
-				),
-				name: 'Jan',
-				created: $(consumer('2014-02-02 12:23:43'), producer(execute('currentDate(it)'))),
-				correlationId: value(consumer('5d1f9fef-e0dc-4f3d-a7e4-72d2220dd827'),
-						producer(regex('[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}'))
-				)
-		)
-		headers {
-			header 'Content-Type': 'text/plain'
-		}
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You can also provide only one side of the communication with a regular expression. If you
-do so, then the contract engine automatically provides the generated string that matches
-the provided regular expression. The following code shows an example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	request {
-		method 'PUT'
-		url value(consumer(regex('/foo/[0-9]{5}')))
-		body([
-				requestElement: $(consumer(regex('[0-9]{5}')))
-		])
-		headers {
-			header('header', $(consumer(regex('application\\/vnd\\.fraud\\.v1\\+json;.*'))))
-		}
-	}
-	response {
-		status OK()
-		body([
-				responseElement: $(producer(regex('[0-9]{7}')))
-		])
-		headers {
-			contentType("application/vnd.fraud.v1+json")
-		}
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In the preceding example, the opposite side of the communication has the respective data
-generated for request and response.</p>
-</div>
-<div class="paragraph">
-<p>Spring Cloud Contract comes with a series of predefined regular expressions that you can
-use in your contracts, as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">protected static final Pattern TRUE_OR_FALSE = Pattern.compile("(true|false)");
-
-protected static final Pattern ALPHA_NUMERIC = Pattern.compile("[a-zA-Z0-9]+");
-
-protected static final Pattern ONLY_ALPHA_UNICODE = Pattern.compile("[\\p{L}]*");
-
-protected static final Pattern NUMBER = Pattern.compile("-?(\\d*\\.\\d+|\\d+)");
-
-protected static final Pattern INTEGER = Pattern.compile("-?(\\d+)");
-
-protected static final Pattern POSITIVE_INT = Pattern.compile("([1-9]\\d*)");
-
-protected static final Pattern DOUBLE = Pattern.compile("-?(\\d*\\.\\d+)");
-
-protected static final Pattern HEX = Pattern.compile("[a-fA-F0-9]+");
-
-protected static final Pattern IP_ADDRESS = Pattern.compile(
-		"([01]?\\d\\d?|2[0-4]\\d|25[0-5])\\.([01]?\\d\\d?|2[0-4]\\d|25[0-5])\\.([01]?\\d\\d?|2[0-4]\\d|25[0-5])\\.([01]?\\d\\d?|2[0-4]\\d|25[0-5])");
-
-protected static final Pattern HOSTNAME_PATTERN = Pattern
-		.compile("((http[s]?|ftp):/)/?([^:/\\s]+)(:[0-9]{1,5})?");
-
-protected static final Pattern EMAIL = Pattern
-		.compile("[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,6}");
-
-protected static final Pattern URL = UrlHelper.URL;
-
-protected static final Pattern HTTPS_URL = UrlHelper.HTTPS_URL;
-
-protected static final Pattern UUID = Pattern
-		.compile("[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}");
-
-protected static final Pattern ANY_DATE = Pattern
-		.compile("(\\d\\d\\d\\d)-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])");
-
-protected static final Pattern ANY_DATE_TIME = Pattern.compile(
-		"([0-9]{4})-(1[0-2]|0[1-9])-(3[01]|0[1-9]|[12][0-9])T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])");
-
-protected static final Pattern ANY_TIME = Pattern
-		.compile("(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])");
-
-protected static final Pattern NON_EMPTY = Pattern.compile("[\\S\\s]+");
-
-protected static final Pattern NON_BLANK = Pattern.compile("^\\s*\\S[\\S\\s]*");
-
-protected static final Pattern ISO8601_WITH_OFFSET = Pattern.compile(
-		"([0-9]{4})-(1[0-2]|0[1-9])-(3[01]|0[1-9]|[12][0-9])T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])(\\.\\d{3})?(Z|[+-][01]\\d:[0-5]\\d)");
-
-protected static Pattern anyOf(String... values) {
-	return Pattern.compile(Arrays.stream(values).map(it -&gt; '^' + it + '$')
-			.collect(Collectors.joining("|")));
-}
-
-public static String multipartParam(Object name, Object value) {
-	return ".*--(.*)\r\nContent-Disposition: form-data; name=\"" + name
-			+ "\"\r\n(Content-Type: .*\r\n)?(Content-Transfer-Encoding: .*\r\n)?(Content-Length: \\d+\r\n)?\r\n"
-			+ value + "\r\n--\\1.*";
-}
-
-public static String multipartFile(Object name, Object filename, Object content,
-		Object contentType) {
-	return ".*--(.*)\r\nContent-Disposition: form-data; name=\"" + name
-			+ "\"; filename=\"" + filename + "\"\r\n(Content-Type: "
-			+ toContentType(contentType)
-			+ "\r\n)?(Content-Transfer-Encoding: .*\r\n)?(Content-Length: \\d+\r\n)?\r\n"
-			+ content + "\r\n--\\1.*";
-}
-
-private static String toContentType(Object contentType) {
-	if (contentType == null) {
-		return ".*";
-	}
-	if (contentType instanceof RegexProperty) {
-		return ((RegexProperty) contentType).pattern();
-	}
-	return contentType.toString();
-}
-
-public RegexProperty onlyAlphaUnicode() {
-	return new RegexProperty(ONLY_ALPHA_UNICODE).asString();
-}
-
-public RegexProperty alphaNumeric() {
-	return new RegexProperty(ALPHA_NUMERIC).asString();
-}
-
-public RegexProperty number() {
-	return new RegexProperty(NUMBER).asDouble();
-}
-
-public RegexProperty positiveInt() {
-	return new RegexProperty(POSITIVE_INT).asInteger();
-}
-
-public RegexProperty anyBoolean() {
-	return new RegexProperty(TRUE_OR_FALSE).asBooleanType();
-}
-
-public RegexProperty anInteger() {
-	return new RegexProperty(INTEGER).asInteger();
-}
-
-public RegexProperty aDouble() {
-	return new RegexProperty(DOUBLE).asDouble();
-}
-
-public RegexProperty ipAddress() {
-	return new RegexProperty(IP_ADDRESS).asString();
-}
-
-public RegexProperty hostname() {
-	return new RegexProperty(HOSTNAME_PATTERN).asString();
-}
-
-public RegexProperty email() {
-	return new RegexProperty(EMAIL).asString();
-}
-
-public RegexProperty url() {
-	return new RegexProperty(URL).asString();
-}
-
-public RegexProperty httpsUrl() {
-	return new RegexProperty(HTTPS_URL).asString();
-}
-
-public RegexProperty uuid() {
-	return new RegexProperty(UUID).asString();
-}
-
-public RegexProperty isoDate() {
-	return new RegexProperty(ANY_DATE).asString();
-}
-
-public RegexProperty isoDateTime() {
-	return new RegexProperty(ANY_DATE_TIME).asString();
-}
-
-public RegexProperty isoTime() {
-	return new RegexProperty(ANY_TIME).asString();
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In your contract, you can use it as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract dslWithOptionalsInString = Contract.make {
-	priority 1
-	request {
-		method POST()
-		url '/users/password'
-		headers {
-			contentType(applicationJson())
-		}
-		body(
-				email: $(consumer(optional(regex(email()))), producer('abc@abc.com')),
-				callback_url: $(consumer(regex(hostname())), producer('http://partners.com'))
-		)
-	}
-	response {
-		status 404
-		headers {
-			contentType(applicationJson())
-		}
-		body(
-				code: value(consumer("123123"), producer(optional("123123"))),
-				message: "User not found by email = [${value(producer(regex(email())), consumer('not.existing@user.com'))}]"
-		)
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>To make matters even simpler you can use a set of predefined objects that will automatically assume that you want a regular expression to be passed.
-All of those methods start with <code>any</code> prefix:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java"></code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>and this is an example of how you can reference those methods:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract contractDsl = Contract.make {
-	name "foo"
-	label 'trigger_event'
-	input {
-		triggeredBy('toString()')
-	}
-	outputMessage {
-		sentTo 'topic.rateablequote'
-		body([
-				alpha            : $(anyAlphaUnicode()),
-				number           : $(anyNumber()),
-				anInteger        : $(anyInteger()),
-				positiveInt      : $(anyPositiveInt()),
-				aDouble          : $(anyDouble()),
-				aBoolean         : $(aBoolean()),
-				ip               : $(anyIpAddress()),
-				hostname         : $(anyHostname()),
-				email            : $(anyEmail()),
-				url              : $(anyUrl()),
-				httpsUrl         : $(anyHttpsUrl()),
-				uuid             : $(anyUuid()),
-				date             : $(anyDate()),
-				dateTime         : $(anyDateTime()),
-				time             : $(anyTime()),
-				iso8601WithOffset: $(anyIso8601WithOffset()),
-				nonBlankString   : $(anyNonBlankString()),
-				nonEmptyString   : $(anyNonEmptyString()),
-				anyOf            : $(anyOf('foo', 'bar'))
-		])
-	}
-}</code></pre>
-</div>
-</div>
-<div class="sect4">
-<h5 id="regex-limitations"><a class="link" href="#regex-limitations">Limitations</a></h5>
-<div class="admonitionblock warning">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-warning" title="Warning"></i>
-</td>
-<td class="content">
-Due to certain limitations of <code>Xeger</code> library that generates string out of
-regex, do not use <code>$</code> and <code>^</code> signs in your regex if you rely on automatic
-generation. <a href="https://github.com/spring-cloud/spring-cloud-contract/issues/899">Issue 899</a>
-</td>
-</tr>
-</table>
-</div>
-<div class="admonitionblock warning">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-warning" title="Warning"></i>
-</td>
-<td class="content">
-Do not use <code>LocalDate</code> instance as a value for <code>$</code> like this <code>$(consumer(LocalDate.now()))</code>.
-It causes <code>java.lang.StackOverflowError</code>. Use <code>$(consumer(LocalDate.now().toString()))</code> instead.
-<a href="https://github.com/spring-cloud/spring-cloud-contract/issues/900">Issue 900</a>
-</td>
-</tr>
-</table>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_passing_optional_parameters"><a class="link" href="#_passing_optional_parameters">8.5.3. Passing Optional Parameters</a></h4>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-This section is valid only for Groovy DSL. Check out the
-<a href="#contract-matchers">Dynamic Properties in the Matchers Sections</a> section for YAML examples of a similar feature.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>It is possible to provide optional parameters in your contract. However, you can provide
-optional parameters only for the following:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><em>STUB</em> side of the Request</p>
-</li>
-<li>
-<p><em>TEST</em> side of the Response</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>The following example shows how to provide optional parameters:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	priority 1
-	name "optionals"
-	request {
-		method 'POST'
-		url '/users/password'
-		headers {
-			contentType(applicationJson())
-		}
-		body(
-				email: $(consumer(optional(regex(email()))), producer('abc@abc.com')),
-				callback_url: $(consumer(regex(hostname())), producer('https://partners.com'))
-		)
-	}
-	response {
-		status 404
-		headers {
-			header 'Content-Type': 'application/json'
-		}
-		body(
-				code: value(consumer("123123"), producer(optional("123123")))
-		)
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>By wrapping a part of the body with the <code>optional()</code> method, you create a regular
-expression that must be present 0 or more times.</p>
-</div>
-<div class="paragraph">
-<p>If you use Spock for, the following test would be generated from the previous example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">					"""\
-package com.example
-
-import com.jayway.jsonpath.DocumentContext
-import com.jayway.jsonpath.JsonPath
-import spock.lang.Specification
-import io.restassured.module.mockmvc.specification.MockMvcRequestSpecification
-import io.restassured.response.ResponseOptions
-
-import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*
-import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson
-import static io.restassured.module.mockmvc.RestAssuredMockMvc.*
-
-@SuppressWarnings("rawtypes")
-class FooSpec extends Specification {
-
-\tdef validate_optionals() throws Exception {
-\t\tgiven:
-\t\t\tMockMvcRequestSpecification request = given()
-\t\t\t\t\t.header("Content-Type", "application/json")
-\t\t\t\t\t.body('''{"email":"abc@abc.com","callback_url":"https://partners.com"}''')
-
-\t\twhen:
-\t\t\tResponseOptions response = given().spec(request)
-\t\t\t\t\t.post("/users/password")
-
-\t\tthen:
-\t\t\tresponse.statusCode() == 404
-\t\t\tresponse.header("Content-Type") == 'application/json'
-
-\t\tand:
-\t\t\tDocumentContext parsedJson = JsonPath.parse(response.body.asString())
-\t\t\tassertThatJson(parsedJson).field("['code']").matches("(123123)?")
-\t}
-
-}
-"""</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following stub would also be generated:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">					'''
-{
-  "request" : {
-	"url" : "/users/password",
-	"method" : "POST",
-	"bodyPatterns" : [ {
-	  "matchesJsonPath" : "$[?(@.['email'] =~ /([a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\\\.[a-zA-Z]{2,6})?/)]"
-	}, {
-	  "matchesJsonPath" : "$[?(@.['callback_url'] =~ /((http[s]?|ftp):\\\\/)\\\\/?([^:\\\\/\\\\s]+)(:[0-9]{1,5})?/)]"
-	} ],
-	"headers" : {
-	  "Content-Type" : {
-		"equalTo" : "application/json"
-	  }
-	}
-  },
-  "response" : {
-	"status" : 404,
-	"body" : "{\\"code\\":\\"123123\\",\\"message\\":\\"User not found by email == [not.existing@user.com]\\"}",
-	"headers" : {
-	  "Content-Type" : "application/json"
-	}
-  },
-  "priority" : 1
-}
-'''</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_executing_custom_methods_on_the_server_side"><a class="link" href="#_executing_custom_methods_on_the_server_side">8.5.4. Executing Custom Methods on the Server Side</a></h4>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-This section is valid only for Groovy DSL. Check out the
-<a href="#contract-matchers">Dynamic Properties in the Matchers Sections</a> section for YAML examples of a similar feature.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>You can define a method call that executes on the server side during the test. Such a
-method can be added to the class defined as "baseClassForTests" in the configuration. The
-following code shows an example of the contract portion of the test case:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy"></code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following code shows the base class portion of the test case:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">abstract class BaseMockMvcSpec extends Specification {
-
-	def setup() {
-		RestAssuredMockMvc.standaloneSetup(new PairIdController())
-	}
-
-	void isProperCorrelationId(Integer correlationId) {
-		assert correlationId == 123456
-	}
-
-	void isEmpty(String value) {
-		assert value == null
-	}
-
-}</code></pre>
-</div>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-You cannot use both a String and <code>execute</code> to perform concatenation. For
-example, calling <code>header('Authorization', 'Bearer ' + execute('authToken()'))</code> leads to
-improper results. Instead, call <code>header('Authorization', execute('authToken()'))</code> and
-ensure that the <code>authToken()</code> method returns everything you need.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>The type of the object read from the JSON can be one of the following, depending on the
-JSON path:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>String</code>: If you point to a <code>String</code> value in the JSON.</p>
-</li>
-<li>
-<p><code>JSONArray</code>: If you point to a <code>List</code> in the JSON.</p>
-</li>
-<li>
-<p><code>Map</code>: If you point to a <code>Map</code> in the JSON.</p>
-</li>
-<li>
-<p><code>Number</code>: If you point to <code>Integer</code>, <code>Double</code> etc. in the JSON.</p>
-</li>
-<li>
-<p><code>Boolean</code>: If you point to a <code>Boolean</code> in the JSON.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>In the request part of the contract, you can specify that the <code>body</code> should be taken from
-a method.</p>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-You must provide both the consumer and the producer side. The <code>execute</code> part
-is applied for the whole body - not for parts of it.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>The following example shows how to read an object from JSON:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract contractDsl = Contract.make {
-	request {
-		method 'GET'
-		url '/something'
-		body(
-				$(c('foo'), p(execute('hashCode()')))
-		)
-	}
-	response {
-		status OK()
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The preceding example results in calling the <code>hashCode()</code> method in the request body.
-It should resemble the following code:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">// given:
- MockMvcRequestSpecification request = given()
-   .body(hashCode());
-
-// when:
- ResponseOptions response = given().spec(request)
-   .get("/something");
-
-// then:
- assertThat(response.statusCode()).isEqualTo(200);</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_referencing_the_request_from_the_response"><a class="link" href="#_referencing_the_request_from_the_response">8.5.5. Referencing the Request from the Response</a></h4>
-<div class="paragraph">
-<p>The best situation is to provide fixed values, but sometimes you need to reference a
-request in your response.</p>
-</div>
-<div class="paragraph">
-<p>If you&#8217;re writing contracts using Groovy DSL, you can use the <code>fromRequest()</code> method, which lets
-you reference a bunch of elements from the HTTP request. You can use the following
-options:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>fromRequest().url()</code>: Returns the request URL and query parameters.</p>
-</li>
-<li>
-<p><code>fromRequest().query(String key)</code>: Returns the first query parameter with a given name.</p>
-</li>
-<li>
-<p><code>fromRequest().query(String key, int index)</code>: Returns the nth query parameter with a
-given name.</p>
-</li>
-<li>
-<p><code>fromRequest().path()</code>: Returns the full path.</p>
-</li>
-<li>
-<p><code>fromRequest().path(int index)</code>: Returns the nth path element.</p>
-</li>
-<li>
-<p><code>fromRequest().header(String key)</code>: Returns the first header with a given name.</p>
-</li>
-<li>
-<p><code>fromRequest().header(String key, int index)</code>: Returns the nth header with a given name.</p>
-</li>
-<li>
-<p><code>fromRequest().body()</code>: Returns the full request body.</p>
-</li>
-<li>
-<p><code>fromRequest().body(String jsonPath)</code>: Returns the element from the request that
-matches the JSON Path.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>If you&#8217;re using the YAML contract definition you have to use the
-<a href="https://handlebarsjs.com/">Handlebars</a> <code>{{{ }}}</code> notation with custom, Spring Cloud Contract
- functions to achieve this.</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>{{{ request.url }}}</code>: Returns the request URL and query parameters.</p>
-</li>
-<li>
-<p><code>{{{ request.query.key.[index] }}}</code>: Returns the nth query parameter with a given name.
-E.g. for key <code>foo</code>, first entry <code>{{{ request.query.foo.[0] }}}</code></p>
-</li>
-<li>
-<p><code>{{{ request.path }}}</code>: Returns the full path.</p>
-</li>
-<li>
-<p><code>{{{ request.path.[index] }}}</code>: Returns the nth path element. E.g.
-for first entry <code>`</code>{{{ request.path.[0] }}}</p>
-</li>
-<li>
-<p><code>{{{ request.headers.key }}}</code>: Returns the first header with a given name.</p>
-</li>
-<li>
-<p><code>{{{ request.headers.key.[index] }}}</code>: Returns the nth header with a given name.</p>
-</li>
-<li>
-<p><code>{{{ request.body }}}</code>: Returns the full request body.</p>
-</li>
-<li>
-<p><code>{{{ jsonpath this 'your.json.path' }}}</code>: Returns the element from the request that
-matches the JSON Path. E.g. for json path <code>$.foo</code> - <code>{{{ jsonpath this '$.foo' }}}</code></p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Consider the following contract:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy"></code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
-  method: GET
-  url: /api/v1/xxxx
-  queryParameters:
-    foo:
-      - bar
-      - bar2
-  headers:
-    Authorization:
-      - secret
-      - secret2
-  body:
-    foo: bar
-    baz: 5
-response:
-  status: 200
-  headers:
-    Authorization: "foo {{{ request.headers.Authorization.0 }}} bar"
-  body:
-    url: "{{{ request.url }}}"
-    path: "{{{ request.path }}}"
-    pathIndex: "{{{ request.path.1 }}}"
-    param: "{{{ request.query.foo }}}"
-    paramIndex: "{{{ request.query.foo.1 }}}"
-    authorization: "{{{ request.headers.Authorization.0 }}}"
-    authorization2: "{{{ request.headers.Authorization.1 }}"
-    fullBody: "{{{ request.body }}}"
-    responseFoo: "{{{ jsonpath this '$.foo' }}}"
-    responseBaz: "{{{ jsonpath this '$.baz' }}}"
-    responseBaz2: "Bla bla {{{ jsonpath this '$.foo' }}} bla bla"</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Running a JUnit test generation leads to a test that resembles the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">// given:
- MockMvcRequestSpecification request = given()
-   .header("Authorization", "secret")
-   .header("Authorization", "secret2")
-   .body("{\"foo\":\"bar\",\"baz\":5}");
-
-// when:
- ResponseOptions response = given().spec(request)
-   .queryParam("foo","bar")
-   .queryParam("foo","bar2")
-   .get("/api/v1/xxxx");
-
-// then:
- assertThat(response.statusCode()).isEqualTo(200);
- assertThat(response.header("Authorization")).isEqualTo("foo secret bar");
-// and:
- DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
- assertThatJson(parsedJson).field("['fullBody']").isEqualTo("{\"foo\":\"bar\",\"baz\":5}");
- assertThatJson(parsedJson).field("['authorization']").isEqualTo("secret");
- assertThatJson(parsedJson).field("['authorization2']").isEqualTo("secret2");
- assertThatJson(parsedJson).field("['path']").isEqualTo("/api/v1/xxxx");
- assertThatJson(parsedJson).field("['param']").isEqualTo("bar");
- assertThatJson(parsedJson).field("['paramIndex']").isEqualTo("bar2");
- assertThatJson(parsedJson).field("['pathIndex']").isEqualTo("v1");
- assertThatJson(parsedJson).field("['responseBaz']").isEqualTo(5);
- assertThatJson(parsedJson).field("['responseFoo']").isEqualTo("bar");
- assertThatJson(parsedJson).field("['url']").isEqualTo("/api/v1/xxxx?foo=bar&amp;foo=bar2");
- assertThatJson(parsedJson).field("['responseBaz2']").isEqualTo("Bla bla bar bla bla");</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>As you can see, elements from the request have been properly referenced in the response.</p>
-</div>
-<div class="paragraph">
-<p>The generated WireMock stub should resemble the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
-  "request" : {
-    "urlPath" : "/api/v1/xxxx",
-    "method" : "POST",
-    "headers" : {
-      "Authorization" : {
-        "equalTo" : "secret2"
-      }
-    },
-    "queryParameters" : {
-      "foo" : {
-        "equalTo" : "bar2"
-      }
-    },
-    "bodyPatterns" : [ {
-      "matchesJsonPath" : "$[?(@.['baz'] == 5)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.['foo'] == 'bar')]"
-    } ]
-  },
-  "response" : {
-    "status" : 200,
-    "body" : "{\"authorization\":\"{{{request.headers.Authorization.[0]}}}\",\"path\":\"{{{request.path}}}\",\"responseBaz\":{{{jsonpath this '$.baz'}}} ,\"param\":\"{{{request.query.foo.[0]}}}\",\"pathIndex\":\"{{{request.path.[1]}}}\",\"responseBaz2\":\"Bla bla {{{jsonpath this '$.foo'}}} bla bla\",\"responseFoo\":\"{{{jsonpath this '$.foo'}}}\",\"authorization2\":\"{{{request.headers.Authorization.[1]}}}\",\"fullBody\":\"{{{escapejsonbody}}}\",\"url\":\"{{{request.url}}}\",\"paramIndex\":\"{{{request.query.foo.[1]}}}\"}",
-    "headers" : {
-      "Authorization" : "{{{request.headers.Authorization.[0]}}};foo"
-    },
-    "transformers" : [ "response-template" ]
-  }
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Sending a request such as the one presented in the <code>request</code> part of the contract results
-in sending the following response body:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
-  "url" : "/api/v1/xxxx?foo=bar&amp;foo=bar2",
-  "path" : "/api/v1/xxxx",
-  "pathIndex" : "v1",
-  "param" : "bar",
-  "paramIndex" : "bar2",
-  "authorization" : "secret",
-  "authorization2" : "secret2",
-  "fullBody" : "{\"foo\":\"bar\",\"baz\":5}",
-  "responseFoo" : "bar",
-  "responseBaz" : 5,
-  "responseBaz2" : "Bla bla bar bla bla"
-}</code></pre>
-</div>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-This feature works only with WireMock having a version greater than or equal
-to 2.5.1. The Spring Cloud Contract Verifier uses WireMock&#8217;s
-<code>response-template</code> response transformer. It uses Handlebars to convert the Mustache <code>{{{ }}}</code> templates into
-proper values. Additionally, it registers two helper functions:
-</td>
-</tr>
-</table>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>escapejsonbody</code>: Escapes the request body in a format that can be embedded in a JSON.</p>
-</li>
-<li>
-<p><code>jsonpath</code>: For a given parameter, find an object in the request body.</p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_registering_your_own_wiremock_extension"><a class="link" href="#_registering_your_own_wiremock_extension">8.5.6. Registering Your Own WireMock Extension</a></h4>
-<div class="paragraph">
-<p>WireMock lets you register custom extensions. By default, Spring Cloud Contract registers
-the transformer, which lets you reference a request from a response. If you want to
-provide your own extensions, you can register an implementation of the
-<code>org.springframework.cloud.contract.verifier.dsl.wiremock.WireMockExtensions</code> interface.
-Since we use the spring.factories extension approach, you can create an entry in
-<code>META-INF/spring.factories</code> file similar to the following:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.verifier.dsl.wiremock.WireMockExtensions=\
-org.springframework.cloud.contract.stubrunner.provider.wiremock.TestWireMockExtensions
-org.springframework.cloud.contract.spec.ContractConverter=\
-org.springframework.cloud.contract.stubrunner.TestCustomYamlContractConverter</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following is an example of a custom extension:</p>
-</div>
-<div class="listingblock">
-<div class="title">TestWireMockExtensions.groovy</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">/*
- * Copyright 2013-2019 the original author or authors.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *      https://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
-package org.springframework.cloud.contract.verifier.dsl.wiremock
-
-import com.github.tomakehurst.wiremock.extension.Extension
-
-/**
- * Extension that registers the default transformer and the custom one
- */
-class TestWireMockExtensions implements WireMockExtensions {
-	@Override
-	List&lt;Extension&gt; extensions() {
-		return [
-				new DefaultResponseTransformer(),
-				new CustomExtension()
-		]
-	}
-}
-
-class CustomExtension implements Extension {
-
-	@Override
-	String getName() {
-		return "foo-transformer"
-	}
-}</code></pre>
-</div>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-Remember to override the <code>applyGlobally()</code> method and set it to <code>false</code> if you
-want the transformation to be applied only for a mapping that explicitly requires it.
-</td>
-</tr>
-</table>
-</div>
-</div>
-<div class="sect3">
-<h4 id="contract-matchers"><a class="link" href="#contract-matchers">8.5.7. Dynamic Properties in the Matchers Sections</a></h4>
-<div class="paragraph">
-<p>If you work with <a href="https://docs.pact.io/">Pact</a>, the following discussion may seem familiar.
-Quite a few users are used to having a separation between the body and setting the
-dynamic parts of a contract.</p>
-</div>
-<div class="paragraph">
-<p>You can use the <code>bodyMatchers</code> section for two reasons:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Define the dynamic values that should end up in a stub.
-You can set it in the <code>request</code> or <code>inputMessage</code> part of your contract.</p>
-</li>
-<li>
-<p>Verify the result of your test.
-This section is present in the <code>response</code> or <code>outputMessage</code> side of the
-contract.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Currently, Spring Cloud Contract Verifier supports only JSON Path-based matchers with the
-following matching possibilities:</p>
-</div>
-<div class="ulist">
-<div class="title">Groovy DSL</div>
-<ul>
-<li>
-<p>For the stubs(in tests on the Consumer&#8217;s side):</p>
-<div class="ulist">
-<ul>
-<li>
-<p><code>byEquality()</code>: The value taken from the consumer&#8217;s request via the provided JSON Path must be
-equal to the value provided in the contract.</p>
-</li>
-<li>
-<p><code>byRegex(&#8230;&#8203;)</code>: The value taken from the consumer&#8217;s request via the provided JSON Path must
-match the regex. You can also pass the type of the expected matched value (e.g. <code>asString()</code>, <code>asLong()</code> etc.)</p>
-</li>
-<li>
-<p><code>byDate()</code>: The value taken from the consumer&#8217;s request via the provided JSON Path must
-match the regex for an ISO Date value.</p>
-</li>
-<li>
-<p><code>byTimestamp()</code>: The value taken from the consumer&#8217;s request via the provided JSON Path must
-match the regex for an ISO DateTime value.</p>
-</li>
-<li>
-<p><code>byTime()</code>: The value taken from the consumer&#8217;s request via the provided JSON Path must
-match the regex for an ISO Time value.</p>
-</li>
-</ul>
-</div>
-</li>
-<li>
-<p>For the verification(in generated tests on the Producer&#8217;s side):</p>
-<div class="ulist">
-<ul>
-<li>
-<p><code>byEquality()</code>: The value taken from the producer&#8217;s response via the provided JSON Path must be
-equal to the provided value in the contract.</p>
-</li>
-<li>
-<p><code>byRegex(&#8230;&#8203;)</code>: The value taken from the producer&#8217;s response via the provided JSON Path must
-match the regex.</p>
-</li>
-<li>
-<p><code>byDate()</code>: The value taken from the producer&#8217;s response via the provided JSON Path must match
-the regex for an ISO Date value.</p>
-</li>
-<li>
-<p><code>byTimestamp()</code>: The value taken from the producer&#8217;s response via the provided JSON Path must
-match the regex for an ISO DateTime value.</p>
-</li>
-<li>
-<p><code>byTime()</code>: The value taken from the producer&#8217;s response via the provided JSON Path must match
-the regex for an ISO Time value.</p>
-</li>
-<li>
-<p><code>byType()</code>: The value taken from the producer&#8217;s response via the provided JSON Path needs to be
-of the same type as the type defined in the body of the response in the contract.
-<code>byType</code> can take a closure, in which you can set <code>minOccurrence</code> and <code>maxOccurrence</code>. For the request side, you should use the closure to assert size of the collection.
-That way, you can assert the size of the flattened collection. To check the size of an
-unflattened collection, use a custom method with the <code>byCommand(&#8230;&#8203;)</code> testMatcher.</p>
-</li>
-<li>
-<p><code>byCommand(&#8230;&#8203;)</code>: The value taken from the producer&#8217;s response via the provided JSON Path is
-passed as an input to the custom method that you provide. For example,
-<code>byCommand('foo($it)')</code> results in calling a <code>foo</code> method to which the value matching the
-JSON Path gets passed. The type of the object read from the JSON can be one of the
-following, depending on the JSON path:</p>
-<div class="ulist">
-<ul>
-<li>
-<p><code>String</code>: If you point to a <code>String</code> value.</p>
-</li>
-<li>
-<p><code>JSONArray</code>: If you point to a <code>List</code>.</p>
-</li>
-<li>
-<p><code>Map</code>: If you point to a <code>Map</code>.</p>
-</li>
-<li>
-<p><code>Number</code>: If you point to <code>Integer</code>, <code>Double</code>, or other kind of number.</p>
-</li>
-<li>
-<p><code>Boolean</code>: If you point to a <code>Boolean</code>.</p>
-</li>
-</ul>
-</div>
-</li>
-<li>
-<p><code>byNull()</code>: The value taken from the response via the provided JSON Path must be null</p>
-</li>
-</ul>
-</div>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<div class="title">YAML</div>
-<p><em>Please read the Groovy section for detailed explanation of
-what the types mean</em></p>
-</div>
-<div class="paragraph">
-<p>For YAML the structure of a matcher looks like this</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">- path: $.foo
-  type: by_regex
-  value: bar
-  regexType: as_string</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Or if you want to use one of the predefined regular expressions
-<code>[only_alpha_unicode, number, any_boolean, ip_address, hostname,
-email, url, uuid, iso_date, iso_date_time, iso_time, iso_8601_with_offset, non_empty, non_blank]</code>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">- path: $.foo
-  type: by_regex
-  predefined: only_alpha_unicode</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Below you can find the allowed list of `type`s.</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>For <code>stubMatchers</code>:</p>
-<div class="ulist">
-<ul>
-<li>
-<p><code>by_equality</code></p>
-</li>
-<li>
-<p><code>by_regex</code></p>
-</li>
-<li>
-<p><code>by_date</code></p>
-</li>
-<li>
-<p><code>by_timestamp</code></p>
-</li>
-<li>
-<p><code>by_time</code></p>
-</li>
-<li>
-<p><code>by_type</code></p>
-<div class="ulist">
-<ul>
-<li>
-<p>there are 2 additional fields accepted: <code>minOccurrence</code> and <code>maxOccurrence</code>.</p>
-</li>
-</ul>
-</div>
-</li>
-</ul>
-</div>
-</li>
-<li>
-<p>For <code>testMatchers</code>:</p>
-<div class="ulist">
-<ul>
-<li>
-<p><code>by_equality</code></p>
-</li>
-<li>
-<p><code>by_regex</code></p>
-</li>
-<li>
-<p><code>by_date</code></p>
-</li>
-<li>
-<p><code>by_timestamp</code></p>
-</li>
-<li>
-<p><code>by_time</code></p>
-</li>
-<li>
-<p><code>by_type</code></p>
-<div class="ulist">
-<ul>
-<li>
-<p>there are 2 additional fields accepted: <code>minOccurrence</code> and <code>maxOccurrence</code>.</p>
-</li>
-</ul>
-</div>
-</li>
-<li>
-<p><code>by_command</code></p>
-</li>
-<li>
-<p><code>by_null</code></p>
-</li>
-</ul>
-</div>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>You can also define which type the regular expression corresponds to via the <code>regexType</code> field. Below you can find the allowed list of regular expression types:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>as_integer</p>
-</li>
-<li>
-<p>as_double</p>
-</li>
-<li>
-<p>as_float,</p>
-</li>
-<li>
-<p>as_long</p>
-</li>
-<li>
-<p>as_short</p>
-</li>
-<li>
-<p>as_boolean</p>
-</li>
-<li>
-<p>as_string</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Consider the following example:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract contractDsl = Contract.make {
-	request {
-		method 'GET'
-		urlPath '/get'
-		body([
-				duck                : 123,
-				alpha               : 'abc',
-				number              : 123,
-				aBoolean            : true,
-				date                : '2017-01-01',
-				dateTime            : '2017-01-01T01:23:45',
-				time                : '01:02:34',
-				valueWithoutAMatcher: 'foo',
-				valueWithTypeMatch  : 'string',
-				key                 : [
-						'complex.key': 'foo'
-				]
-		])
-		bodyMatchers {
-			jsonPath('$.duck', byRegex("[0-9]{3}").asInteger())
-			jsonPath('$.duck', byEquality())
-			jsonPath('$.alpha', byRegex(onlyAlphaUnicode()).asString())
-			jsonPath('$.alpha', byEquality())
-			jsonPath('$.number', byRegex(number()).asInteger())
-			jsonPath('$.aBoolean', byRegex(anyBoolean()).asBooleanType())
-			jsonPath('$.date', byDate())
-			jsonPath('$.dateTime', byTimestamp())
-			jsonPath('$.time', byTime())
-			jsonPath("\$.['key'].['complex.key']", byEquality())
-		}
-		headers {
-			contentType(applicationJson())
-		}
-	}
-	response {
-		status OK()
-		body([
-				duck                 : 123,
-				alpha                : 'abc',
-				number               : 123,
-				positiveInteger      : 1234567890,
-				negativeInteger      : -1234567890,
-				positiveDecimalNumber: 123.4567890,
-				negativeDecimalNumber: -123.4567890,
-				aBoolean             : true,
-				date                 : '2017-01-01',
-				dateTime             : '2017-01-01T01:23:45',
-				time                 : "01:02:34",
-				valueWithoutAMatcher : 'foo',
-				valueWithTypeMatch   : 'string',
-				valueWithMin         : [
-						1, 2, 3
-				],
-				valueWithMax         : [
-						1, 2, 3
-				],
-				valueWithMinMax      : [
-						1, 2, 3
-				],
-				valueWithMinEmpty    : [],
-				valueWithMaxEmpty    : [],
-				key                  : [
-						'complex.key': 'foo'
-				],
-				nullValue            : null
-		])
-		bodyMatchers {
-			// asserts the jsonpath value against manual regex
-			jsonPath('$.duck', byRegex("[0-9]{3}").asInteger())
-			// asserts the jsonpath value against the provided value
-			jsonPath('$.duck', byEquality())
-			// asserts the jsonpath value against some default regex
-			jsonPath('$.alpha', byRegex(onlyAlphaUnicode()).asString())
-			jsonPath('$.alpha', byEquality())
-			jsonPath('$.number', byRegex(number()).asInteger())
-			jsonPath('$.positiveInteger', byRegex(anInteger()).asInteger())
-			jsonPath('$.negativeInteger', byRegex(anInteger()).asInteger())
-			jsonPath('$.positiveDecimalNumber', byRegex(aDouble()).asDouble())
-			jsonPath('$.negativeDecimalNumber', byRegex(aDouble()).asDouble())
-			jsonPath('$.aBoolean', byRegex(anyBoolean()).asBooleanType())
-			// asserts vs inbuilt time related regex
-			jsonPath('$.date', byDate())
-			jsonPath('$.dateTime', byTimestamp())
-			jsonPath('$.time', byTime())
-			// asserts that the resulting type is the same as in response body
-			jsonPath('$.valueWithTypeMatch', byType())
-			jsonPath('$.valueWithMin', byType {
-				// results in verification of size of array (min 1)
-				minOccurrence(1)
-			})
-			jsonPath('$.valueWithMax', byType {
-				// results in verification of size of array (max 3)
-				maxOccurrence(3)
-			})
-			jsonPath('$.valueWithMinMax', byType {
-				// results in verification of size of array (min 1 &amp; max 3)
-				minOccurrence(1)
-				maxOccurrence(3)
-			})
-			jsonPath('$.valueWithMinEmpty', byType {
-				// results in verification of size of array (min 0)
-				minOccurrence(0)
-			})
-			jsonPath('$.valueWithMaxEmpty', byType {
-				// results in verification of size of array (max 0)
-				maxOccurrence(0)
-			})
-			// will execute a method `assertThatValueIsANumber`
-			jsonPath('$.duck', byCommand('assertThatValueIsANumber($it)'))
-			jsonPath("\$.['key'].['complex.key']", byEquality())
-			jsonPath('$.nullValue', byNull())
-		}
-		headers {
-			contentType(applicationJson())
-			header('Some-Header', $(c('someValue'), p(regex('[a-zA-Z]{9}'))))
-		}
-	}
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
-  method: GET
-  urlPath: /get/1
-  headers:
-    Content-Type: application/json
-  cookies:
-    foo: 2
-    bar: 3
-  queryParameters:
-    limit: 10
-    offset: 20
-    filter: 'email'
-    sort: name
-    search: 55
-    age: 99
-    name: John.Doe
-    email: 'bob@email.com'
-  body:
-    duck: 123
-    alpha: "abc"
-    number: 123
-    aBoolean: true
-    date: "2017-01-01"
-    dateTime: "2017-01-01T01:23:45"
-    time: "01:02:34"
-    valueWithoutAMatcher: "foo"
-    valueWithTypeMatch: "string"
-    key:
-      "complex.key": 'foo'
-    nullValue: null
-    valueWithMin:
-      - 1
-      - 2
-      - 3
-    valueWithMax:
-      - 1
-      - 2
-      - 3
-    valueWithMinMax:
-      - 1
-      - 2
-      - 3
-    valueWithMinEmpty: []
-    valueWithMaxEmpty: []
-  matchers:
-    url:
-      regex: /get/[0-9]
-      # predefined:
-      # execute a method
-      #command: 'equals($it)'
-    queryParameters:
-      - key: limit
-        type: equal_to
-        value: 20
-      - key: offset
-        type: containing
-        value: 20
-      - key: sort
-        type: equal_to
-        value: name
-      - key: search
-        type: not_matching
-        value: '^[0-9]{2}$'
-      - key: age
-        type: not_matching
-        value: '^\\w*$'
-      - key: name
-        type: matching
-        value: 'John.*'
-      - key: hello
-        type: absent
-    cookies:
-      - key: foo
-        regex: '[0-9]'
-      - key: bar
-        command: 'equals($it)'
-    headers:
-      - key: Content-Type
-        regex: "application/json.*"
-    body:
-      - path: $.duck
-        type: by_regex
-        value: "[0-9]{3}"
-      - path: $.duck
-        type: by_equality
-      - path: $.alpha
-        type: by_regex
-        predefined: only_alpha_unicode
-      - path: $.alpha
-        type: by_equality
-      - path: $.number
-        type: by_regex
-        predefined: number
-      - path: $.aBoolean
-        type: by_regex
-        predefined: any_boolean
-      - path: $.date
-        type: by_date
-      - path: $.dateTime
-        type: by_timestamp
-      - path: $.time
-        type: by_time
-      - path: "$.['key'].['complex.key']"
-        type: by_equality
-      - path: $.nullvalue
-        type: by_null
-      - path: $.valueWithMin
-        type: by_type
-        minOccurrence: 1
-      - path: $.valueWithMax
-        type: by_type
-        maxOccurrence: 3
-      - path: $.valueWithMinMax
-        type: by_type
-        minOccurrence: 1
-        maxOccurrence: 3
-response:
-  status: 200
-  cookies:
-    foo: 1
-    bar: 2
-  body:
-    duck: 123
-    alpha: "abc"
-    number: 123
-    aBoolean: true
-    date: "2017-01-01"
-    dateTime: "2017-01-01T01:23:45"
-    time: "01:02:34"
-    valueWithoutAMatcher: "foo"
-    valueWithTypeMatch: "string"
-    valueWithMin:
-      - 1
-      - 2
-      - 3
-    valueWithMax:
-      - 1
-      - 2
-      - 3
-    valueWithMinMax:
-      - 1
-      - 2
-      - 3
-    valueWithMinEmpty: []
-    valueWithMaxEmpty: []
-    key:
-      'complex.key': 'foo'
-    nulValue: null
-  matchers:
-    headers:
-      - key: Content-Type
-        regex: "application/json.*"
-    cookies:
-      - key: foo
-        regex: '[0-9]'
-      - key: bar
-        command: 'equals($it)'
-    body:
-      - path: $.duck
-        type: by_regex
-        value: "[0-9]{3}"
-      - path: $.duck
-        type: by_equality
-      - path: $.alpha
-        type: by_regex
-        predefined: only_alpha_unicode
-      - path: $.alpha
-        type: by_equality
-      - path: $.number
-        type: by_regex
-        predefined: number
-      - path: $.aBoolean
-        type: by_regex
-        predefined: any_boolean
-      - path: $.date
-        type: by_date
-      - path: $.dateTime
-        type: by_timestamp
-      - path: $.time
-        type: by_time
-      - path: $.valueWithTypeMatch
-        type: by_type
-      - path: $.valueWithMin
-        type: by_type
-        minOccurrence: 1
-      - path: $.valueWithMax
-        type: by_type
-        maxOccurrence: 3
-      - path: $.valueWithMinMax
-        type: by_type
-        minOccurrence: 1
-        maxOccurrence: 3
-      - path: $.valueWithMinEmpty
-        type: by_type
-        minOccurrence: 0
-      - path: $.valueWithMaxEmpty
-        type: by_type
-        maxOccurrence: 0
-      - path: $.duck
-        type: by_command
-        value: assertThatValueIsANumber($it)
-      - path: $.nullValue
-        type: by_null
-        value: null
-  headers:
-    Content-Type: application/json</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In the preceding example, you can see the dynamic portions of the contract in the
-<code>matchers</code> sections. For the request part, you can see that, for all fields but
-<code>valueWithoutAMatcher</code>, the values of the regular expressions that the stub should
-contain are explicitly set. For the <code>valueWithoutAMatcher</code>, the verification takes place
-in the same way as without the use of matchers. In that case, the test performs an
-equality check.</p>
-</div>
-<div class="paragraph">
-<p>For the response side in the <code>bodyMatchers</code> section, we define the dynamic parts in a
-similar manner. The only difference is that the <code>byType</code> matchers are also present. The
-verifier engine checks four fields to verify whether the response from the test
-has a value for which the JSON path matches the given field, is of the same type as the one
-defined in the response body, and passes the following check (based on the method being called):</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>For <code>$.valueWithTypeMatch</code>, the engine checks whether the type is the same.</p>
-</li>
-<li>
-<p>For <code>$.valueWithMin</code>, the engine check the type and asserts whether the size is greater
-than or equal to the minimum occurrence.</p>
-</li>
-<li>
-<p>For <code>$.valueWithMax</code>, the engine checks the type and asserts whether the size is
-smaller than or equal to the maximum occurrence.</p>
-</li>
-<li>
-<p>For <code>$.valueWithMinMax</code>, the engine checks the type and asserts whether the size is
-between the min and maximum occurrence.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>The resulting test would resemble the following example (note that an <code>and</code> section
-separates the autogenerated assertions and the assertion from matchers):</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">// given:
- MockMvcRequestSpecification request = given()
-   .header("Content-Type", "application/json")
-   .body("{\"duck\":123,\"alpha\":\"abc\",\"number\":123,\"aBoolean\":true,\"date\":\"2017-01-01\",\"dateTime\":\"2017-01-01T01:23:45\",\"time\":\"01:02:34\",\"valueWithoutAMatcher\":\"foo\",\"valueWithTypeMatch\":\"string\",\"key\":{\"complex.key\":\"foo\"}}");
-
-// when:
- ResponseOptions response = given().spec(request)
-   .get("/get");
-
-// then:
- assertThat(response.statusCode()).isEqualTo(200);
- assertThat(response.header("Content-Type")).matches("application/json.*");
-// and:
- DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
- assertThatJson(parsedJson).field("['valueWithoutAMatcher']").isEqualTo("foo");
-// and:
- assertThat(parsedJson.read("$.duck", String.class)).matches("[0-9]{3}");
- assertThat(parsedJson.read("$.duck", Integer.class)).isEqualTo(123);
- assertThat(parsedJson.read("$.alpha", String.class)).matches("[\\p{L}]*");
- assertThat(parsedJson.read("$.alpha", String.class)).isEqualTo("abc");
- assertThat(parsedJson.read("$.number", String.class)).matches("-?(\\d*\\.\\d+|\\d+)");
- assertThat(parsedJson.read("$.aBoolean", String.class)).matches("(true|false)");
- assertThat(parsedJson.read("$.date", String.class)).matches("(\\d\\d\\d\\d)-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])");
- assertThat(parsedJson.read("$.dateTime", String.class)).matches("([0-9]{4})-(1[0-2]|0[1-9])-(3[01]|0[1-9]|[12][0-9])T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])");
- assertThat(parsedJson.read("$.time", String.class)).matches("(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])");
- assertThat((Object) parsedJson.read("$.valueWithTypeMatch")).isInstanceOf(java.lang.String.class);
- assertThat((Object) parsedJson.read("$.valueWithMin")).isInstanceOf(java.util.List.class);
- assertThat((java.lang.Iterable) parsedJson.read("$.valueWithMin", java.util.Collection.class)).as("$.valueWithMin").hasSizeGreaterThanOrEqualTo(1);
- assertThat((Object) parsedJson.read("$.valueWithMax")).isInstanceOf(java.util.List.class);
- assertThat((java.lang.Iterable) parsedJson.read("$.valueWithMax", java.util.Collection.class)).as("$.valueWithMax").hasSizeLessThanOrEqualTo(3);
- assertThat((Object) parsedJson.read("$.valueWithMinMax")).isInstanceOf(java.util.List.class);
- assertThat((java.lang.Iterable) parsedJson.read("$.valueWithMinMax", java.util.Collection.class)).as("$.valueWithMinMax").hasSizeBetween(1, 3);
- assertThat((Object) parsedJson.read("$.valueWithMinEmpty")).isInstanceOf(java.util.List.class);
- assertThat((java.lang.Iterable) parsedJson.read("$.valueWithMinEmpty", java.util.Collection.class)).as("$.valueWithMinEmpty").hasSizeGreaterThanOrEqualTo(0);
- assertThat((Object) parsedJson.read("$.valueWithMaxEmpty")).isInstanceOf(java.util.List.class);
- assertThat((java.lang.Iterable) parsedJson.read("$.valueWithMaxEmpty", java.util.Collection.class)).as("$.valueWithMaxEmpty").hasSizeLessThanOrEqualTo(0);
- assertThatValueIsANumber(parsedJson.read("$.duck"));
- assertThat(parsedJson.read("$.['key'].['complex.key']", String.class)).isEqualTo("foo");</code></pre>
-</div>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-Notice that, for the <code>byCommand</code> method, the example calls the
-<code>assertThatValueIsANumber</code>. This method must be defined in the test base class or be
-statically imported to your tests. Notice that the <code>byCommand</code> call was converted to
-<code>assertThatValueIsANumber(parsedJson.read("$.duck"));</code>. That means that the engine took
-the method name and passed the proper JSON path as a parameter to it.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>The resulting WireMock stub is in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">					'''
-{
-  "request" : {
-    "urlPath" : "/get",
-    "method" : "POST",
-    "headers" : {
-      "Content-Type" : {
-        "matches" : "application/json.*"
-      }
-    },
-    "bodyPatterns" : [ {
-      "matchesJsonPath" : "$.['list'].['some'].['nested'][?(@.['anothervalue'] == 4)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.['valueWithoutAMatcher'] == 'foo')]"
-    }, {
-      "matchesJsonPath" : "$[?(@.['valueWithTypeMatch'] == 'string')]"
-    }, {
-      "matchesJsonPath" : "$.['list'].['someother'].['nested'][?(@.['json'] == 'with value')]"
-    }, {
-      "matchesJsonPath" : "$.['list'].['someother'].['nested'][?(@.['anothervalue'] == 4)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.duck =~ /([0-9]{3})/)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.duck == 123)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.alpha =~ /([\\\\p{L}]*)/)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.alpha == 'abc')]"
-    }, {
-      "matchesJsonPath" : "$[?(@.number =~ /(-?(\\\\d*\\\\.\\\\d+|\\\\d+))/)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.aBoolean =~ /((true|false))/)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.date =~ /((\\\\d\\\\d\\\\d\\\\d)-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01]))/)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.dateTime =~ /(([0-9]{4})-(1[0-2]|0[1-9])-(3[01]|0[1-9]|[12][0-9])T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9]))/)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.time =~ /((2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9]))/)]"
-    }, {
-      "matchesJsonPath" : "$.list.some.nested[?(@.json =~ /(.*)/)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.valueWithMin.size() &gt;= 1)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.valueWithMax.size() &lt;= 3)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.valueWithMinMax.size() &gt;= 1 &amp;&amp; @.valueWithMinMax.size() &lt;= 3)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.valueWithOccurrence.size() &gt;= 4 &amp;&amp; @.valueWithOccurrence.size() &lt;= 4)]"
-    } ]
-  },
-  "response" : {
-    "status" : 200,
-    "body" : "{\\"date\\":\\"2017-01-01\\",\\"dateTime\\":\\"2017-01-01T01:23:45\\",\\"aBoolean\\":true,\\"valueWithMax\\":[1,2,3],\\"valueWithOccurrence\\":[1,2,3,4],\\"number\\":123,\\"duck\\":123,\\"alpha\\":\\"abc\\",\\"valueWithMin\\":[1,2,3],\\"time\\":\\"01:02:34\\",\\"valueWithTypeMatch\\":\\"string\\",\\"valueWithMinMax\\":[1,2,3],\\"valueWithoutAMatcher\\":\\"foo\\"}",
-    "headers" : {
-      "Content-Type" : "application/json"
-    },
-    "transformers" : [ "response-template" ]
-  }
-}
-'''</code></pre>
-</div>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-If you use a <code>matcher</code>, then the part of the request and response that the
-<code>matcher</code> addresses with the JSON Path gets removed from the assertion. In the case of
-verifying a collection, you must create matchers for <strong>all</strong> the elements of the
-collection.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>Consider the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
-    request {
-        method 'GET'
-        url("/foo")
-    }
-    response {
-        status OK()
-        body(events: [[
-                                 operation          : 'EXPORT',
-                                 eventId            : '16f1ed75-0bcc-4f0d-a04d-3121798faf99',
-                                 status             : 'OK'
-                         ], [
-                                 operation          : 'INPUT_PROCESSING',
-                                 eventId            : '3bb4ac82-6652-462f-b6d1-75e424a0024a',
-                                 status             : 'OK'
-                         ]
-                ]
-        )
-        bodyMatchers {
-            jsonPath('$.events[0].operation', byRegex('.+'))
-            jsonPath('$.events[0].eventId', byRegex('^([a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12})$'))
-            jsonPath('$.events[0].status', byRegex('.+'))
-        }
-    }
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The preceding code leads to creating the following test (the code block shows only the assertion section):</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">and:
-	DocumentContext parsedJson = JsonPath.parse(response.body.asString())
-	assertThatJson(parsedJson).array("['events']").contains("['eventId']").isEqualTo("16f1ed75-0bcc-4f0d-a04d-3121798faf99")
-	assertThatJson(parsedJson).array("['events']").contains("['operation']").isEqualTo("EXPORT")
-	assertThatJson(parsedJson).array("['events']").contains("['operation']").isEqualTo("INPUT_PROCESSING")
-	assertThatJson(parsedJson).array("['events']").contains("['eventId']").isEqualTo("3bb4ac82-6652-462f-b6d1-75e424a0024a")
-	assertThatJson(parsedJson).array("['events']").contains("['status']").isEqualTo("OK")
-and:
-	assertThat(parsedJson.read("\$.events[0].operation", String.class)).matches(".+")
-	assertThat(parsedJson.read("\$.events[0].eventId", String.class)).matches("^([a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12})\$")
-	assertThat(parsedJson.read("\$.events[0].status", String.class)).matches(".+")</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>As you can see, the assertion is malformed. Only the first element of the array got
-asserted. In order to fix this, you should apply the assertion to the whole <code>$.events</code>
-collection and assert it with the <code>byCommand(&#8230;&#8203;)</code> method.</p>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_jax_rs_support"><a class="link" href="#_jax_rs_support">8.6. JAX-RS Support</a></h3>
-<div class="paragraph">
-<p>The Spring Cloud Contract Verifier supports the JAX-RS 2 Client API. The base class needs
-to define <code>protected WebTarget webTarget</code> and server initialization. The only option for
-testing JAX-RS API is to start a web server. Also, a request with a body needs to have a
-content type set. Otherwise, the default of <code>application/octet-stream</code> gets used.</p>
-</div>
-<div class="paragraph">
-<p>In order to use JAX-RS mode, use the following settings:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">testMode == 'JAXRSCLIENT'</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following example shows a generated test API:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">					"""\
-package com.example;
-
-import com.jayway.jsonpath.DocumentContext;
-import com.jayway.jsonpath.JsonPath;
-import org.junit.Test;
-import org.junit.Rule;
-import javax.ws.rs.client.Entity;
-import javax.ws.rs.core.Response;
-
-import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat;
-import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*;
-import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson;
-import static javax.ws.rs.client.Entity.*;
-
-@SuppressWarnings("rawtypes")
-public class FooTest {
-\tWebTarget webTarget;
-
-\t@Test
-\tpublic void validate_() throws Exception {
-
-\t\t// when:
-\t\t\tResponse response = webTarget
-\t\t\t\t\t\t\t.path("/users")
-\t\t\t\t\t\t\t.queryParam("limit", "10")
-\t\t\t\t\t\t\t.queryParam("offset", "20")
-\t\t\t\t\t\t\t.queryParam("filter", "email")
-\t\t\t\t\t\t\t.queryParam("sort", "name")
-\t\t\t\t\t\t\t.queryParam("search", "55")
-\t\t\t\t\t\t\t.queryParam("age", "99")
-\t\t\t\t\t\t\t.queryParam("name", "Denis.Stepanov")
-\t\t\t\t\t\t\t.queryParam("email", "bob@email.com")
-\t\t\t\t\t\t\t.request()
-\t\t\t\t\t\t\t.build("GET")
-\t\t\t\t\t\t\t.invoke();
-\t\t\tString responseAsString = response.readEntity(String.class);
-
-\t\t// then:
-\t\t\tassertThat(response.getStatus()).isEqualTo(200);
-
-\t\t// and:
-\t\t\tDocumentContext parsedJson = JsonPath.parse(responseAsString);
-\t\t\tassertThatJson(parsedJson).field("['property1']").isEqualTo("a");
-\t}
-
-}
-
-"""</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_async_support"><a class="link" href="#_async_support">8.7. Async Support</a></h3>
-<div class="paragraph">
-<p>If you&#8217;re using asynchronous communication on the server side (your controllers are
-returning <code>Callable</code>, <code>DeferredResult</code>, and so on), then, inside your contract, you must
-provide an <code>async()</code> method in the <code>response</code> section. The following code shows an example:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-    request {
-        method GET()
-        url '/get'
-    }
-    response {
-        status OK()
-        body 'Passed'
-        async()
-    }
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">response:
-    async: true</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You can also use the <code>fixedDelayMilliseconds</code> method / property to add delay to your stubs.</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-    request {
-        method GET()
-        url '/get'
-    }
-    response {
-        status 200
-        body 'Passed'
-        fixedDelayMilliseconds 1000
-    }
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">response:
-    fixedDelayMilliseconds: 1000</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_working_with_context_paths"><a class="link" href="#_working_with_context_paths">8.8. Working with Context Paths</a></h3>
-<div class="paragraph">
-<p>Spring Cloud Contract supports context paths.</p>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-The only change needed to fully support context paths is the switch on the
-<strong>PRODUCER</strong> side. Also, the autogenerated tests must use <strong>EXPLICIT</strong> mode. The  consumer
-side remains untouched. In order for the generated test to pass, you must use <strong>EXPLICIT</strong>
-mode.
-</td>
-</tr>
-</table>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-    &lt;extensions&gt;true&lt;/extensions&gt;
-    &lt;configuration&gt;
-        &lt;testMode&gt;EXPLICIT&lt;/testMode&gt;
-    &lt;/configuration&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
-		testMode = 'EXPLICIT'
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>That way, you generate a test that <strong>DOES NOT</strong> use MockMvc. It means that you generate
-real requests and you need to setup your generated test&#8217;s base class to work on a real
-socket.</p>
-</div>
-<div class="paragraph">
-<p>Consider the following contract:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
-	request {
-		method 'GET'
-		url '/my-context-path/url'
-	}
-	response {
-		status OK()
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following example shows how to set up a base class and Rest Assured:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">import io.restassured.RestAssured;
-import org.junit.Before;
-import org.springframework.boot.web.server.LocalServerPort;
-import org.springframework.boot.test.context.SpringBootTest;
-
-@SpringBootTest(classes = ContextPathTestingBaseClass.class, webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
-class ContextPathTestingBaseClass {
-
-	@LocalServerPort int port;
-
-	@Before
-	public void setup() {
-		RestAssured.baseURI = "http://localhost";
-		RestAssured.port = this.port;
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>If you do it this way:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>All of your requests in the autogenerated tests are sent to the real endpoint with your
-context path included (for example, <code>/my-context-path/url</code>).</p>
-</li>
-<li>
-<p>Your contracts reflect that you have a context path. Your generated stubs also have
-that information (for example, in the stubs, you have to call <code>/my-context-path/url</code>).</p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_working_with_webflux"><a class="link" href="#_working_with_webflux">8.9. Working with WebFlux</a></h3>
-<div class="paragraph">
-<p>Spring Cloud Contract offers two ways of working with WebFlux.</p>
-</div>
-<div class="sect3">
-<h4 id="_webflux_with_webtestclient"><a class="link" href="#_webflux_with_webtestclient">8.9.1. WebFlux with WebTestClient</a></h4>
-<div class="paragraph">
-<p>One of them is via the <code>WebTestClient</code> mode.</p>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-    &lt;extensions&gt;true&lt;/extensions&gt;
-    &lt;configuration&gt;
-        &lt;testMode&gt;WEBTESTCLIENT&lt;/testMode&gt;
-    &lt;/configuration&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
-		testMode = 'WEBTESTCLIENT'
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following example shows how to set up a <code>WebTestClient</code> base class and <code>RestAssured</code>
-for WebFlux:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">import io.restassured.module.webtestclient.RestAssuredWebTestClient;
-import org.junit.Before;
-
-public abstract class BeerRestBase {
-
-	@Before
-	public void setup() {
-		RestAssuredWebTestClient.standaloneSetup(
-		new ProducerController(personToCheck -&gt; personToCheck.age &gt;= 20));
-	}
-}
-}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_webflux_with_explicit_mode"><a class="link" href="#_webflux_with_explicit_mode">8.9.2. WebFlux with Explicit mode</a></h4>
-<div class="paragraph">
-<p>Another way is with the <code>EXPLICIT</code> mode in your generated tests
-to work with WebFlux.</p>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-    &lt;extensions&gt;true&lt;/extensions&gt;
-    &lt;configuration&gt;
-        &lt;testMode&gt;EXPLICIT&lt;/testMode&gt;
-    &lt;/configuration&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
-		testMode = 'EXPLICIT'
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The following example shows how to set up a base class and Rest Assured for Web Flux:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@RunWith(SpringRunner.class)
-@SpringBootTest(classes = BeerRestBase.Config.class,
-		webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT,
-		properties = "server.port=0")
-public abstract class BeerRestBase {
-
-    // your tests go here
-
-    // in this config class you define all controllers and mocked services
-@Configuration
-@EnableAutoConfiguration
-static class Config {
-
-	@Bean
-	PersonCheckingService personCheckingService()  {
-		return personToCheck -&gt; personToCheck.age &gt;= 20;
-	}
-
-	@Bean
-	ProducerController producerController() {
-		return new ProducerController(personCheckingService());
-	}
-}
-
-}</code></pre>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_xml_support_for_rest"><a class="link" href="#_xml_support_for_rest">8.10. XML Support for REST</a></h3>
-<div class="paragraph">
-<p>For REST contracts, we also support XML request and response body.
-The XML body has to be passed within the <code>body</code> element
-as a <code>String</code> or <code>GString</code>. Also body matchers can be provided for
-both request and response. In place of the <code>jsonPath(&#8230;&#8203;)</code> method, the <code>org.springframework.cloud.contract.spec.internal.BodyMatchers.xPath</code>
-method should be used, with the desired <code>xPath</code> provided as the first argument
-and the appropriate <code>MatchingType</code> as second. All the body matchers apart from <code>byType()</code> are supported.</p>
-</div>
-<div class="paragraph">
-<p>Here is an example of a Groovy DSL contract with XML response body:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">					Contract.make {
-						request {
-							method GET()
-							urlPath '/get'
-							headers {
-								contentType(applicationXml())
-							}
-						}
-						response {
-							status(OK())
-							headers {
-								contentType(applicationXml())
-							}
-							body """
-&lt;test&gt;
-&lt;duck type='xtype'&gt;123&lt;/duck&gt;
-&lt;alpha&gt;abc&lt;/alpha&gt;
-&lt;list&gt;
-&lt;elem&gt;abc&lt;/elem&gt;
-&lt;elem&gt;def&lt;/elem&gt;
-&lt;elem&gt;ghi&lt;/elem&gt;
-&lt;/list&gt;
-&lt;number&gt;123&lt;/number&gt;
-&lt;aBoolean&gt;true&lt;/aBoolean&gt;
-&lt;date&gt;2017-01-01&lt;/date&gt;
-&lt;dateTime&gt;2017-01-01T01:23:45&lt;/dateTime&gt;
-&lt;time&gt;01:02:34&lt;/time&gt;
-&lt;valueWithoutAMatcher&gt;foo&lt;/valueWithoutAMatcher&gt;
-&lt;key&gt;&lt;complex&gt;foo&lt;/complex&gt;&lt;/key&gt;
-&lt;/test&gt;"""
-							bodyMatchers {
-								xPath('/test/duck/text()', byRegex("[0-9]{3}"))
-								xPath('/test/duck/text()', byCommand('equals($it)'))
-								xPath('/test/duck/xxx', byNull())
-								xPath('/test/duck/text()', byEquality())
-								xPath('/test/alpha/text()', byRegex(onlyAlphaUnicode()))
-								xPath('/test/alpha/text()', byEquality())
-								xPath('/test/number/text()', byRegex(number()))
-								xPath('/test/date/text()', byDate())
-								xPath('/test/dateTime/text()', byTimestamp())
-								xPath('/test/time/text()', byTime())
-								xPath('/test/*/complex/text()', byEquality())
-								xPath('/test/duck/@type', byEquality())
-							}
-						}
-					}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>And below is an example of a YAML contract with XML request and response bodies:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">include::{verifier_core_path}/src/test/resources/yml/contract_rest_xml.yml</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Here is an example of an automatically generated test for XML response body:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Test
-public void validate_xmlMatches() throws Exception {
-	// given:
-	MockMvcRequestSpecification request = given()
-				.header("Content-Type", "application/xml");
-
-	// when:
-	ResponseOptions response = given().spec(request).get("/get");
-
-	// then:
-	assertThat(response.statusCode()).isEqualTo(200);
-	// and:
-	DocumentBuilder documentBuilder = DocumentBuilderFactory.newInstance()
-					.newDocumentBuilder();
-	Document parsedXml = documentBuilder.parse(new InputSource(
-				new StringReader(response.getBody().asString())));
-	// and:
-	assertThat(valueFromXPath(parsedXml, "/test/list/elem/text()")).isEqualTo("abc");
-	assertThat(valueFromXPath(parsedXml,"/test/list/elem[2]/text()")).isEqualTo("def");
-	assertThat(valueFromXPath(parsedXml, "/test/duck/text()")).matches("[0-9]{3}");
-	assertThat(nodeFromXPath(parsedXml, "/test/duck/xxx")).isNull();
-	assertThat(valueFromXPath(parsedXml, "/test/alpha/text()")).matches("[\\p{L}]*");
-	assertThat(valueFromXPath(parsedXml, "/test/*/complex/text()")).isEqualTo("foo");
-	assertThat(valueFromXPath(parsedXml, "/test/duck/@type")).isEqualTo("xtype");
-	}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_messaging_top_level_elements"><a class="link" href="#_messaging_top_level_elements">8.11. Messaging Top-Level Elements</a></h3>
-<div class="paragraph">
-<p>The DSL for messaging looks a little bit different than the one that focuses on HTTP. The
-following sections explain the differences:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="#contract-dsl-output-triggered-method">Output Triggered by a Method</a></p>
-</li>
-<li>
-<p><a href="#contract-dsl-output-triggered-message">Output Triggered by a Message</a></p>
-</li>
-<li>
-<p><a href="#contract-dsl-consumer-producer">Consumer/Producer</a></p>
-</li>
-<li>
-<p><a href="#contract-dsl-common">Common</a></p>
-</li>
-</ul>
-</div>
-<div class="sect3">
-<h4 id="contract-dsl-output-triggered-method"><a class="link" href="#contract-dsl-output-triggered-method">8.11.1. Output Triggered by a Method</a></h4>
-<div class="paragraph">
-<p>The output message can be triggered by calling a method (such as a <code>Scheduler</code> when a was
-started and a message was sent), as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">def dsl = Contract.make {
-	// Human readable description
-	description 'Some description'
-	// Label by means of which the output message can be triggered
-	label 'some_label'
-	// input to the contract
-	input {
-		// the contract will be triggered by a method
-		triggeredBy('bookReturnedTriggered()')
-	}
-	// output message of the contract
-	outputMessage {
-		// destination to which the output message will be sent
-		sentTo('output')
-		// the body of the output message
-		body('''{ "bookName" : "foo" }''')
-		// the headers of the output message
-		headers {
-			header('BOOK-NAME', 'foo')
-		}
-	}
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml"># Human readable description
-description: Some description
-# Label by means of which the output message can be triggered
-label: some_label
-input:
-  # the contract will be triggered by a method
-  triggeredBy: bookReturnedTriggered()
-# output message of the contract
-outputMessage:
-  # destination to which the output message will be sent
-  sentTo: output
-  # the body of the output message
-  body:
-    bookName: foo
-  # the headers of the output message
-  headers:
-    BOOK-NAME: foo</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In the previous example case, the output message is sent to <code>output</code> if a method called
-<code>bookReturnedTriggered</code> is executed. On the message <strong>publisher&#8217;s</strong> side, we generate a
-test that calls that method to trigger the message. On the <strong>consumer</strong> side, you can use
-the <code>some_label</code> to trigger the message.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="contract-dsl-output-triggered-message"><a class="link" href="#contract-dsl-output-triggered-message">8.11.2. Output Triggered by a Message</a></h4>
-<div class="paragraph">
-<p>The output message can be triggered by receiving a message, as shown in the following
-example:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">def dsl = Contract.make {
-	description 'Some Description'
-	label 'some_label'
-	// input is a message
-	input {
-		// the message was received from this destination
-		messageFrom('input')
-		// has the following body
-		messageBody([
-				bookName: 'foo'
-		])
-		// and the following headers
-		messageHeaders {
-			header('sample', 'header')
-		}
-	}
-	outputMessage {
-		sentTo('output')
-		body([
-				bookName: 'foo'
-		])
-		headers {
-			header('BOOK-NAME', 'foo')
-		}
-	}
-}</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml"># Human readable description
-description: Some description
-# Label by means of which the output message can be triggered
-label: some_label
-# input is a message
-input:
-  messageFrom: input
-  # has the following body
-  messageBody:
-    bookName: 'foo'
-  # and the following headers
-  messageHeaders:
-    sample: 'header'
-# output message of the contract
-outputMessage:
-  # destination to which the output message will be sent
-  sentTo: output
-  # the body of the output message
-  body:
-    bookName: foo
-  # the headers of the output message
-  headers:
-    BOOK-NAME: foo</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In the preceding example, the output message is sent to <code>output</code> if a proper message is
-received on the <code>input</code> destination. On the message <strong>publisher&#8217;s</strong> side, the engine
-generates a test that sends the input message to the defined destination. On the
-<strong>consumer</strong> side, you can either send a message to the input destination or use a label
-(<code>some_label</code> in the example) to trigger the message.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="contract-dsl-consumer-producer"><a class="link" href="#contract-dsl-consumer-producer">8.11.3. Consumer/Producer</a></h4>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-This section is valid only for Groovy DSL.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>In HTTP, you have a notion of <code>client</code>/<code>stub and `server</code>/<code>test</code> notation. You can also
-use those paradigms in messaging. In addition, Spring Cloud Contract Verifier also
-provides the <code>consumer</code> and <code>producer</code> methods, as presented in the following example
-(note that you can use either <code>$</code> or <code>value</code> methods to provide <code>consumer</code> and <code>producer</code>
-parts):</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">					Contract.make {
-				name "foo"
-						label 'some_label'
-						input {
-							messageFrom value(consumer('jms:output'), producer('jms:input'))
-							messageBody([
-									bookName: 'foo'
-							])
-							messageHeaders {
-								header('sample', 'header')
-							}
-						}
-						outputMessage {
-							sentTo $(consumer('jms:input'), producer('jms:output'))
-							body([
-									bookName: 'foo'
-							])
-						}
-					}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="contract-dsl-common"><a class="link" href="#contract-dsl-common">8.11.4. Common</a></h4>
-<div class="paragraph">
-<p>In the <code>input</code> or <code>outputMessage</code> section you can call <code>assertThat</code> with the name
-of a <code>method</code> (e.g. <code>assertThatMessageIsOnTheQueue()</code>) that you have defined in the
-base class or in a static import. Spring Cloud Contract will execute that method
-in the generated test.</p>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_multiple_contracts_in_one_file"><a class="link" href="#_multiple_contracts_in_one_file">8.12. Multiple Contracts in One File</a></h3>
-<div class="paragraph">
-<p>You can define multiple contracts in one file. Such a contract might resemble the
-following example:</p>
-</div>
-<div class="listingblock">
-<div class="title">Groovy DSL</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">import org.springframework.cloud.contract.spec.Contract
-
-[
-	Contract.make {
-		name("should post a user")
-		request {
-			method 'POST'
-			url('/users/1')
-		}
-		response {
-			status OK()
-		}
-	},
-	Contract.make {
-		request {
-			method 'POST'
-			url('/users/2')
-		}
-		response {
-			status OK()
-		}
-	}
-]</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">YAML</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">---
-name: should post a user
-request:
-  method: POST
-  url: /users/1
-response:
-  status: 200
----
-request:
-  method: POST
-  url: /users/2
-response:
-  status: 200
----
-request:
-  method: POST
-  url: /users/3
-response:
-  status: 200</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In the preceding example, one contract has the <code>name</code> field and the other does not. This
-leads to generation of two tests that look more or less like this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package org.springframework.cloud.contract.verifier.tests.com.hello;
-
-import com.example.TestBase;
-import com.jayway.jsonpath.DocumentContext;
-import com.jayway.jsonpath.JsonPath;
-import com.jayway.restassured.module.mockmvc.specification.MockMvcRequestSpecification;
-import com.jayway.restassured.response.ResponseOptions;
-import org.junit.Test;
-
-import static com.jayway.restassured.module.mockmvc.RestAssuredMockMvc.*;
-import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson;
-import static org.assertj.core.api.Assertions.assertThat;
-
-public class V1Test extends TestBase {
-
-	@Test
-	public void validate_should_post_a_user() throws Exception {
-		// given:
-			MockMvcRequestSpecification request = given();
-
-		// when:
-			ResponseOptions response = given().spec(request)
-					.post("/users/1");
-
-		// then:
-			assertThat(response.statusCode()).isEqualTo(200);
-	}
-
-	@Test
-	public void validate_withList_1() throws Exception {
-		// given:
-			MockMvcRequestSpecification request = given();
-
-		// when:
-			ResponseOptions response = given().spec(request)
-					.post("/users/2");
-
-		// then:
-			assertThat(response.statusCode()).isEqualTo(200);
-	}
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Notice that, for the contract that has the <code>name</code> field, the generated test method is named
-<code>validate_should_post_a_user</code>. For the one that does not have the name, it is called
-<code>validate_withList_1</code>. It corresponds to the name of the file <code>WithList.groovy</code> and the
-index of the contract in the list.</p>
-</div>
-<div class="paragraph">
-<p>The generated stubs is shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code>should post a user.json
-1_WithList.json</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>As you can see, the first file got the <code>name</code> parameter from the contract. The second
-got the name of the contract file (<code>WithList.groovy</code>) prefixed with the index (in this
-case, the contract had an index of <code>1</code> in the list of contracts in the file).</p>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-As you can see, it is much better if you name your contracts because doing so makes
-your tests far more meaningful.
-</td>
-</tr>
-</table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_generating_spring_rest_docs_snippets_from_the_contracts"><a class="link" href="#_generating_spring_rest_docs_snippets_from_the_contracts">8.13. Generating Spring REST Docs snippets from the contracts</a></h3>
-<div class="paragraph">
-<p>When you want to include the requests and responses of your API using Spring REST Docs,
-you only need to make some minor changes to your setup if you are using MockMvc and RestAssuredMockMvc.
-Simply include the following dependencies if you haven&#8217;t already.</p>
-</div>
-<div class="listingblock">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-starter-contract-verifier&lt;/artifactId&gt;
-	&lt;scope&gt;test&lt;/scope&gt;
-&lt;/dependency&gt;
-&lt;dependency&gt;
-	&lt;groupId&gt;org.springframework.restdocs&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-restdocs-mockmvc&lt;/artifactId&gt;
-	&lt;optional&gt;true&lt;/optional&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">testCompile 'org.springframework.cloud:spring-cloud-starter-contract-verifier'
-testCompile 'org.springframework.restdocs:spring-restdocs-mockmvc'</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Next you need to make some changes to your base class like the following example.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package com.example.fraud;
-
-import io.restassured.module.mockmvc.RestAssuredMockMvc;
-import org.junit.Before;
-import org.junit.Rule;
-import org.junit.rules.TestName;
-import org.junit.runner.RunWith;
-
-import org.springframework.beans.factory.annotation.Autowired;
-import org.springframework.boot.test.context.SpringBootTest;
-import org.springframework.restdocs.JUnitRestDocumentation;
-import org.springframework.test.context.junit4.SpringRunner;
-import org.springframework.test.web.servlet.setup.MockMvcBuilders;
-import org.springframework.web.context.WebApplicationContext;
-
-import static org.springframework.restdocs.mockmvc.MockMvcRestDocumentation.document;
-import static org.springframework.restdocs.mockmvc.MockMvcRestDocumentation.documentationConfiguration;
-
-@RunWith(SpringRunner.class)
-@SpringBootTest(classes = Application.class)
-public abstract class FraudBaseWithWebAppSetup {
-
-	private static final String OUTPUT = "target/generated-snippets";
-
-	@Rule
-	public JUnitRestDocumentation restDocumentation = new JUnitRestDocumentation(OUTPUT);
-
-	@Rule
-	public TestName testName = new TestName();
-
-	@Autowired
-	private WebApplicationContext context;
-
-	@Before
-	public void setup() {
-		RestAssuredMockMvc.mockMvc(MockMvcBuilders.webAppContextSetup(this.context)
-				.apply(documentationConfiguration(this.restDocumentation))
-				.alwaysDo(document(
-						getClass().getSimpleName() + "_" + testName.getMethodName()))
-				.build());
-	}
-
-	protected void assertThatRejectionReasonIsNull(Object rejectionReason) {
-		assert rejectionReason == null;
-	}
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In case you are using the standalone setup, you can set up RestAssuredMockMvc like this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package com.example.fraud;
-
-import io.restassured.module.mockmvc.RestAssuredMockMvc;
-import org.junit.Before;
-import org.junit.Rule;
-import org.junit.rules.TestName;
-
-import org.springframework.restdocs.JUnitRestDocumentation;
-import org.springframework.test.web.servlet.setup.MockMvcBuilders;
-
-import static org.springframework.restdocs.mockmvc.MockMvcRestDocumentation.document;
-import static org.springframework.restdocs.mockmvc.MockMvcRestDocumentation.documentationConfiguration;
-
-public abstract class FraudBaseWithStandaloneSetup {
-
-	private static final String OUTPUT = "target/generated-snippets";
-
-	@Rule
-	public JUnitRestDocumentation restDocumentation = new JUnitRestDocumentation(OUTPUT);
-
-	@Rule
-	public TestName testName = new TestName();
-
-	@Before
-	public void setup() {
-		RestAssuredMockMvc.standaloneSetup(MockMvcBuilders
-				.standaloneSetup(new FraudDetectionController())
-				.apply(documentationConfiguration(this.restDocumentation))
-				.alwaysDo(document(
-						getClass().getSimpleName() + "_" + testName.getMethodName())));
-	}
-
-}</code></pre>
-</div>
-</div>
-<div class="admonitionblock tip">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
-</td>
-<td class="content">
-You don&#8217;t need to specify the output directory for the generated snippets since version 1.2.0.RELEASE of Spring REST Docs.
-</td>
-</tr>
-</table>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_customization"><a class="link" href="#_customization">9. Customization</a></h2>
-<div class="sectionbody">
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-This section is valid only for Groovy DSL
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>You can customize the Spring Cloud Contract Verifier by extending the DSL, as shown in
-the remainder of this section.</p>
-</div>
-<div class="sect2">
-<h3 id="_extending_the_dsl"><a class="link" href="#_extending_the_dsl">9.1. Extending the DSL</a></h3>
-<div class="paragraph">
-<p>You can provide your own functions to the DSL. The key requirement for this feature is to
-maintain the static compatibility. Later in this document, you can see examples of:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Creating a JAR with reusable classes.</p>
-</li>
-<li>
-<p>Referencing of these classes in the DSLs.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>You can find the full example
-<a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples">here</a>.</p>
-</div>
-<div class="sect3">
-<h4 id="_common_jar"><a class="link" href="#_common_jar">9.1.1. Common JAR</a></h4>
-<div class="paragraph">
-<p>The following examples show three classes that can be reused in the DSLs.</p>
-</div>
-<div class="paragraph">
-<p><strong>PatternUtils</strong> contains functions used by both the <strong>consumer</strong> and the <strong>producer</strong>.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package com.example;
-
-import java.util.regex.Pattern;
-
-/**
- * If you want to use {@link Pattern} directly in your tests
- * then you can create a class resembling this one. It can
- * contain all the {@link Pattern} you want to use in the DSL.
- *
- * &lt;pre&gt;
- * {@code
- * request {
- *     body(
- *         [ age: $(c(PatternUtils.oldEnough()))]
- *     )
- * }
- * &lt;/pre&gt;
- *
- * Notice that we're using both {@code $()} for dynamic values
- * and {@code c()} for the consumer side.
- *
- * @author Marcin Grzejszczak
- */
-//tag::impl[]
-public class PatternUtils {
-
-	public static String tooYoung() {
-		//remove::start[]
-		return "[0-1][0-9]";
-		//remove::end[return]
-	}
-
-	public static Pattern oldEnough() {
-		//remove::start[]
-		return Pattern.compile("[2-9][0-9]");
-		//remove::end[return]
-	}
-
-	/**
-	 * Makes little sense but it's just an example ;)
-	 */
-	public static Pattern ok() {
-		//remove::start[]
-		return Pattern.compile("OK");
-		//remove::end[return]
-	}
-}
-//end::impl[]</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><strong>ConsumerUtils</strong> contains functions used by the <strong>consumer</strong>.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package com.example;
-
-import org.springframework.cloud.contract.spec.internal.ClientDslProperty;
-
-/**
- * DSL Properties passed to the DSL from the consumer's perspective.
- * That means that on the input side {@code Request} for HTTP
- * or {@code Input} for messaging you can have a regular expression.
- * On the {@code Response} for HTTP or {@code Output} for messaging
- * you have to have a concrete value.
- *
- * @author Marcin Grzejszczak
- */
-//tag::impl[]
-public class ConsumerUtils {
-	/**
-	 * Consumer side property. By using the {@link ClientDslProperty}
-	 * you can omit most of boilerplate code from the perspective
-	 * of dynamic values. Example
-	 *
-	 * &lt;pre&gt;
-	 * {@code
-	 * request {
-	 *     body(
-	 *         [ age: $(ConsumerUtils.oldEnough())]
-	 *     )
-	 * }
-	 * &lt;/pre&gt;
-	 *
-	 * That way it's in the implementation that we decide what value we will pass to the consumer
-	 * and which one to the producer.
-	 *
-	 * @author Marcin Grzejszczak
-	 */
-	public static ClientDslProperty oldEnough() {
-		//remove::start[]
-		// this example is not the best one and
-		// theoretically you could just pass the regex instead of `ServerDslProperty` but
-		// it's just to show some new tricks :)
-		return new ClientDslProperty(PatternUtils.oldEnough(), 40);
-		//remove::end[return]
-	}
-
-}
-//end::impl[]</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p><strong>ProducerUtils</strong> contains functions used by the <strong>producer</strong>.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package com.example;
-
-import org.springframework.cloud.contract.spec.internal.ServerDslProperty;
-
-/**
- * DSL Properties passed to the DSL from the producer's perspective.
- * That means that on the input side {@code Request} for HTTP
- * or {@code Input} for messaging you have to have a concrete value.
- * On the {@code Response} for HTTP or {@code Output} for messaging
- * you can have a regular expression.
- *
- * @author Marcin Grzejszczak
- */
-//tag::impl[]
-public class ProducerUtils {
-
-	/**
-	 * Producer side property. By using the {@link ProducerUtils}
-	 * you can omit most of boilerplate code from the perspective
-	 * of dynamic values. Example
-	 *
-	 * &lt;pre&gt;
-	 * {@code
-	 * response {
-	 *     body(
-	 *         [ status: $(ProducerUtils.ok())]
-	 *     )
-	 * }
-	 * &lt;/pre&gt;
-	 *
-	 * That way it's in the implementation that we decide what value we will pass to the consumer
-	 * and which one to the producer.
-	 */
-	public static ServerDslProperty ok() {
-		// this example is not the best one and
-		// theoretically you could just pass the regex instead of `ServerDslProperty` but
-		// it's just to show some new tricks :)
-		return new ServerDslProperty( PatternUtils.ok(), "OK");
-	}
-}
-//end::impl[]</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_adding_the_dependency_to_the_project"><a class="link" href="#_adding_the_dependency_to_the_project">9.1.2. Adding the Dependency to the Project</a></h4>
-<div class="paragraph">
-<p>In order for the plugins and IDE to be able to reference the common JAR classes, you need
-to pass the dependency to your project.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_test_the_dependency_in_the_projects_dependencies"><a class="link" href="#_test_the_dependency_in_the_projects_dependencies">9.1.3. Test the Dependency in the Project&#8217;s Dependencies</a></h4>
-<div class="paragraph">
-<p>First, add the common jar dependency as a test dependency. Because your contracts files
-are available on the test resources path,  the common jar classes automatically become
-visible in your Groovy files. The following examples show how to test the dependency:</p>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
-	&lt;groupId&gt;com.example&lt;/groupId&gt;
-	&lt;artifactId&gt;beer-common&lt;/artifactId&gt;
-	&lt;version&gt;${project.version}&lt;/version&gt;
-	&lt;scope&gt;test&lt;/scope&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">testCompile("com.example:beer-common:0.0.1.BUILD-SNAPSHOT")</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_test_a_dependency_in_the_plugins_dependencies"><a class="link" href="#_test_a_dependency_in_the_plugins_dependencies">9.1.4. Test a Dependency in the Plugin&#8217;s Dependencies</a></h4>
-<div class="paragraph">
-<p>Now, you must add the dependency for the plugin to reuse at runtime, as shown in the
-following example:</p>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-	&lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-	&lt;extensions&gt;true&lt;/extensions&gt;
-	&lt;configuration&gt;
-		&lt;packageWithBaseClasses&gt;com.example&lt;/packageWithBaseClasses&gt;
-		&lt;baseClassMappings&gt;
-			&lt;baseClassMapping&gt;
-				&lt;contractPackageRegex&gt;.*intoxication.*&lt;/contractPackageRegex&gt;
-				&lt;baseClassFQN&gt;com.example.intoxication.BeerIntoxicationBase&lt;/baseClassFQN&gt;
-			&lt;/baseClassMapping&gt;
-		&lt;/baseClassMappings&gt;
-	&lt;/configuration&gt;
-	&lt;dependencies&gt;
-		&lt;dependency&gt;
-			&lt;groupId&gt;com.example&lt;/groupId&gt;
-			&lt;artifactId&gt;beer-common&lt;/artifactId&gt;
-			&lt;version&gt;${project.version}&lt;/version&gt;
-			&lt;scope&gt;compile&lt;/scope&gt;
-		&lt;/dependency&gt;
-	&lt;/dependencies&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">classpath "com.example:beer-common:0.0.1.BUILD-SNAPSHOT"</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_referencing_classes_in_dsls"><a class="link" href="#_referencing_classes_in_dsls">9.1.5. Referencing classes in DSLs</a></h4>
-<div class="paragraph">
-<p>You can now reference your classes in your DSL, as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package contracts.beer.rest
-
-import com.example.ConsumerUtils
-import com.example.ProducerUtils
-import org.springframework.cloud.contract.spec.Contract
-
-Contract.make {
-	description("""
-Represents a successful scenario of getting a beer
-
-```
-given:
-	client is old enough
-when:
-	he applies for a beer
-then:
-	we'll grant him the beer
-```
-
-""")
-	request {
-		method 'POST'
-		url '/check'
-		body(
-				age: $(ConsumerUtils.oldEnough())
-		)
-		headers {
-			contentType(applicationJson())
-		}
-	}
-	response {
-		status 200
-		body("""
-			{
-				"status": "${value(ProducerUtils.ok())}"
-			}
-			""")
-		headers {
-			contentType(applicationJson())
-		}
-	}
-}</code></pre>
-</div>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-You can set the Spring Cloud Contract plugin up by setting <code>convertToYaml</code> to <code>true</code>. That way you will NOT have to add the dependency with the extended functionality to the consumer side, since the consumer side will be using YAML contracts instead of Groovy ones.
-</td>
-</tr>
-</table>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_using_the_pluggable_architecture"><a class="link" href="#_using_the_pluggable_architecture">10. Using the Pluggable Architecture</a></h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>You may encounter cases where you have your contracts have been defined in other formats,
-such as YAML, RAML or PACT. In those cases, you still want to benefit from the automatic
-generation of tests and stubs. You can add your own implementation for generating both
-tests and stubs. Also, you can customize the way tests are generated (for example, you
-can generate tests for other languages) and the way stubs are generated (for example, you
-can generate stubs for other HTTP server implementations).</p>
-</div>
-<div class="sect2">
-<h3 id="_custom_contract_converter"><a class="link" href="#_custom_contract_converter">10.1. Custom Contract Converter</a></h3>
-<div class="paragraph">
-<p>The <code>ContractConverter</code> interface lets you register your own implementation of a contract
-structure converter. The following code listing shows the <code>ContractConverter</code> interface:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package org.springframework.cloud.contract.spec;
-
-import java.io.File;
-import java.util.Collection;
-
-/**
- * Converter to be used to convert FROM {@link File} TO {@link Contract} and from
- * {@link Contract} to {@code T}.
- *
- * @param &lt;T&gt; - type to which we want to convert the contract
- * @author Marcin Grzejszczak
- * @since 1.1.0
- */
-public interface ContractConverter&lt;T&gt; extends ContractStorer&lt;T&gt; {
-
-	/**
-	 * Should this file be accepted by the converter. Can use the file extension to check
-	 * if the conversion is possible.
-	 * @param file - file to be considered for conversion
-	 * @return - {@code true} if the given implementation can convert the file
-	 */
-	boolean isAccepted(File file);
-
-	/**
-	 * Converts the given {@link File} to its {@link Contract} representation.
-	 * @param file - file to convert
-	 * @return - {@link Contract} representation of the file
-	 */
-	Collection&lt;Contract&gt; convertFrom(File file);
-
-	/**
-	 * Converts the given {@link Contract} to a {@link T} representation.
-	 * @param contract - the parsed contract
-	 * @return - {@link T} the type to which we do the conversion
-	 */
-	T convertTo(Collection&lt;Contract&gt; contract);
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Your implementation must define the condition on which it should start the
-conversion. Also, you must define how to perform that conversion in both directions.</p>
-</div>
-<div class="admonitionblock important">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
-</td>
-<td class="content">
-Once you create your implementation, you must create a
-<code>/META-INF/spring.factories</code> file in which you provide the fully qualified name of your
-implementation.
-</td>
-</tr>
-</table>
-</div>
-<div class="paragraph">
-<p>The following example shows a typical <code>spring.factories</code> file:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code>org.springframework.cloud.contract.spec.ContractConverter=\
-org.springframework.cloud.contract.verifier.converter.YamlContractConverter</code></pre>
-</div>
-</div>
-<div class="sect3">
-<h4 id="pact-converter"><a class="link" href="#pact-converter">10.1.1. Pact Converter</a></h4>
-<div class="paragraph">
-<p>Spring Cloud Contract includes support for <a href="https://docs.pact.io/">Pact</a> representation of
-contracts up until v4. Instead of using the Groovy DSL, you can use Pact files. In this section, we
-present how to add Pact support for your project. Note however that not all functionality is supported.
-Starting with v3 you can combine multiple matcher for the same element;
-you can use matchers for the body, headers, request and path; and you can use value generators.
-Spring Cloud Contract currently only supports multiple matchers that are combined using the AND rule logic.
-Next to that the request and path matchers are skipped during the conversion.
-When using a date, time or datetime value generator with a given format,
-the given format will be skipped and the ISO format will be used.</p>
-</div>
-<div class="paragraph">
-<p>In order to properly support the Spring Cloud Contract way of doing messaging
-with Pact you&#8217;ll have to provide some additional meta data entries. Below you can find a list of such entries:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>to define the destination to which a message gets sent, you have to
-set a <code>metaData</code> entry in the Pact file, with key <code>sentTo</code> equal to the destination to which a message is to be sent. E.g. <code>"metaData": { "sentTo": "activemq:output" }</code></p>
-</li>
-</ul>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_pact_contract"><a class="link" href="#_pact_contract">10.1.2. Pact Contract</a></h4>
-<div class="paragraph">
-<p>Consider following example of a Pact contract, which is a file under the
-<code>src/test/resources/contracts</code> folder.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-javascript hljs" data-lang="javascript">{
-  "provider": {
-    "name": "Provider"
-  },
-  "consumer": {
-    "name": "Consumer"
-  },
-  "interactions": [
-    {
-      "description": "",
-      "request": {
-        "method": "PUT",
-        "path": "/fraudcheck",
-        "headers": {
-          "Content-Type": "application/vnd.fraud.v1+json"
-        },
-        "body": {
-          "clientId": "1234567890",
-          "loanAmount": 99999
-        },
-        "generators": {
-          "body": {
-            "$.clientId": {
-              "type": "Regex",
-              "regex": "[0-9]{10}"
-            }
-          }
-        },
-        "matchingRules": {
-          "header": {
-            "Content-Type": {
-              "matchers": [
-                {
-                  "match": "regex",
-                  "regex": "application/vnd\\.fraud\\.v1\\+json.*"
-                }
-              ],
-              "combine": "AND"
-            }
-          },
-          "body": {
-            "$.clientId": {
-              "matchers": [
-                {
-                  "match": "regex",
-                  "regex": "[0-9]{10}"
-                }
-              ],
-              "combine": "AND"
-            }
-          }
-        }
-      },
-      "response": {
-        "status": 200,
-        "headers": {
-          "Content-Type": "application/vnd.fraud.v1+json"
-        },
-        "body": {
-          "fraudCheckStatus": "FRAUD",
-          "rejectionReason": "Amount too high"
-        },
-        "matchingRules": {
-          "header": {
-            "Content-Type": {
-              "matchers": [
-                {
-                  "match": "regex",
-                  "regex": "application/vnd\\.fraud\\.v1\\+json.*"
-                }
-              ],
-              "combine": "AND"
-            }
-          },
-          "body": {
-            "$.fraudCheckStatus": {
-              "matchers": [
-                {
-                  "match": "regex",
-                  "regex": "FRAUD"
-                }
-              ],
-              "combine": "AND"
-            }
-          }
-        }
-      }
-    }
-  ],
-  "metadata": {
-    "pact-specification": {
-      "version": "3.0.0"
-    },
-    "pact-jvm": {
-      "version": "3.5.13"
-    }
-  }
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The remainder of this section about using Pact refers to the preceding file.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_pact_for_producers"><a class="link" href="#_pact_for_producers">10.1.3. Pact for Producers</a></h4>
-<div class="paragraph">
-<p>On the producer side, you must add two additional dependencies to your plugin
-configuration. One is the Spring Cloud Contract Pact support, and the other represents
-the current Pact version that you use.</p>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
-	&lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-	&lt;extensions&gt;true&lt;/extensions&gt;
-	&lt;configuration&gt;
-		&lt;packageWithBaseClasses&gt;com.example.fraud&lt;/packageWithBaseClasses&gt;
-	&lt;/configuration&gt;
-	&lt;dependencies&gt;
-		&lt;dependency&gt;
-			&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-			&lt;artifactId&gt;spring-cloud-contract-pact&lt;/artifactId&gt;
-			&lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
-		&lt;/dependency&gt;
-	&lt;/dependencies&gt;
-&lt;/plugin&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">classpath "org.springframework.cloud:spring-cloud-contract-pact:${findProperty('verifierVersion') ?: verifierVersion}"</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>When you execute the build of your application, a test will be generated. The generated
-test might be as follows:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Test
-public void validate_shouldMarkClientAsFraud() throws Exception {
-	// given:
-		MockMvcRequestSpecification request = given()
-				.header("Content-Type", "application/vnd.fraud.v1+json")
-				.body("{\"clientId\":\"1234567890\",\"loanAmount\":99999}");
-
-	// when:
-		ResponseOptions response = given().spec(request)
-				.put("/fraudcheck");
-
-	// then:
-		assertThat(response.statusCode()).isEqualTo(200);
-		assertThat(response.header("Content-Type")).matches("application/vnd\\.fraud\\.v1\\+json.*");
-	// and:
-		DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
-		assertThatJson(parsedJson).field("['rejectionReason']").isEqualTo("Amount too high");
-	// and:
-		assertThat(parsedJson.read("$.fraudCheckStatus", String.class)).matches("FRAUD");
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The corresponding generated stub might be as follows:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-javascript hljs" data-lang="javascript">{
-  "id" : "996ae5ae-6834-4db6-8fac-358ca187ab62",
-  "uuid" : "996ae5ae-6834-4db6-8fac-358ca187ab62",
-  "request" : {
-    "url" : "/fraudcheck",
-    "method" : "PUT",
-    "headers" : {
-      "Content-Type" : {
-        "matches" : "application/vnd\\.fraud\\.v1\\+json.*"
-      }
-    },
-    "bodyPatterns" : [ {
-      "matchesJsonPath" : "$[?(@.['loanAmount'] == 99999)]"
-    }, {
-      "matchesJsonPath" : "$[?(@.clientId =~ /([0-9]{10})/)]"
-    } ]
-  },
-  "response" : {
-    "status" : 200,
-    "body" : "{\"fraudCheckStatus\":\"FRAUD\",\"rejectionReason\":\"Amount too high\"}",
-    "headers" : {
-      "Content-Type" : "application/vnd.fraud.v1+json;charset=UTF-8"
-    },
-    "transformers" : [ "response-template" ]
-  },
-}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_pact_for_consumers"><a class="link" href="#_pact_for_consumers">10.1.4. Pact for Consumers</a></h4>
-<div class="paragraph">
-<p>On the producer side, you must add two additional dependencies to your project
-dependencies. One is the Spring Cloud Contract Pact support, and the other represents the
-current Pact version that you use.</p>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
-	&lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
-	&lt;artifactId&gt;spring-cloud-contract-pact&lt;/artifactId&gt;
-	&lt;scope&gt;test&lt;/scope&gt;
-&lt;/dependency&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">testCompile "org.springframework.cloud:spring-cloud-contract-pact"</code></pre>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_using_the_custom_test_generator"><a class="link" href="#_using_the_custom_test_generator">10.2. Using the Custom Test Generator</a></h3>
-<div class="paragraph">
-<p>If you want to generate tests for languages other than Java or you are not happy with the
-way the verifier builds Java tests, you can register your own implementation.</p>
-</div>
-<div class="paragraph">
-<p>The <code>SingleTestGenerator</code> interface lets you register your own implementation.  The
-following code listing shows the <code>SingleTestGenerator</code> interface:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package org.springframework.cloud.contract.verifier.builder;
-
-import java.nio.file.Path;
-import java.util.Collection;
-
-import org.springframework.cloud.contract.verifier.config.ContractVerifierConfigProperties;
-import org.springframework.cloud.contract.verifier.file.ContractMetadata;
-
-/**
- * Builds a single test.
- *
- * @since 1.1.0
- */
-public interface SingleTestGenerator {
-
-	/**
-	 * Creates contents of a single test class in which all test scenarios from the
-	 * contract metadata should be placed.
-	 * @param properties - properties passed to the plugin
-	 * @param listOfFiles - list of parsed contracts with additional metadata
-	 * @param className - the name of the generated test class
-	 * @param classPackage - the name of the package in which the test class should be
-	 * stored
-	 * @param includedDirectoryRelativePath - relative path to the included directory
-	 * @return contents of a single test class
-	 * @deprecated use{@link SingleTestGenerator#buildClass(ContractVerifierConfigProperties, Collection, String, GeneratedClassData)}
-	 */
-	@Deprecated
-	String buildClass(ContractVerifierConfigProperties properties,
-			Collection&lt;ContractMetadata&gt; listOfFiles, String className,
-			String classPackage, String includedDirectoryRelativePath);
-
-	/**
-	 * Creates contents of a single test class in which all test scenarios from the
-	 * contract metadata should be placed.
-	 * @param properties - properties passed to the plugin
-	 * @param listOfFiles - list of parsed contracts with additional metadata
-	 * @param generatedClassData - information about the generated class
-	 * @param includedDirectoryRelativePath - relative path to the included directory
-	 * @return contents of a single test class
-	 */
-	default String buildClass(ContractVerifierConfigProperties properties,
-			Collection&lt;ContractMetadata&gt; listOfFiles,
-			String includedDirectoryRelativePath, GeneratedClassData generatedClassData) {
-		String className = generatedClassData.className;
-		String classPackage = generatedClassData.classPackage;
-		String path = includedDirectoryRelativePath;
-		return buildClass(properties, listOfFiles, className, classPackage, path);
-	}
-
-	/**
-	 * Extension that should be appended to the generated test class. E.g. {@code .java}
-	 * or {@code .php}
-	 * @param properties - properties passed to the plugin
-	 */
-	String fileExtension(ContractVerifierConfigProperties properties);
-
-	class GeneratedClassData {
-
-		public final String className;
-
-		public final String classPackage;
-
-		public final Path testClassPath;
-
-		public GeneratedClassData(String className, String classPackage,
-				Path testClassPath) {
-			this.className = className;
-			this.classPackage = classPackage;
-			this.testClassPath = testClassPath;
-		}
-
-	}
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Again, you must provide a <code>spring.factories</code> file, such as the one shown in the following
-example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code>org.springframework.cloud.contract.verifier.builder.SingleTestGenerator=/
-com.example.MyGenerator</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_using_the_custom_stub_generator"><a class="link" href="#_using_the_custom_stub_generator">10.3. Using the Custom Stub Generator</a></h3>
-<div class="paragraph">
-<p>If you want to generate stubs for stub servers other than WireMock, you can plug in your
-own implementation of the <code>StubGenerator</code> interface. The following code listing shows the
-<code>StubGenerator</code> interface:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package org.springframework.cloud.contract.verifier.converter;
-
-import java.util.Map;
-
-import org.springframework.cloud.contract.spec.Contract;
-import org.springframework.cloud.contract.verifier.file.ContractMetadata;
-
-/**
- * Converts contracts into their stub representation.
- *
- * @since 1.1.0
- */
-public interface StubGenerator {
-
-	/**
-	 * @param fileName - file name
-	 * @return {@code true} if the converter can handle the file to convert it into a
-	 * stub.
-	 */
-	default boolean canHandleFileName(String fileName) {
-		return fileName.endsWith(fileExtension());
-	}
-
-	/**
-	 * @param rootName - root name of the contract
-	 * @param content - metadata of the contract
-	 * @return the collection of converted contracts into stubs. One contract can result
-	 * in multiple stubs.
-	 */
-	Map&lt;Contract, String&gt; convertContents(String rootName, ContractMetadata content);
-
-	/**
-	 * @param inputFileName - name of the input file
-	 * @return the name of the converted stub file. If you have multiple contracts in a
-	 * single file then a prefix will be added to the generated file. If you provide the
-	 * {@link Contract#name} field then that field will override the generated file name.
-	 *
-	 * Example: name of file with 2 contracts is {@code foo.groovy}, it will be converted
-	 * by the implementation to {@code foo.json}. The recursive file converter will create
-	 * two files {@code 0_foo.json} and {@code 1_foo.json}
-	 */
-	String generateOutputFileNameForInput(String inputFileName);
-
-	/**
-	 * Describes the file extension that this stub generator can handle.
-	 * @return string describing the file extension
-	 */
-	default String fileExtension() {
-		return ".json";
-	}
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Again, you must provide a <code>spring.factories</code> file, such as the one shown in the following
-example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code># Stub converters
-org.springframework.cloud.contract.verifier.converter.StubGenerator=\
-org.springframework.cloud.contract.verifier.wiremock.DslToWireMockClientConverter</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The default implementation is the WireMock stub generation.</p>
-</div>
-<div class="admonitionblock tip">
+<div class="hdlist">
 <table>
 <tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
+<td class="hdlist1">
+<a href="legal.html#legal-information">Legal</a> 
 </td>
-<td class="content">
-You can provide multiple stub generator implementations. For example, from a single
-DSL, you can produce both WireMock stubs and Pact files.
+<td class="hdlist2">
+<p>Legal information.</p>
 </td>
 </tr>
-</table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_using_the_custom_stub_runner"><a class="link" href="#_using_the_custom_stub_runner">10.4. Using the Custom Stub Runner</a></h3>
-<div class="paragraph">
-<p>If you decide to use a custom stub generation, you also need a custom way of running
-stubs with your different stub provider.</p>
-</div>
-<div class="paragraph">
-<p>Assume that you use <a href="https://github.com/dreamhead/moco">Moco</a> to build your stubs and that
-you have written a stub generator and placed your stubs in a JAR file.</p>
-</div>
-<div class="paragraph">
-<p>In order for Stub Runner to know how to run your stubs, you have to define a custom
-HTTP Stub server implementation, which might resemble the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package org.springframework.cloud.contract.stubrunner.provider.moco
-
-import com.github.dreamhead.moco.bootstrap.arg.HttpArgs
-import com.github.dreamhead.moco.runner.JsonRunner
-import com.github.dreamhead.moco.runner.RunnerSetting
-import groovy.util.logging.Commons
-
-import org.springframework.cloud.contract.stubrunner.HttpServerStub
-import org.springframework.util.SocketUtils
-
-@Commons
-class MocoHttpServerStub implements HttpServerStub {
-
-	private boolean started
-	private JsonRunner runner
-	private int port
-
-	@Override
-	int port() {
-		if (!isRunning()) {
-			return -1
-		}
-		return port
-	}
-
-	@Override
-	boolean isRunning() {
-		return started
-	}
-
-	@Override
-	HttpServerStub start() {
-		return start(SocketUtils.findAvailableTcpPort())
-	}
-
-	@Override
-	HttpServerStub start(int port) {
-		this.port = port
-		return this
-	}
-
-	@Override
-	HttpServerStub stop() {
-		if (!isRunning()) {
-			return this
-		}
-		this.runner.stop()
-		return this
-	}
-
-	@Override
-	HttpServerStub registerMappings(Collection&lt;File&gt; stubFiles) {
-		List&lt;RunnerSetting&gt; settings = stubFiles.findAll { it.name.endsWith("json") }
-			.collect {
-			log.info("Trying to parse [${it.name}]")
-			try {
-				return RunnerSetting.aRunnerSetting().withStream(it.newInputStream()).
-					build()
-			}
-			catch (Exception e) {
-				log.warn("Exception occurred while trying to parse file [${it.name}]", e)
-				return null
-			}
-		}.findAll { it }
-		this.runner = JsonRunner.newJsonRunnerWithSetting(settings,
-			HttpArgs.httpArgs().withPort(this.port).build())
-		this.runner.run()
-		this.started = true
-		return this
-	}
-
-	@Override
-	String registeredMappings() {
-		return ""
-	}
-
-	@Override
-	boolean isAccepted(File file) {
-		return file.name.endsWith(".json")
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Then, you can register it in your <code>spring.factories</code> file, as shown in the following
-example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code>org.springframework.cloud.contract.stubrunner.HttpServerStub=\
-org.springframework.cloud.contract.stubrunner.provider.moco.MocoHttpServerStub</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Now you can run stubs with Moco.</p>
-</div>
-<div class="admonitionblock important">
-<table>
 <tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
+<td class="hdlist1">
+<a href="documentation-overview.html#contract-documentation">Documentation Overview</a> 
 </td>
-<td class="content">
-If you do not provide any implementation, then the default (WireMock)
-implementation is used. If you provide more than one, the first one on the list is used.
+<td class="hdlist2">
+<p>About the Documentation, Getting Help, First Steps, and more.</p>
 </td>
 </tr>
-</table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_using_the_custom_stub_downloader"><a class="link" href="#_using_the_custom_stub_downloader">10.5. Using the Custom Stub Downloader</a></h3>
-<div class="paragraph">
-<p>You can customize the way your stubs are downloaded by creating an implementation of the
-<code>StubDownloaderBuilder</code> interface, as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package com.example;
-
-class CustomStubDownloaderBuilder implements StubDownloaderBuilder {
-
-	@Override
-	public StubDownloader build(final StubRunnerOptions stubRunnerOptions) {
-		return new StubDownloader() {
-			@Override
-			public Map.Entry&lt;StubConfiguration, File&gt; downloadAndUnpackStubJar(
-					StubConfiguration config) {
-				File unpackedStubs = retrieveStubs();
-				return new AbstractMap.SimpleEntry&lt;&gt;(
-						new StubConfiguration(config.getGroupId(), config.getArtifactId(), version,
-								config.getClassifier()), unpackedStubs);
-			}
-
-			File retrieveStubs() {
-			    // here goes your custom logic to provide a folder where all the stubs reside
-			}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Then you can register it in your <code>spring.factories</code> file, as shown in the following
-example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code># Example of a custom Stub Downloader Provider
-org.springframework.cloud.contract.stubrunner.StubDownloaderBuilder=\
-com.example.CustomStubDownloaderBuilder</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Now you can pick a folder with the source of your stubs.</p>
-</div>
-<div class="admonitionblock important">
-<table>
 <tr>
-<td class="icon">
-<i class="fa icon-important" title="Important"></i>
+<td class="hdlist1">
+<a href="getting-started.html#getting-started">Getting Started</a> 
 </td>
-<td class="content">
-If you do not provide any implementation, then the default is used (scan classpath).
-If you provide the <code>stubsMode = StubRunnerProperties.StubsMode.LOCAL</code> or
-<code>, stubsMode = StubRunnerProperties.StubsMode.REMOTE</code> then the Aether implementation will be used
-If you provide more than one, then the first one on the list is used.
+<td class="hdlist2">
+<p>Introducing Spring Cloud Contract, Developing Your First Spring Cloud Contract-based Application</p>
 </td>
 </tr>
-</table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="scm-stub-downloader"><a class="link" href="#scm-stub-downloader">10.6. Using the SCM Stub Downloader</a></h3>
-<div class="paragraph">
-<p>Whenever the <code>repositoryRoot</code> starts with a SCM protocol
-(currently we support only <code>git://</code>), the stub downloader will try
-to clone the repository and use it as a source of contracts
-to generate tests or stubs.</p>
-</div>
-<div class="paragraph">
-<p>Either via environment variables, system properties, properties set
-inside the plugin or contracts repository configuration you can
-tweak the downloader&#8217;s behaviour. Below you can find the list of
-properties</p>
-</div>
-<table class="tableblock frame-all grid-all stretch">
-<caption class="title">Table 1. SCM Stub Downloader properties</caption>
-<colgroup>
-<col style="width: 33.3333%;">
-<col style="width: 33.3333%;">
-<col style="width: 33.3334%;">
-</colgroup>
-<tbody>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Type of a property</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Name of the property</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Description</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>git.branch</code> (plugin prop)</p>
-<p class="tableblock">* <code>stubrunner.properties.git.branch</code> (system prop)</p>
-<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_GIT_BRANCH</code> (env prop)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">master</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Which branch to checkout</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>git.username</code> (plugin prop)</p>
-<p class="tableblock">* <code>stubrunner.properties.git.username</code> (system prop)</p>
-<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_GIT_USERNAME</code> (env prop)</p></td>
-<td class="tableblock halign-left valign-top"></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Git clone username</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>git.password</code> (plugin prop)</p>
-<p class="tableblock">* <code>stubrunner.properties.git.password</code> (system prop)</p>
-<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_GIT_PASSWORD</code> (env prop)</p></td>
-<td class="tableblock halign-left valign-top"></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Git clone password</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>git.no-of-attempts</code> (plugin prop)</p>
-<p class="tableblock">* <code>stubrunner.properties.git.no-of-attempts</code> (system prop)</p>
-<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_GIT_NO_OF_ATTEMPTS</code> (env prop)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">10</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Number of attempts to push the commits to <code>origin</code></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>git.wait-between-attempts</code> (Plugin prop)</p>
-<p class="tableblock">* <code>stubrunner.properties.git.wait-between-attempts</code>  (system prop)</p>
-<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_GIT_WAIT_BETWEEN_ATTEMPTS</code>  (env prop)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">1000</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Number of millis to wait between attempts to push the commits to <code>origin</code></p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="sect2">
-<h3 id="pact-stub-downloader"><a class="link" href="#pact-stub-downloader">10.7. Using the Pact Stub Downloader</a></h3>
-<div class="paragraph">
-<p>Whenever the <code>repositoryRoot</code> starts with a Pact protocol
-(starts with <code>pact://</code>), the stub downloader will try
-to fetch the Pact contract definitions from the Pact Broker.
-Whatever is set after <code>pact://</code> will be parsed as the Pact Broker URL.</p>
-</div>
-<div class="paragraph">
-<p>Either via environment variables, system properties, properties set
-inside the plugin or contracts repository configuration you can
-tweak the downloader&#8217;s behaviour. Below you can find the list of
-properties</p>
-</div>
-<table class="tableblock frame-all grid-all stretch">
-<caption class="title">Table 2. SCM Stub Downloader properties</caption>
-<colgroup>
-<col style="width: 33.3333%;">
-<col style="width: 33.3333%;">
-<col style="width: 33.3334%;">
-</colgroup>
-<tbody>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Name of a property</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Default</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Description</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.host</code> (plugin prop)</p>
-<p class="tableblock">* <code>stubrunner.properties.pactbroker.host</code> (system prop)</p>
-<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_HOST</code> (env prop)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Host from URL passed to <code>repositoryRoot</code></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">What is the URL of Pact Broker</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.port</code> (plugin prop)</p>
-<p class="tableblock">* <code>stubrunner.properties.pactbroker.port</code> (system prop)</p>
-<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_PORT</code> (env prop)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Port from URL passed to <code>repositoryRoot</code></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">What is the port of Pact Broker</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.protocol</code> (plugin prop)</p>
-<p class="tableblock">* <code>stubrunner.properties.pactbroker.protocol</code> (system prop)</p>
-<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_PROTOCOL</code> (env prop)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Protocol from URL passed to <code>repositoryRoot</code></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">What is the protocol of Pact Broker</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.tags</code> (plugin prop)</p>
-<p class="tableblock">* <code>stubrunner.properties.pactbroker.tags</code> (system prop)</p>
-<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_TAGS</code> (env prop)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Version of the stub, or <code>latest</code> if version is <code>+</code></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">What tags should be used to fetch the stub</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.auth.scheme</code> (plugin prop)</p>
-<p class="tableblock">* <code>stubrunner.properties.pactbroker.auth.scheme</code> (system prop)</p>
-<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_AUTH_SCHEME</code> (env prop)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><code>Basic</code></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">What kind of authentication should be used to connect to the Pact Broker</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.auth.username</code> (plugin prop)</p>
-<p class="tableblock">* <code>stubrunner.properties.pactbroker.auth.username</code> (system prop)</p>
-<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_AUTH_USERNAME</code> (env prop)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">The username passed to <code>contractsRepositoryUsername</code> (maven) or <code>contractRepository.username</code> (gradle)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Username used to connect to the Pact Broker</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.auth.password</code> (plugin prop)</p>
-<p class="tableblock">* <code>stubrunner.properties.pactbroker.auth.password</code> (system prop)</p>
-<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_AUTH_PASSWORD</code> (env prop)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">The password passed to <code>contractsRepositoryPassword</code> (maven) or <code>contractRepository.password</code> (gradle)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Password used to connect to the Pact Broker</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.provider-name-with-group-id</code> (plugin prop)</p>
-<p class="tableblock">* <code>stubrunner.properties.pactbroker.provider-name-with-group-id</code> (system prop)</p>
-<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_PROVIDER_NAME_WITH_GROUP_ID</code> (env prop)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">false</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">When <code>true</code>, the provider name will be a combination of <code>groupId:artifactId</code>. If <code>false</code>, just <code>artifactId</code> is used</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_spring_cloud_contract_wiremock"><a class="link" href="#_spring_cloud_contract_wiremock">11. Spring Cloud Contract WireMock</a></h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>The Spring Cloud Contract WireMock modules let you use <a href="https://github.com/tomakehurst/wiremock">WireMock</a> in a
-Spring Boot application. Check out the
-<a href="https://github.com/spring-cloud/spring-cloud-contract/tree/master/samples">samples</a>
-for more details.</p>
-</div>
-<div class="paragraph">
-<p>If you have a Spring Boot application that uses Tomcat as an embedded server (which is
-the default with <code>spring-boot-starter-web</code>),  you can add
-<code>spring-cloud-starter-contract-stub-runner</code> to your classpath and add <code>@AutoConfigureWireMock</code> in
-order to be able to use Wiremock in your tests. Wiremock runs as a stub server and you
-can register stub behavior using a Java API or via static JSON declarations as part of
-your test. The following code shows an example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
-@SpringBootTest(webEnvironment = WebEnvironment.RANDOM_PORT)
-@AutoConfigureWireMock(port = 0)
-public class WiremockForDocsTests {
-
-	// A service that calls out over HTTP
-	@Autowired
-	private Service service;
-
-	@Before
-	public void setup() {
-		this.service.setBase("http://localhost:"
-				+ this.environment.getProperty("wiremock.server.port"));
-	}
-
-	// Using the WireMock APIs in the normal way:
-	@Test
-	public void contextLoads() throws Exception {
-		// Stubbing WireMock
-		stubFor(get(urlEqualTo("/resource")).willReturn(aResponse()
-				.withHeader("Content-Type", "text/plain").withBody("Hello World!")));
-		// We're asserting if WireMock responded properly
-		assertThat(this.service.go()).isEqualTo("Hello World!");
-	}
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>To start the stub server on a different port use (for example),
-<code>@AutoConfigureWireMock(port=9999)</code>. For a random port, use a value of <code>0</code>. The stub
-server port can be bound in the test application context with the "wiremock.server.port"
-property. Using <code>@AutoConfigureWireMock</code> adds a bean of type <code>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. Also you can inject a bean of type <code>WireMockServer</code> into your test.</p>
-</div>
-<div class="sect2">
-<h3 id="_registering_stubs_automatically"><a class="link" href="#_registering_stubs_automatically">11.1. Registering Stubs Automatically</a></h3>
-<div class="paragraph">
-<p>If you use <code>@AutoConfigureWireMock</code>, it registers WireMock JSON stubs from the file
-system or classpath (by default, from <code>file:src/test/resources/mappings</code>). You can
-customize the locations using the <code>stubs</code> attribute in the annotation, which can be an
-Ant-style resource pattern or a directory. In the case of a directory, <code><strong>*/</strong>.json</code> is
-appended. The following code shows an example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>@RunWith(SpringRunner.class)
-@SpringBootTest
-@AutoConfigureWireMock(stubs="classpath:/stubs")
-public class WiremockImportApplicationTests {
-
-	@Autowired
-	private Service service;
-
-	@Test
-	public void contextLoads() throws Exception {
-		assertThat(this.service.go()).isEqualTo("Hello World!");
-	}
-
-}</pre>
-</div>
-</div>
-<div class="admonitionblock note">
-<table>
 <tr>
-<td class="icon">
-<i class="fa icon-note" title="Note"></i>
+<td class="hdlist1">
+<a href="using.html#using">Using Spring Cloud Contract</a> 
 </td>
-<td class="content">
-Actually, WireMock always loads mappings from <code>src/test/resources/mappings</code> <strong>as
-well as</strong> the custom locations in the stubs attribute. To change this behavior, you can
-also specify a files root as described in the next section of this document.
+<td class="hdlist2">
+<p>Spring Cloud Contract usage examples and workflows</p>
 </td>
 </tr>
-</table>
-</div>
-<div class="paragraph">
-<p>If you&#8217;re using Spring Cloud Contract&#8217;s default stub jars, then your
-stubs are stored under <code>/META-INF/group-id/artifact-id/versions/mappings/</code> folder. If you want to register all stubs from that location, from all embedded JARs, then it&#8217;s enough to use the following syntax.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureWireMock(port = 0, stubs = "classpath*:/META-INF/**/mappings/**/*.json")</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_using_files_to_specify_the_stub_bodies"><a class="link" href="#_using_files_to_specify_the_stub_bodies">11.2. Using Files to Specify the Stub Bodies</a></h3>
-<div class="paragraph">
-<p>WireMock can read response bodies from files on the classpath or the file system. In that
-case, you can see in the JSON DSL that the response has a <code>bodyFileName</code> instead of a
-(literal) <code>body</code>. The files are resolved relative to a root directory (by default,
-<code>src/test/resources/__files</code>). To customize this location you can set the <code>files</code>
-attribute in the <code>@AutoConfigureWireMock</code> annotation to the location of the parent
-directory (in other words, <code>__files</code> is a subdirectory). You can use Spring resource
-notation to refer to <code>file:&#8230;&#8203;</code> or <code>classpath:&#8230;&#8203;</code> locations. Generic URLs are not
-supported. A list of values can be given, in which case WireMock resolves the first file
-that exists when it needs to find a response body.</p>
-</div>
-<div class="admonitionblock note">
-<table>
 <tr>
-<td class="icon">
-<i class="fa icon-note" title="Note"></i>
+<td class="hdlist1">
+<a href="project-features.html#features">Spring Cloud Contract Features</a> 
 </td>
-<td class="content">
-When you configure the <code>files</code> root, it also affects the
-automatic loading of stubs, because they come from the root location
-in a subdirectory called "mappings". The value of <code>files</code> has no
-effect on the stubs loaded explicitly from the <code>stubs</code> attribute.
+<td class="hdlist2">
+<p>Contract DSL, Messaging, Spring Cloud Contract Stub Runner, and Spring Cloud Contract WireMock.</p>
 </td>
 </tr>
-</table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_alternative_using_junit_rules"><a class="link" href="#_alternative_using_junit_rules">11.3. Alternative: Using JUnit Rules</a></h3>
-<div class="paragraph">
-<p>For a more conventional WireMock experience, you can use JUnit <code>@Rules</code> to start and stop
-the server. To do so, use the <code>WireMockSpring</code> convenience class to obtain an <code>Options</code>
-instance, as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
-@SpringBootTest(webEnvironment = WebEnvironment.RANDOM_PORT)
-public class WiremockForDocsClassRuleTests {
-
-	// Start WireMock on some dynamic port
-	// for some reason `dynamicPort()` is not working properly
-	@ClassRule
-	public static WireMockClassRule wiremock = new WireMockClassRule(
-			WireMockSpring.options().dynamicPort());
-
-	// A service that calls out over HTTP to wiremock's port
-	@Autowired
-	private Service service;
-
-	@Before
-	public void setup() {
-		this.service.setBase("http://localhost:" + wiremock.port());
-	}
-
-	// Using the WireMock APIs in the normal way:
-	@Test
-	public void contextLoads() throws Exception {
-		// Stubbing WireMock
-		wiremock.stubFor(get(urlEqualTo("/resource")).willReturn(aResponse()
-				.withHeader("Content-Type", "text/plain").withBody("Hello World!")));
-		// We're asserting if WireMock responded properly
-		assertThat(this.service.go()).isEqualTo("Hello World!");
-	}
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The <code>@ClassRule</code> means that the server shuts down after all the methods in this class
-have been run.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_relaxed_ssl_validation_for_rest_template"><a class="link" href="#_relaxed_ssl_validation_for_rest_template">11.4. Relaxed SSL Validation for Rest Template</a></h3>
-<div class="paragraph">
-<p>WireMock lets you stub a "secure" server with an "https" URL protocol. If your
-application wants to contact that stub server in an integration test, it will find that
-the SSL certificates are not valid (the usual problem with self-installed certificates).
-The best option is often to re-configure the client to use "http". If that&#8217;s not an
-option, you can ask Spring to configure an HTTP client that ignores SSL validation errors
-(do so only for tests, of course).</p>
-</div>
-<div class="paragraph">
-<p>To make this work with minimum fuss, you need to be using the Spring Boot
-<code>RestTemplateBuilder</code> in your app, as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Bean
-public RestTemplate restTemplate(RestTemplateBuilder builder) {
-	return builder.build();
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You need <code>RestTemplateBuilder</code> because the builder is passed through callbacks to
-initialize it, so the SSL validation can be set up in the client at that point. This
-happens automatically in your test if you are using the <code>@AutoConfigureWireMock</code>
-annotation or the stub runner. If you use the JUnit <code>@Rule</code> approach, you need to add the
-<code>@AutoConfigureHttpClient</code> annotation as well, as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
-@SpringBootTest("app.baseUrl=https://localhost:6443")
-@AutoConfigureHttpClient
-public class WiremockHttpsServerApplicationTests {
-
-	@ClassRule
-	public static WireMockClassRule wiremock = new WireMockClassRule(
-			WireMockSpring.options().httpsPort(6443));
-...
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>If you are using <code>spring-boot-starter-test</code>, you have the Apache HTTP client on the
-classpath and it is selected by the <code>RestTemplateBuilder</code> and configured to ignore SSL
-errors. If you use the default <code>java.net</code> client, you do not need the annotation (but it
-won&#8217;t do any harm). There is no support currently for other clients, but it may be added
-in future releases.</p>
-</div>
-<div class="paragraph">
-<p>To disable the custom <code>RestTemplateBuilder</code>, set the <code>wiremock.rest-template-ssl-enabled</code>
-property to <code>false</code>.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_wiremock_and_spring_mvc_mocks"><a class="link" href="#_wiremock_and_spring_mvc_mocks">11.5. WireMock and Spring MVC Mocks</a></h3>
-<div class="paragraph">
-<p>Spring Cloud Contract provides a convenience class that can load JSON WireMock stubs into
-a Spring <code>MockRestServiceServer</code>. The following code shows an example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
-@SpringBootTest(webEnvironment = WebEnvironment.NONE)
-public class WiremockForDocsMockServerApplicationTests {
-
-	@Autowired
-	private RestTemplate restTemplate;
-
-	@Autowired
-	private Service service;
-
-	@Test
-	public void contextLoads() throws Exception {
-		// will read stubs classpath
-		MockRestServiceServer server = WireMockRestServiceServer.with(this.restTemplate)
-				.baseUrl("https://example.org").stubs("classpath:/stubs/resource.json")
-				.build();
-		// We're asserting if WireMock responded properly
-		assertThat(this.service.go()).isEqualTo("Hello World");
-		server.verify();
-	}
-
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The <code>baseUrl</code> value is prepended to all mock calls, and the <code>stubs()</code> method takes a stub
-path resource pattern as an argument. In the preceding example, the stub defined at
-<code>/stubs/resource.json</code> is loaded into the mock server. If the <code>RestTemplate</code> is asked to
-visit <code><a href="https://example.org/" class="bare">https://example.org/</a></code>, it gets the responses as being declared at that URL. More
-than one stub pattern can be specified, and each one can be a directory (for a recursive
-list of all ".json"), a fixed filename (as in the example above), or an Ant-style
-pattern. The JSON format is the normal WireMock format, which you can read about in the
-<a href="https://wiremock.org/docs/stubbing/">WireMock website</a>.</p>
-</div>
-<div class="paragraph">
-<p>Currently, the Spring Cloud Contract Verifier supports Tomcat, Jetty, and Undertow as
-Spring Boot embedded servers, and Wiremock itself has "native" support for a particular
-version of Jetty (currently 9.2). To use the native Jetty, you need to add the native
-Wiremock dependencies and exclude the Spring Boot container (if there is one).</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_customization_of_wiremock_configuration"><a class="link" href="#_customization_of_wiremock_configuration">11.6. Customization of WireMock configuration</a></h3>
-<div class="paragraph">
-<p>You can register a bean of <code>org.springframework.cloud.contract.wiremock.WireMockConfigurationCustomizer</code> type
-in order to customize the WireMock configuration (e.g. add custom transformers).
-Example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">		@Bean
-		WireMockConfigurationCustomizer optionsCustomizer() {
-			return new WireMockConfigurationCustomizer() {
-				@Override
-				public void customize(WireMockConfiguration options) {
-// perform your customization here
-				}
-			};
-		}</code></pre>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_generating_stubs_using_rest_docs"><a class="link" href="#_generating_stubs_using_rest_docs">11.7. Generating Stubs using REST Docs</a></h3>
-<div class="paragraph">
-<p><a href="https://projects.spring.io/spring-restdocs">Spring REST Docs</a> can be used to generate
-documentation (for example in Asciidoctor format) for an HTTP API with Spring MockMvc
-or <code>WebTestClient</code> or Rest Assured. At the same time that you generate documentation for your API, you can also
-generate WireMock stubs by using Spring Cloud Contract WireMock. To do so, write your
-normal REST Docs test cases and use <code>@AutoConfigureRestDocs</code> to have stubs be
-automatically generated in the REST Docs output directory. The following code shows an
-example using <code>MockMvc</code>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
-@SpringBootTest
-@AutoConfigureRestDocs(outputDir = "target/snippets")
-@AutoConfigureMockMvc
-public class ApplicationTests {
-
-	@Autowired
-	private MockMvc mockMvc;
-
-	@Test
-	public void contextLoads() throws Exception {
-		mockMvc.perform(get("/resource"))
-				.andExpect(content().string("Hello World"))
-				.andDo(document("resource"));
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>This test generates a WireMock stub at "target/snippets/stubs/resource.json". It matches
-all GET requests to the "/resource" path. The same example with <code>WebTestClient</code> (used
-for testing Spring WebFlux applications) would look like this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
-@SpringBootTest
-@AutoConfigureRestDocs(outputDir = "target/snippets")
-@AutoConfigureWebTestClient
-public class ApplicationTests {
-
-	@Autowired
-	private WebTestClient client;
-
-	@Test
-	public void contextLoads() throws Exception {
-		client.get().uri("/resource").exchange()
-				.expectBody(String.class).isEqualTo("Hello World")
- 				.consumeWith(document("resource"));
-	}
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Without any additional configuration, these tests create a stub with a request matcher
-for the HTTP method and all headers except "host" and "content-length". To match the
-request more precisely (for example, to match the body of a POST or PUT), we need to
-explicitly create a request matcher. Doing so has two effects:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Creating a stub that matches only in the way you specify.</p>
-</li>
-<li>
-<p>Asserting that the request in the test case also matches the same conditions.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>The main entry point for this feature is <code>WireMockRestDocs.verify()</code>, which can be used
-as a substitute for the <code>document()</code> convenience method, as shown in the following
-example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import static org.springframework.cloud.contract.wiremock.restdocs.WireMockRestDocs.verify;</code></pre>
-</div>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>@RunWith(SpringRunner.class)
-@SpringBootTest
-@AutoConfigureRestDocs(outputDir = "target/snippets")
-@AutoConfigureMockMvc
-public class ApplicationTests {
-
-	@Autowired
-	private MockMvc mockMvc;
-
-	@Test
-	public void contextLoads() throws Exception {
-		mockMvc.perform(post("/resource")
-                .content("{\"id\":\"123456\",\"message\":\"Hello World\"}"))
-				.andExpect(status().isOk())
-				.andDo(verify().jsonPath("$.id")
-                        .stub("resource"));
-	}
-}</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>This contract specifies that any valid POST with an "id" field receives the response
-defined in this test. You can chain together calls to <code>.jsonPath()</code> to add additional
-matchers. If JSON Path is unfamiliar, The <a href="https://github.com/jayway/JsonPath">JayWay
-documentation</a> can help you get up to speed. The <code>WebTestClient</code> version of this test
-has a similar <code>verify()</code> static helper that you insert in the same place.</p>
-</div>
-<div class="paragraph">
-<p>Instead of the <code>jsonPath</code> and <code>contentType</code> convenience methods, you can also use the
-WireMock APIs to verify that the request matches the created stub, as shown in the
-following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Test
-public void contextLoads() throws Exception {
-	mockMvc.perform(post("/resource")
-               .content("{\"id\":\"123456\",\"message\":\"Hello World\"}"))
-			.andExpect(status().isOk())
-			.andDo(verify()
-					.wiremock(WireMock.post(
-						urlPathEquals("/resource"))
-						.withRequestBody(matchingJsonPath("$.id"))
-                       .stub("post-resource"));
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The WireMock API is rich. You can match headers, query parameters, and request body by
-regex as well as by JSON path. These features can be used to create stubs with a wider
-range of parameters. The above example generates a stub resembling the following example:</p>
-</div>
-<div class="listingblock">
-<div class="title">post-resource.json</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
-  "request" : {
-    "url" : "/resource",
-    "method" : "POST",
-    "bodyPatterns" : [ {
-      "matchesJsonPath" : "$.id"
-    }]
-  },
-  "response" : {
-    "status" : 200,
-    "body" : "Hello World",
-    "headers" : {
-      "X-Application-Context" : "application:-1",
-      "Content-Type" : "text/plain"
-    }
-  }
-}</code></pre>
-</div>
-</div>
-<div class="admonitionblock note">
-<table>
 <tr>
-<td class="icon">
-<i class="fa icon-note" title="Note"></i>
+<td class="hdlist1">
+<a href="project-features.html#features-build-tools">Build Tools</a> 
 </td>
-<td class="content">
-You can use either the <code>wiremock()</code> method or the <code>jsonPath()</code> and <code>contentType()</code>
-methods to create request matchers, but you can&#8217;t use both approaches.
+<td class="hdlist2">
+<p>Maven Plugin, Gradle Plugin, and Docker.</p>
 </td>
 </tr>
-</table>
-</div>
-<div class="paragraph">
-<p>On the consumer side, you can make the <code>resource.json</code> generated earlier in this section
-available on the classpath (by
-&lt;&lt;publishing-stubs-as-jars], for example). After that, you can create a stub using WireMock in a
-number of different ways, including by using
-<code>@AutoConfigureWireMock(stubs="classpath:resource.json")</code>, as described earlier in this
-document.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_generating_contracts_by_using_rest_docs"><a class="link" href="#_generating_contracts_by_using_rest_docs">11.8. Generating Contracts by Using REST Docs</a></h3>
-<div class="paragraph">
-<p>You can also generate Spring Cloud Contract DSL files and documentation with Spring REST
-Docs. If you do so in combination with Spring Cloud WireMock, you get both the contracts
-and the stubs.</p>
-</div>
-<div class="paragraph">
-<p>Why would you want to use this feature? Some people in the community asked questions
-about a situation in which they would like to move to DSL-based contract definition,
-but they already have a lot of Spring MVC tests. Using this feature lets you generate
-the contract files that you can later modify and move to folders (defined in your
-configuration) so that the plugin finds them.</p>
-</div>
-<div class="admonitionblock tip">
-<table>
 <tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
+<td class="hdlist1">
+<a href="howto.html#howto">&#8220;How-to&#8221; Guides</a> 
 </td>
-<td class="content">
-You might wonder why this functionality is in the WireMock module. The functionality
-is there because it makes sense to generate both the contracts and the stubs.
+<td class="hdlist2">
+<p>Stubs versioning, Pact integration, Debugging, and more.</p>
 </td>
 </tr>
-</table>
-</div>
-<div class="paragraph">
-<p>Consider the following test:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">		this.mockMvc
-				.perform(post("/foo").accept(MediaType.APPLICATION_PDF)
-						.accept(MediaType.APPLICATION_JSON)
-						.contentType(MediaType.APPLICATION_JSON)
-						.content("{\"foo\": 23, \"bar\" : \"baz\" }"))
-				.andExpect(status().isOk()).andExpect(content().string("bar"))
-				// first WireMock
-				.andDo(WireMockRestDocs.verify().jsonPath("$[?(@.foo &gt;= 20)]")
-						.jsonPath("$[?(@.bar in ['baz','bazz','bazzz'])]")
-						.contentType(MediaType.valueOf("application/json"))
-						.stub("shouldGrantABeerIfOldEnough"))
-				// then Contract DSL documentation
-				.andDo(document("index", SpringCloudContractRestDocs.dslContract()));</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The preceding test creates the stub presented in the previous section, generating both
-the contract and a documentation file.</p>
-</div>
-<div class="paragraph">
-<p>The contract is called <code>index.groovy</code> and might look like the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">import org.springframework.cloud.contract.spec.Contract
-
-Contract.make {
-    request {
-        method 'POST'
-        url '/foo'
-        body('''
-            {"foo": 23 }
-        ''')
-        headers {
-            header('''Accept''', '''application/json''')
-            header('''Content-Type''', '''application/json''')
-        }
-    }
-    response {
-        status OK()
-        body('''
-        bar
-        ''')
-        headers {
-            header('''Content-Type''', '''application/json;charset=UTF-8''')
-            header('''Content-Length''', '''3''')
-        }
-        testMatchers {
-            jsonPath('$[?(@.foo &gt;= 20)]', byType())
-        }
-    }
-}</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The generated document (formatted in Asciidoc in this case) contains a formatted
-contract. The location of this file would be <code>index/dsl-contract.adoc</code>.</p>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_migrations"><a class="link" href="#_migrations">12. Migrations</a></h2>
-<div class="sectionbody">
-<div class="admonitionblock tip">
-<table>
 <tr>
-<td class="icon">
-<i class="fa icon-tip" title="Tip"></i>
+<td class="hdlist1">
+<a href="appendix.html#appendix">Appendices</a> 
 </td>
-<td class="content">
-For up to date migration guides please visit
-the project&#8217;s <a href="https://github.com/spring-cloud/spring-cloud-contract/wiki/">wiki page</a>.
+<td class="hdlist2">
+<p>Properties, Metadata, Configuration, Dependencies, and more.</p>
 </td>
 </tr>
 </table>
 </div>
-<div class="paragraph">
-<p>This section covers migrating from one version of Spring Cloud Contract Verifier to the
-next version. It covers the following versions upgrade paths:</p>
-</div>
-<div class="sect2">
-<h3 id="cloud-verifier-1.0-1.1"><a class="link" href="#cloud-verifier-1.0-1.1">12.1. 1.0.x &#8594; 1.1.x</a></h3>
-<div class="paragraph">
-<p>This section covers upgrading from version 1.0 to version 1.1.</p>
-</div>
-<div class="sect3">
-<h4 id="_new_structure_of_generated_stubs"><a class="link" href="#_new_structure_of_generated_stubs">12.1.1. New structure of generated stubs</a></h4>
-<div class="paragraph">
-<p>In <code>1.1.x</code> we have introduced a change to the structure of generated stubs. If you have
-been using the  <code>@AutoConfigureWireMock</code> notation to use the stubs from the classpath,
-it no longer works. The following example shows how the <code>@AutoConfigureWireMock</code> notation
-used to work:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureWireMock(stubs = "classpath:/customer-stubs/mappings", port = 8084)</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You must either change the location of the stubs to:
-<code>classpath:&#8230;&#8203;/META-INF/groupId/artifactId/version/mappings</code> or use the new
-classpath-based <code>@AutoConfigureStubRunner</code>, as shown in the following example:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureWireMock(stubs = "classpath:customer-stubs/META-INF/travel.components/customer-contract/1.0.2-SNAPSHOT/mappings/", port = 8084)</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>If you do not want to use <code>@AutoConfigureStubRunner</code> and you want to remain with the old
-structure, set your plugin tasks accordingly. The following example would work for the
-structure presented in the previous snippet.</p>
-</div>
-<div class="listingblock primary">
-<div class="title">Maven</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;!-- start of pom.xml --&gt;
-
-&lt;properties&gt;
-    &lt;!-- we don't want the verifier to do a jar for us --&gt;
-    &lt;spring.cloud.contract.verifier.skip&gt;true&lt;/spring.cloud.contract.verifier.skip&gt;
-&lt;/properties&gt;
-
-&lt;!-- ... --&gt;
-
-&lt;!-- You need to set up the assembly plugin --&gt;
-&lt;build&gt;
-    &lt;plugins&gt;
-        &lt;plugin&gt;
-            &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
-            &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
-            &lt;executions&gt;
-                &lt;execution&gt;
-                    &lt;id&gt;stub&lt;/id&gt;
-                    &lt;phase&gt;prepare-package&lt;/phase&gt;
-                    &lt;goals&gt;
-                        &lt;goal&gt;single&lt;/goal&gt;
-                    &lt;/goals&gt;
-                    &lt;inherited&gt;false&lt;/inherited&gt;
-                    &lt;configuration&gt;
-                        &lt;attach&gt;true&lt;/attach&gt;
-                        &lt;descriptor&gt;${basedir}/src/assembly/stub.xml&lt;/descriptor&gt;
-                    &lt;/configuration&gt;
-                &lt;/execution&gt;
-            &lt;/executions&gt;
-        &lt;/plugin&gt;
-    &lt;/plugins&gt;
-&lt;/build&gt;
-&lt;!-- end of pom.xml --&gt;
-
-&lt;!-- start of stub.xml--&gt;
-
-&lt;assembly
-	xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3"
-	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-	xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3 https://maven.apache.org/xsd/assembly-1.1.3.xsd"&gt;
-	&lt;id&gt;stubs&lt;/id&gt;
-	&lt;formats&gt;
-		&lt;format&gt;jar&lt;/format&gt;
-	&lt;/formats&gt;
-	&lt;includeBaseDirectory&gt;false&lt;/includeBaseDirectory&gt;
-	&lt;fileSets&gt;
-		&lt;fileSet&gt;
-			&lt;directory&gt;${project.build.directory}/snippets/stubs&lt;/directory&gt;
-			&lt;outputDirectory&gt;customer-stubs/mappings&lt;/outputDirectory&gt;
-			&lt;includes&gt;
-				&lt;include&gt;**/*&lt;/include&gt;
-			&lt;/includes&gt;
-		&lt;/fileSet&gt;
-		&lt;fileSet&gt;
-			&lt;directory&gt;${basedir}/src/test/resources/contracts&lt;/directory&gt;
-			&lt;outputDirectory&gt;customer-stubs/contracts&lt;/outputDirectory&gt;
-			&lt;includes&gt;
-				&lt;include&gt;**/*.groovy&lt;/include&gt;
-			&lt;/includes&gt;
-		&lt;/fileSet&gt;
-	&lt;/fileSets&gt;
-&lt;/assembly&gt;
-
-&lt;!-- end of stub.xml--&gt;</code></pre>
-</div>
-</div>
-<div class="listingblock secondary">
-<div class="title">Gradle</div>
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">task copyStubs(type: Copy, dependsOn: 'generateWireMockClientStubs') {
-//    Preserve directory structure from 1.0.X of spring-cloud-contract
-    from "${project.buildDir}/resources/main/customer-stubs/META-INF/${project.group}/${project.name}/${project.version}"
-    into "${project.buildDir}/resources/main/customer-stubs"
-}</code></pre>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="cloud-verifier-1.1-1.2"><a class="link" href="#cloud-verifier-1.1-1.2">12.2. 1.1.x &#8594; 1.2.x</a></h3>
-<div class="paragraph">
-<p>This section covers upgrading from version 1.1 to version 1.2.</p>
-</div>
-<div class="sect3">
-<h4 id="_custom_httpserverstub"><a class="link" href="#_custom_httpserverstub">12.2.1. Custom <code>HttpServerStub</code></a></h4>
-<div class="paragraph">
-<p><code>HttpServerStub</code> includes a method that was not in version 1.1. The method is
-<code>String registeredMappings()</code> If you have classes that implement <code>HttpServerStub</code>, you
-now have to implement the <code>registeredMappings()</code> method. It should return a <code>String</code>
-representing all mappings available in a single <code>HttpServerStub</code>.</p>
-</div>
-<div class="paragraph">
-<p>See <a href="https://github.com/spring-cloud/spring-cloud-contract/issues/355">issue 355</a> for more
-detail.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_new_packages_for_generated_tests"><a class="link" href="#_new_packages_for_generated_tests">12.2.2. New packages for generated tests</a></h4>
-<div class="paragraph">
-<p>The flow for setting the generated tests package name will look like this:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Set <code>basePackageForTests</code></p>
-</li>
-<li>
-<p>If <code>basePackageForTests</code> was not set, pick the package from <code>baseClassForTests</code></p>
-</li>
-<li>
-<p>If <code>baseClassForTests</code> was not set, pick <code>packageWithBaseClasses</code></p>
-</li>
-<li>
-<p>If nothing got set, pick the default value:
-<code>org.springframework.cloud.contract.verifier.tests</code></p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>See <a href="https://github.com/spring-cloud/spring-cloud-contract/issues/260">issue 260</a> for more
-detail.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_new_methods_in_templateprocessor"><a class="link" href="#_new_methods_in_templateprocessor">12.2.3. New Methods in TemplateProcessor</a></h4>
-<div class="paragraph">
-<p>In order to add support for <code>fromRequest.path</code>, the following methods had to be added to the
-<code>TemplateProcessor</code> interface:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><code>path()</code></p>
-</li>
-<li>
-<p><code>path(int index)</code></p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>See <a href="https://github.com/spring-cloud/spring-cloud-contract/issues/388">issue 388</a> for more
-detail.</p>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_restassured_3_0"><a class="link" href="#_restassured_3_0">12.2.4. RestAssured 3.0</a></h4>
-<div class="paragraph">
-<p>Rest Assured, used in the generated test classes, got bumped to <code>3.0</code>. If
-you manually set versions of Spring Cloud Contract and the release train
-you might see the following exception:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile (default-testCompile) on project some-project: Compilation failure: Compilation failure:
-[ERROR] /some/path/SomeClass.java:[4,39] package com.jayway.restassured.response does not exist</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>This exception will occur due to the fact that the tests got generated with
-an old version of plugin and at test execution time you have an incompatible
-version of the release train (and vice versa).</p>
-</div>
-<div class="paragraph">
-<p>Done via <a href="https://github.com/spring-cloud/spring-cloud-contract/issues/267">issue 267</a></p>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="cloud-verifier-1.2-2.0"><a class="link" href="#cloud-verifier-1.2-2.0">12.3. 1.2.x &#8594; 2.0.x</a></h3>
-
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_links"><a class="link" href="#_links">13. Links</a></h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>The following links may be helpful when working with Spring Cloud Contract:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="https://github.com/spring-cloud/spring-cloud-contract/">Spring Cloud Contract Github
-Repository</a></p>
-</li>
-<li>
-<p><a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/">Spring Cloud
-Contract Samples</a></p>
-</li>
-<li>
-<p><a href="https://gitter.im/spring-cloud/spring-cloud-contract">Spring Cloud Contract Gitter</a></p>
-</li>
-<li>
-<p><a href="https://www.youtube.com/watch?v=sAAklvxmPmk">Spring Cloud Contract WJUG Presentation by
-Marcin Grzejszczak</a></p>
-</li>
-</ul>
-</div>
 </div>
 </div>
 </div>
 <script type="text/javascript" src="js/tocbot/tocbot.min.js"></script>
 <script type="text/javascript" src="js/toc.js"></script>
-<link rel="stylesheet" href="js/highlight/styles/atom-one-dark-reasonable.min.css">
+<link rel="stylesheet" href="js/highlight/styles/github.min.css">
 <script src="js/highlight/highlight.min.js"></script>
 <script>hljs.initHighlighting()</script>
 </body>
diff --git a/reference/htmlsingle/spring-cloud-contract.html b/reference/htmlsingle/spring-cloud-contract.html
new file mode 100644
index 0000000000..0317d5c47e
--- /dev/null
+++ b/reference/htmlsingle/spring-cloud-contract.html
@@ -0,0 +1,20044 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta charset="UTF-8">
+<!--[if IE]><meta http-equiv="X-UA-Compatible" content="IE=edge"><![endif]-->
+<meta name="viewport" content="width=device-width, initial-scale=1.0">
+<meta name="generator" content="Asciidoctor 1.5.8">
+<meta name="author" content="Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant">
+<title>Spring Cloud Contract Reference Documentation</title>
+<link rel="stylesheet" href="css/spring.css">
+<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css">
+
+<style>
+.hidden {
+	display: none;
+}
+
+.switch {
+	border-width: 1px 1px 0 1px;
+	border-style: solid;
+	border-color: #7a2518;
+	display: inline-block;
+}
+
+.switch--item {
+	padding: 10px;
+	background-color: #ffffff;
+	color: #7a2518;
+	display: inline-block;
+	cursor: pointer;
+}
+
+.switch--item:not(:first-child) {
+	border-width: 0 0 0 1px;
+	border-style: solid;
+	border-color: #7a2518;
+}
+
+.switch--item.selected {
+	background-color: #7a2519;
+	color: #ffffff;
+}
+</style>
+<script src="https://cdnjs.cloudflare.com/ajax/libs/zepto/1.2.0/zepto.min.js"></script>
+<script type="text/javascript">
+function addBlockSwitches() {
+	$('.primary').each(function() {
+		primary = $(this);
+		createSwitchItem(primary, createBlockSwitch(primary)).item.addClass("selected");
+		primary.children('.title').remove();
+	});
+	$('.secondary').each(function(idx, node) {
+		secondary = $(node);
+		primary = findPrimary(secondary);
+		switchItem = createSwitchItem(secondary, primary.children('.switch'));
+		switchItem.content.addClass('hidden');
+		findPrimary(secondary).append(switchItem.content);
+		secondary.remove();
+	});
+}
+
+function createBlockSwitch(primary) {
+	blockSwitch = $('<div class="switch"></div>');
+	primary.prepend(blockSwitch);
+	return blockSwitch;
+}
+
+function findPrimary(secondary) {
+	candidate = secondary.prev();
+	while (!candidate.is('.primary')) {
+		candidate = candidate.prev();
+	}
+	return candidate;
+}
+
+function createSwitchItem(block, blockSwitch) {
+	blockName = block.children('.title').text();
+	content = block.children('.content').first().append(block.next('.colist'));
+	item = $('<div class="switch--item">' + blockName + '</div>');
+	item.on('click', '', content, function(e) {
+		$(this).addClass('selected');
+		$(this).siblings().removeClass('selected');
+		e.data.siblings('.content').addClass('hidden');
+		e.data.removeClass('hidden');
+	});
+	blockSwitch.append(item);
+	return {'item': item, 'content': content};
+}
+
+function globalSwitch() {
+	$('.switch--item').each(function() {
+		$(this).off('click');
+		$(this).on('click', function() {
+			selectedText = $(this).text()
+			selectedIndex = $(this).index()
+			$(".switch--item").filter(function() { return ($(this).text() === selectedText) }).each(function() {
+				$(this).addClass('selected');
+				$(this).siblings().removeClass('selected');
+				selectedContent = $(this).parent().siblings(".content").eq(selectedIndex)
+				selectedContent.removeClass('hidden');
+				selectedContent.siblings().addClass('hidden');
+			});
+		});
+	});
+}
+
+$(addBlockSwitches);
+$(globalSwitch);
+
+</script>
+
+</head>
+<body id="spring-cloud-contract-reference-documentation" class="book toc2 toc-left">
+<div id="header">
+<h1>Spring Cloud Contract Reference Documentation</h1>
+<div class="details">
+<span id="author" class="author">Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant</span><br>
+</div>
+<div id="toc" class="toc2">
+<div id="toctitle">Table of Contents</div>
+<ul class="sectlevel1">
+<li><a href="#legal">Legal</a></li>
+<li><a href="#getting-started">1. Getting Started</a>
+<ul class="sectlevel2">
+<li><a href="#getting-started-introducing-spring-cloud-contract">1.1. Introducing Spring Cloud Contract</a></li>
+<li><a href="#getting-started-three-second-tour">1.2. A Three-second Tour</a></li>
+<li><a href="#getting-started-first-application">1.3. Developing Your First Spring Cloud Contract-based Application</a></li>
+<li><a href="#getting-started-cdc">1.4. Step-by-step Guide to Consumer Driven Contracts (CDC) with Contracts on the Producer Side</a></li>
+<li><a href="#getting-started-whats-next">1.5. Next Steps</a></li>
+</ul>
+</li>
+<li><a href="#using">2. Using Spring Cloud Contract</a>
+<ul class="sectlevel2">
+<li><a href="#flows-provider-nexus">2.1. Provider Contract Testing with Stubs in Nexus or Artifactory</a></li>
+<li><a href="#flows-provider-git">2.2. Provider Contract Testing with Stubs in Git</a></li>
+<li><a href="#flows-cdc-contracts-producer">2.3. Consumer Driven Contracts with Contracts on the Producer Side</a></li>
+<li><a href="#flows-cdc-contracts-external">2.4. Consumer Driven Contracts with Contracts in an External Repository</a></li>
+<li><a href="#flows-cdc-contracts-stubs-git">2.5. Consumer Driven Contracts with Contracts on the Producer Side, Pushed to Git</a></li>
+<li><a href="#flows-provider-non-spring">2.6. Provider Contract Testing with Stubs in Artifactory for a non-Spring Application</a></li>
+<li><a href="#flows-provider-non-jvm">2.7. Provider Contract Testing with Stubs in Artifactory in a non-JVM World</a></li>
+<li><a href="#flows-provider-rest-docs">2.8. Provider Contract Testing with REST Docs and Stubs in Nexus or Artifactory</a></li>
+<li><a href="#using-whats-next">2.9. What to Read Next</a></li>
+</ul>
+</li>
+<li><a href="#features">3. Spring Cloud Contract Features</a>
+<ul class="sectlevel2">
+<li><a href="#contract-dsl">3.1. Contract DSL</a></li>
+<li><a href="#features-http">3.2. Contracts for HTTP</a></li>
+<li><a href="#feature-integrations">3.3. Integrations</a></li>
+<li><a href="#features-messaging">3.4. Messaging</a></li>
+<li><a href="#features-stub-runner">3.5. Spring Cloud Contract Stub Runner</a></li>
+<li><a href="#features-wiremock">3.6. Spring Cloud Contract WireMock</a></li>
+<li><a href="#features-build-tools">3.7. Build Tools Integration</a></li>
+<li><a href="#features-whats-next">3.8. What to Read Next</a></li>
+</ul>
+</li>
+<li><a href="#maven-project">4. Maven Project</a>
+<ul class="sectlevel2">
+<li><a href="#maven-add-plugin">4.1. Adding the Maven Plugin</a></li>
+<li><a href="#maven-rest-assured">4.2. Maven and Rest Assured 2.0</a></li>
+<li><a href="#maven-snapshot-versions">4.3. Using Snapshot and Milestone Versions for Maven</a></li>
+<li><a href="#maven-add-stubs">4.4. Adding stubs</a></li>
+<li><a href="#maven-run-plugin">4.5. Run plugin</a></li>
+<li><a href="#maven-configure-plugin">4.6. Configure plugin</a></li>
+<li><a href="#maven-configuration-options">4.7. Configuration Options</a></li>
+<li><a href="#maven-single-base">4.8. Single Base Class for All Tests</a></li>
+<li><a href="#maven-different-base">4.9. Using Different Base Classes for Contracts</a></li>
+<li><a href="#maven-invoking-generated-tests">4.10. Invoking Generated Tests</a></li>
+<li><a href="#maven-pushing-stubs-to-scm">4.11. Pushing Stubs to SCM</a></li>
+<li><a href="#maven-sts">4.12. Maven Plugin and STS</a></li>
+<li><a href="#maven-plugin-with-spock-tests">4.13. Maven Plugin with Spock Tests</a></li>
+</ul>
+</li>
+<li><a href="#gradle-project">5. Gradle Project</a>
+<ul class="sectlevel2">
+<li><a href="#gradle-prerequisites">5.1. Prerequisites</a></li>
+<li><a href="#gradle-add-gradle-plugin">5.2. Add Gradle Plugin with Dependencies</a></li>
+<li><a href="#gradle-and-rest-assured">5.3. Gradle and Rest Assured 2.0</a></li>
+<li><a href="#gradle-snapshot-versions">5.4. Snapshot Versions for Gradle</a></li>
+<li><a href="#gradle-add-stubs">5.5. Add stubs</a></li>
+<li><a href="#gradle-run-plugin">5.6. Running the Plugin</a></li>
+<li><a href="#gradle-default-setup">5.7. Default Setup</a></li>
+<li><a href="#gradle-configure-plugin">5.8. Configuring the Plugin</a></li>
+<li><a href="#gradle-configuration-options">5.9. Configuration Options</a></li>
+<li><a href="#gradle-single-base-class">5.10. Single Base Class for All Tests</a></li>
+<li><a href="#gradle-different-base-classes">5.11. Different Base Classes for Contracts</a></li>
+<li><a href="#gradle-invoking-generated-tests">5.12. Invoking Generated Tests</a></li>
+<li><a href="#gradle-pushing-stubs-to-scm">5.13. Pushing Stubs to SCM</a></li>
+<li><a href="#gradle-consumer">5.14. Spring Cloud Contract Verifier on the Consumer Side</a></li>
+</ul>
+</li>
+<li><a href="#docker">6. Docker Project</a>
+<ul class="sectlevel2">
+<li><a href="#docker-intro">6.1. A Short Introduction to Maven, JARs and Binary storage</a></li>
+<li><a href="#docker-how-it-works">6.2. Generating Tests on the Producer Side</a></li>
+<li><a href="#docker-stubrunner">6.3. Running Stubs on the Consumer Side</a></li>
+</ul>
+</li>
+<li><a href="#contract-customization">7. Spring Cloud Contract customization</a>
+<ul class="sectlevel2">
+<li><a href="#customization-customization">7.1. DSL Customization</a></li>
+<li><a href="#customization-wiremock">7.2. WireMock Customization</a></li>
+<li><a href="#customization-pluggable-architecture">7.3. Using the Pluggable Architecture</a></li>
+</ul>
+</li>
+<li><a href="#howto">8. &#8220;How-to&#8221; Guides</a>
+<ul class="sectlevel2">
+<li><a href="#why-spring-cloud-contract">8.1. Why use Spring Cloud Contract?</a></li>
+<li><a href="#how-to-not-write-contracts-in-groovy">8.2. How Can I Write Contracts in a Language Other than Groovy?</a></li>
+<li><a href="#how-to-provide-dynamic-values">8.3. How Can I Provide Dynamic Values to a Contract?</a></li>
+<li><a href="#how-to-do-stubs-versioning">8.4. How to Do Stubs versioning?</a></li>
+<li><a href="#how-to-common-repo-with-contracts">8.5. How Can I use a Common Repository with Contracts Instead of Storing Them with the Producer?</a></li>
+<li><a href="#how-to-use-git-as-storage">8.6. How Can I Use Git as the Storage for Contracts and Stubs?</a></li>
+<li><a href="#how-to-use-pact-broker">8.7. How Can I Use the Pact Broker?</a></li>
+<li><a href="#how-to-debug">8.8. How Can I Debug the Request/Response Being Sent by the Generated Tests Client?</a></li>
+<li><a href="#how-to-debug-wiremock">8.9. How Can I Debug the Mapping, Request, or Response Being Sent by WireMock?</a></li>
+<li><a href="#how-to-see-registered-stubs">8.10. How Can I See What Got Registered in the HTTP Server Stub?</a></li>
+<li><a href="#how-to-reference-text-from-file">8.11. How Can I Reference Text from File?</a></li>
+<li><a href="#how-to-generate-pact-from-scc">8.12. How Can I Generate Pact, YAML, or X files from Spring Cloud Contract Contracts?</a></li>
+<li><a href="#how-to-work-with-transitivie">8.13. How Can I Work with Transitive Dependencies?</a></li>
+<li><a href="#contract-dsl-rest-docs">8.14. How can I Generate Spring REST Docs Snippets from the Contracts?</a></li>
+<li><a href="#how-to-use-stubs-from-a-location">8.15. How can I Use Stubs from a Location</a></li>
+<li><a href="#how-to-generate-stubs-at-runtime">8.16. How can I Generate Stubs at Runtime</a></li>
+<li><a href="#how-to-use-the-failonnostubs-feature">8.17. How can I Make The Build Pass if There Are No Contracts or Stubs</a></li>
+<li><a href="#how-to-mark-contract-in-progress">8.18. How can I Mark that a Contract Is in Progress</a></li>
+<li><a href="#common-application-properties">Appendix A: Common application properties</a></li>
+</ul>
+</li>
+</ul>
+</div>
+</div>
+<div id="content">
+<div class="sect1">
+<h2 id="legal"><a class="anchor" href="#legal"></a><a class="link" href="#legal">Legal</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>3.0.0-SNAPSHOT</p>
+</div>
+<div class="paragraph">
+<p>Copyright &#169; 2012-2020</p>
+</div>
+<div class="paragraph">
+<p>Copies of this document may be made for your own use and for distribution to
+others, provided that you do not charge any fee for such copies and further
+provided that each copy contains this Copyright Notice, whether distributed in
+print or electronically.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="getting-started"><a class="anchor" href="#getting-started"></a><a class="link" href="#getting-started">1. Getting Started</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>If you are getting started with Spring Cloud Contract, or Spring in general, start by reading
+this section. It answers the basic &#8220;what?&#8221;, &#8220;how?&#8221; and &#8220;why?&#8221; questions. It
+includes an introduction to Spring Cloud Contract, along with installation instructions. We then
+walk you through building your first Spring Cloud Contract application, discussing some core
+principles as we go.</p>
+</div>
+<div class="sect2">
+<h3 id="getting-started-introducing-spring-cloud-contract"><a class="anchor" href="#getting-started-introducing-spring-cloud-contract"></a><a class="link" href="#getting-started-introducing-spring-cloud-contract">1.1. Introducing Spring Cloud Contract</a></h3>
+<div class="paragraph">
+<p>Spring Cloud Contract moves TDD to the level of software architecture.
+It lets you perform consumer-driven and producer-driven contract testing.</p>
+</div>
+<div class="sect3">
+<h4 id="getting-started-introducing-spring-cloud-contract-history"><a class="anchor" href="#getting-started-introducing-spring-cloud-contract-history"></a><a class="link" href="#getting-started-introducing-spring-cloud-contract-history">1.1.1. History</a></h4>
+<div class="paragraph">
+<p>Before becoming Spring Cloud Contract, this project was called <a href="https://github.com/Codearte/accurest">Accurest</a>.
+It was created by <a href="https://twitter.com/mgrzejszczak">Marcin Grzejszczak</a> and <a href="https://twitter.com/jkubrynski">Jakub Kubrynski</a>
+from (<a href="https://github.com/Codearte">Codearte</a>).</p>
+</div>
+<div class="paragraph">
+<p>The <code>0.1.0</code> release took place on 26 Jan 2015 and it became stable with <code>1.0.0</code> release on 29 Feb 2016.</p>
+</div>
+<div class="sect4">
+<h5 id="getting-started-introducing-spring-cloud-contract-why"><a class="anchor" href="#getting-started-introducing-spring-cloud-contract-why"></a><a class="link" href="#getting-started-introducing-spring-cloud-contract-why">Why Do You Need It?</a></h5>
+<div class="paragraph">
+<p>Assume that we have a system that consists of multiple microservices, as the following
+image shows:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/Deps.png" alt="Microservices Architecture">
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="getting-started-introducing-spring-cloud-contract-testing-issues"><a class="anchor" href="#getting-started-introducing-spring-cloud-contract-testing-issues"></a><a class="link" href="#getting-started-introducing-spring-cloud-contract-testing-issues">Testing Issues</a></h5>
+<div class="paragraph">
+<p>If we want to test the application in the top left corner of the image in the preceding
+section to determine whether it can communicate with other services, we could do one of
+two things:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Deploy all microservices and perform end-to-end tests.</p>
+</li>
+<li>
+<p>Mock other microservices in unit and integration tests.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Both have their advantages but also a lot of disadvantages.</p>
+</div>
+<div class="paragraph">
+<p><strong>Deploy all microservices and perform end to end tests</strong></p>
+</div>
+<div class="paragraph">
+<p>Advantages:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Simulates production.</p>
+</li>
+<li>
+<p>Tests real communication between services.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Disadvantages:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>To test one microservice, we have to deploy six microservices, a couple of databases,
+and other items.</p>
+</li>
+<li>
+<p>The environment where the tests run is locked for a single suite of tests (nobody else
+would be able to run the tests in the meantime).</p>
+</li>
+<li>
+<p>They take a long time to run.</p>
+</li>
+<li>
+<p>The feedback comes very late in the process.</p>
+</li>
+<li>
+<p>They are extremely hard to debug.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p><strong>Mock other microservices in unit and integration tests</strong></p>
+</div>
+<div class="paragraph">
+<p>Advantages:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>They provide very fast feedback.</p>
+</li>
+<li>
+<p>They have no infrastructure requirements.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Disadvantages:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>The implementor of the service creates stubs that might have nothing to do with
+reality.</p>
+</li>
+<li>
+<p>You can go to production with passing tests and failing production.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>To solve the aforementioned issues, Spring Cloud Contract was created. The main idea is to
+give you very fast feedback, without the need to set up the
+whole world of microservices. If you work on stubs, then the only applications you need
+are those that your application directly uses. The following image shows the relationship
+of stubs to an application:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/Stubs2.png" alt="Stubbed Services">
+</div>
+</div>
+<div class="paragraph">
+<p>Spring Cloud Contract gives you the certainty that the stubs that you use were
+created by the service that you call. Also, if you can use them, it means that they
+were tested against the producer&#8217;s side. In short, you can trust those stubs.</p>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="getting-started-introducing-spring-cloud-contract-purposes"><a class="anchor" href="#getting-started-introducing-spring-cloud-contract-purposes"></a><a class="link" href="#getting-started-introducing-spring-cloud-contract-purposes">1.1.2. Purposes</a></h4>
+<div class="paragraph">
+<p>The main purposes of Spring Cloud Contract are:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>To ensure that HTTP and Messaging stubs (used when developing the client) do exactly
+what the actual server-side implementation does.</p>
+</li>
+<li>
+<p>To promote the ATDD (acceptance test-driven developement) method and the microservices architectural style.</p>
+</li>
+<li>
+<p>To provide a way to publish changes in contracts that are immediately visible on both sides.</p>
+</li>
+<li>
+<p>To generate boilerplate test code to be used on the server side.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>By default, Spring Cloud Contract integrates with <a href="http://wiremock.org">Wiremock</a> as the HTTP server stub.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+Spring Cloud Contract&#8217;s purpose is NOT to start writing business
+features in the contracts. Assume that we have a business use case of fraud check. If a
+user can be a fraud for 100 different reasons, we would assume that you would create two
+contracts, one for the positive case and one for the negative case. Contract tests are
+used to test contracts between applications and not to simulate full behavior.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="getting-started-what-is-a-contract"><a class="anchor" href="#getting-started-what-is-a-contract"></a><a class="link" href="#getting-started-what-is-a-contract">1.1.3. What Is a Contract?</a></h4>
+<div class="paragraph">
+<p>As consumers of services, we need to define what exactly we want to achieve. We need to
+formulate our expectations. That is why we write contracts. In other words, a contract is
+an agreement on how the API or message communication should look. Consider the following example:</p>
+</div>
+<div class="paragraph">
+<p>Assume that you want to send a request that contains the ID of a client company and the
+amount it wants to borrow from us. You also want to send it to the <code>/fraudcheck</code> URL via
+the <code>PUT</code> method. The following listing shows a contract to check whether a client should
+be marked as a fraud in both Groovy and YAML:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">/*
+ * Copyright 2013-2020 the original author or authors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *      https://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package contracts
+
+org.springframework.cloud.contract.spec.Contract.make {
+    request { // (1)
+        method 'PUT' // (2)
+        url '/fraudcheck' // (3)
+        body([ // (4)
+               "client.id": $(regex('[0-9]{10}')),
+               loanAmount : 99999
+        ])
+        headers { // (5)
+            contentType('application/json')
+        }
+    }
+    response { // (6)
+        status OK() // (7)
+        body([ // (8)
+               fraudCheckStatus  : "FRAUD",
+               "rejection.reason": "Amount too high"
+        ])
+        headers { // (9)
+            contentType('application/json')
+        }
+    }
+}
+
+/*
+From the Consumer perspective, when shooting a request in the integration test:
+
+(1) - If the consumer sends a request
+(2) - With the "PUT" method
+(3) - to the URL "/fraudcheck"
+(4) - with the JSON body that
+ * has a field `client.id` that matches a regular expression `[0-9]{10}`
+ * has a field `loanAmount` that is equal to `99999`
+(5) - with header `Content-Type` equal to `application/json`
+(6) - then the response will be sent with
+(7) - status equal `200`
+(8) - and JSON body equal to
+ { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
+(9) - with header `Content-Type` equal to `application/json`
+
+From the Producer perspective, in the autogenerated producer-side test:
+
+(1) - A request will be sent to the producer
+(2) - With the "PUT" method
+(3) - to the URL "/fraudcheck"
+(4) - with the JSON body that
+ * has a field `client.id` that will have a generated value that matches a regular expression `[0-9]{10}`
+ * has a field `loanAmount` that is equal to `99999`
+(5) - with header `Content-Type` equal to `application/json`
+(6) - then the test will assert if the response has been sent with
+(7) - status equal `200`
+(8) - and JSON body equal to
+ { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
+(9) - with header `Content-Type` matching `application/json.*`
+ */</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yaml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">request: # (1)
+  method: PUT # (2)
+  url: /yamlfraudcheck # (3)
+  body: # (4)
+    "client.id": 1234567890
+    loanAmount: 99999
+  headers: # (5)
+    Content-Type: application/json
+  matchers:
+    body:
+      - path: $.['client.id'] # (6)
+        type: by_regex
+        value: "[0-9]{10}"
+response: # (7)
+  status: 200 # (8)
+  body:  # (9)
+    fraudCheckStatus: "FRAUD"
+    "rejection.reason": "Amount too high"
+  headers: # (10)
+    Content-Type: application/json
+
+
+#From the Consumer perspective, when shooting a request in the integration test:
+#
+#(1) - If the consumer sends a request
+#(2) - With the "PUT" method
+#(3) - to the URL "/yamlfraudcheck"
+#(4) - with the JSON body that
+# * has a field `client.id`
+# * has a field `loanAmount` that is equal to `99999`
+#(5) - with header `Content-Type` equal to `application/json`
+#(6) - and a `client.id` json entry matches the regular expression `[0-9]{10}`
+#(7) - then the response will be sent with
+#(8) - status equal `200`
+#(9) - and JSON body equal to
+# { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
+#(10) - with header `Content-Type` equal to `application/json`
+#
+#From the Producer perspective, in the autogenerated producer-side test:
+#
+#(1) - A request will be sent to the producer
+#(2) - With the "PUT" method
+#(3) - to the URL "/yamlfraudcheck"
+#(4) - with the JSON body that
+# * has a field `client.id` `1234567890`
+# * has a field `loanAmount` that is equal to `99999`
+#(5) - with header `Content-Type` equal to `application/json`
+#(7) - then the test will assert if the response has been sent with
+#(8) - status equal `200`
+#(9) - and JSON body equal to
+# { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
+#(10) - with header `Content-Type` equal to `application/json`</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="getting-started-three-second-tour"><a class="anchor" href="#getting-started-three-second-tour"></a><a class="link" href="#getting-started-three-second-tour">1.2. A Three-second Tour</a></h3>
+<div class="paragraph">
+<p>This very brief tour walks through using Spring Cloud Contract. It consists of the
+following topics:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="#getting-started-three-second-tour-producer">On the Producer Side</a></p>
+</li>
+<li>
+<p><a href="#getting-started-three-second-tour-consumer">On the Consumer Side</a></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>You can find a somewhat longer tour
+<a href="#getting-started-first-application">here</a>.</p>
+</div>
+<div class="paragraph">
+<p>The following UML diagram shows the relationship of the parts within Spring Cloud Contract:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/getting-started-three-second.png" alt="getting started three second" width="986" height="704">
+</div>
+</div>
+<div class="sect3">
+<h4 id="getting-started-three-second-tour-producer"><a class="anchor" href="#getting-started-three-second-tour-producer"></a><a class="link" href="#getting-started-three-second-tour-producer">1.2.1. On the Producer Side</a></h4>
+<div class="paragraph">
+<p>To start working with Spring Cloud Contract, you can add files with REST or messaging contracts
+expressed in either Groovy DSL or YAML to the contracts directory, which is set by the
+<code>contractsDslDir</code> property. By default, it is <code>$rootDir/src/test/resources/contracts</code>.</p>
+</div>
+<div class="paragraph">
+<p>Then you can add the Spring Cloud Contract Verifier dependency and plugin to your build file, as
+the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-starter-contract-verifier&lt;/artifactId&gt;
+    &lt;scope&gt;test&lt;/scope&gt;
+&lt;/dependency&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following listing shows how to add the plugin, which should go in the build/plugins
+portion of the file:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Running <code>./mvnw clean install</code> automatically generates tests that verify the application
+compliance with the added contracts. By default, the tests get generated under
+<code>org.springframework.cloud.contract.verifier.tests.</code>.</p>
+</div>
+<div class="paragraph">
+<p>As the implementation of the functionalities described by the contracts is not yet
+present, the tests fail.</p>
+</div>
+<div class="paragraph">
+<p>To make them pass, you must add the correct implementation of either handling HTTP
+requests or messages. Also, you must add a base test class for auto-generated
+tests to the project. This class is extended by all the auto-generated tests, and it
+should contain all the setup information necessary to run them (for example <code>RestAssuredMockMvc</code>
+controller setup or messaging test setup).</p>
+</div>
+<div class="paragraph">
+<p>The following example, from <code>pom.xml</code>, shows how to specify the base test class:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre>&lt;build&gt;
+        &lt;plugins&gt;
+            &lt;plugin&gt;
+                &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+                &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+                &lt;version&gt;2.1.2.RELEASE&lt;/version&gt;
+                &lt;extensions&gt;true&lt;/extensions&gt;
+                &lt;configuration&gt;
+                    &lt;baseClassForTests&gt;com.example.contractTest.BaseTestClass&lt;/baseClassForTests&gt; <i class="conum" data-value="1"></i><b>(1)</b>
+                &lt;/configuration&gt;
+            &lt;/plugin&gt;
+            &lt;plugin&gt;
+                &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
+                &lt;artifactId&gt;spring-boot-maven-plugin&lt;/artifactId&gt;
+            &lt;/plugin&gt;
+        &lt;/plugins&gt;
+    &lt;/build&gt;</pre>
+</div>
+</div>
+<div class="colist arabic">
+<table>
+<tr>
+<td><i class="conum" data-value="1"></i><b>1</b></td>
+<td>The <code>baseClassForTests</code> element lets you specify your base test class. It must be a child
+of a <code>configuration</code> element within <code>spring-cloud-contract-maven-plugin</code>.</td>
+</tr>
+</table>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Once the implementation and the test base class are in place, the tests pass, and both the
+application and the stub artifacts are built and installed in the local Maven repository.
+You can now merge the changes, and you can publish both the application and the stub artifacts
+in an online repository.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="getting-started-three-second-tour-consumer"><a class="anchor" href="#getting-started-three-second-tour-consumer"></a><a class="link" href="#getting-started-three-second-tour-consumer">1.2.2. On the Consumer Side</a></h4>
+<div class="paragraph">
+<p>You can use <code>Spring Cloud Contract Stub Runner</code> in the integration tests to get a running
+WireMock instance or messaging route that simulates the actual service.</p>
+</div>
+<div class="paragraph">
+<p>To do so, add the dependency to <code>Spring Cloud Contract Stub Runner</code>, as the
+following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-starter-contract-stub-runner&lt;/artifactId&gt;
+    &lt;scope&gt;test&lt;/scope&gt;
+&lt;/dependency&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You can get the Producer-side stubs installed in your Maven repository in either of two
+ways:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>By checking out the Producer side repository and adding contracts and generating the stubs
+by running the following commands:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ cd local-http-server-repo
+$ ./mvnw clean install -DskipTests</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+The tests are being skipped because the producer-side contract implementation is not
+in place yet, so the automatically-generated contract tests fail.
+</td>
+</tr>
+</table>
+</div>
+</li>
+<li>
+<p>By getting already-existing producer service stubs from a remote repository. To do so,
+pass the stub artifact IDs and artifact repository URL as <code>Spring Cloud Contract
+Stub Runner</code> properties, as the following example shows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">stubrunner:
+  ids: 'com.example:http-server-dsl:+:stubs:8080'
+  repositoryRoot: https://repo.spring.io/libs-snapshot</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Now you can annotate your test class with <code>@AutoConfigureStubRunner</code>. In the annotation,
+provide the <code>group-id</code> and <code>artifact-id</code> values for <code>Spring Cloud Contract Stub Runner</code> to
+run the collaborators' stubs for you, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
+@SpringBootTest(webEnvironment=WebEnvironment.NONE)
+@AutoConfigureStubRunner(ids = {"com.example:http-server-dsl:+:stubs:6565"},
+        stubsMode = StubRunnerProperties.StubsMode.LOCAL)
+public class LoanApplicationServiceTests {</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+Use the <code>REMOTE</code> <code>stubsMode</code> when downloading stubs from an online repository and
+<code>LOCAL</code> for offline work.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>Now, in your integration test, you can receive stubbed versions of HTTP responses or
+messages that are expected to be emitted by the collaborator service.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="getting-started-first-application"><a class="anchor" href="#getting-started-first-application"></a><a class="link" href="#getting-started-first-application">1.3. Developing Your First Spring Cloud Contract-based Application</a></h3>
+<div class="paragraph">
+<p>This brief tour walks through using Spring Cloud Contract. It consists of the following topics:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="#getting-started-first-application-producer">On the Producer Side</a></p>
+</li>
+<li>
+<p><a href="#getting-started-first-application-consumer">On the Consumer Side</a></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>You can find an even more brief tour
+<a href="#getting-started-three-second-tour">here</a>.</p>
+</div>
+<div class="paragraph">
+<p>For the sake of this example, the <code>Stub Storage</code> is Nexus/Artifactory.</p>
+</div>
+<div class="paragraph">
+<p>The following UML diagram shows the relationship of the parts of Spring Cloud Contract:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/getting-started-three-second.png" alt="Getting started first application">
+</div>
+</div>
+<div class="sect3">
+<h4 id="getting-started-first-application-producer"><a class="anchor" href="#getting-started-first-application-producer"></a><a class="link" href="#getting-started-first-application-producer">1.3.1. On the Producer Side</a></h4>
+<div class="paragraph">
+<p>To start working with <code>Spring Cloud Contract</code>, you can add Spring Cloud Contract Verifier
+dependency and plugin to your build file, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-starter-contract-verifier&lt;/artifactId&gt;
+    &lt;scope&gt;test&lt;/scope&gt;
+&lt;/dependency&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following listing shows how to add the plugin, which should go in the build/plugins
+portion of the file:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+<div class="paragraph">
+<p>The easiest way to get started is to go to <a href="https://start.spring.io">the Spring Initializr</a>
+and add &#8220;Web&#8221; and &#8220;Contract Verifier&#8221; as dependencies. Doing so pulls in the previously
+mentioned dependencies and everything else you need in the <code>pom.xml</code> file (except for
+setting the base test class, which we cover later in this section). The following image
+shows the settings to use in <a href="https://start.spring.io">the Spring Initializr</a>:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/start_spring_io_dependencies.png" alt="Spring Initializr with Web and Contract Verifier" width="800">
+</div>
+</div>
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>Now you can add files with <code>REST/</code> messaging contracts
+expressed in either Groovy DSL or YAML to the contracts directory, which is set by the
+<code>contractsDslDir</code> property. By default, it is <code>$rootDir/src/test/resources/contracts</code>.
+Note that the file name does not matter. You can organize your contracts within this
+directory with whatever naming scheme you like.</p>
+</div>
+<div class="paragraph">
+<p>For the HTTP stubs, a contract defines what kind of response should be returned for a
+given request (taking into account the HTTP methods, URLs, headers, status codes, and so
+on). The following example shows an HTTP stub contract in both Groovy and YAML:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package contracts
+
+org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        method 'PUT'
+        url '/fraudcheck'
+        body([
+               "client.id": $(regex('[0-9]{10}')),
+               loanAmount: 99999
+        ])
+        headers {
+            contentType('application/json')
+        }
+    }
+    response {
+        status OK()
+        body([
+               fraudCheckStatus: "FRAUD",
+               "rejection.reason": "Amount too high"
+        ])
+        headers {
+            contentType('application/json')
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yaml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">request:
+  method: PUT
+  url: /fraudcheck
+  body:
+    "client.id": 1234567890
+    loanAmount: 99999
+  headers:
+    Content-Type: application/json
+  matchers:
+    body:
+      - path: $.['client.id']
+        type: by_regex
+        value: "[0-9]{10}"
+response:
+  status: 200
+  body:
+    fraudCheckStatus: "FRAUD"
+    "rejection.reason": "Amount too high"
+  headers:
+    Content-Type: application/json;charset=UTF-8</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>If you need to use messaging, you can define:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>The input and output messages (taking into account from and where it
+was sent, the message body, and the header).</p>
+</li>
+<li>
+<p>The methods that should be called after the message is received.</p>
+</li>
+<li>
+<p>The methods that, when called, should trigger a message.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The following example shows a Camel messaging contract:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">def contractDsl = Contract.make {
+    name "foo"
+    label 'some_label'
+    input {
+        messageFrom('jms:delete')
+        messageBody([
+                bookName: 'foo'
+        ])
+        messageHeaders {
+            header('sample', 'header')
+        }
+        assertThat('bookWasDeleted()')
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yaml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">label: some_label
+input:
+  messageFrom: jms:delete
+  messageBody:
+    bookName: 'foo'
+  messageHeaders:
+    sample: header
+  assertThat: bookWasDeleted()</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Running <code>./mvnw clean install</code> automatically generates tests that verify the application
+compliance with the added contracts. By default, the generated tests are under
+<code>org.springframework.cloud.contract.verifier.tests.</code>.</p>
+</div>
+<div class="paragraph">
+<p>The generated tests may differ, depending on which framework and test type you have setup
+in your plugin.</p>
+</div>
+<div class="paragraph">
+<p>In the next listing, you can find:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>The default test mode for HTTP contracts in <code>MockMvc</code></p>
+</li>
+<li>
+<p>A JAX-RS client with the <code>JAXRS</code> test mode</p>
+</li>
+<li>
+<p>A <code>WebTestClient</code>-based test (this is particularly recommended while working with
+Reactive, <code>Web-Flux</code>-based applications) set with the <code>WEBTESTCLIENT</code> test mode</p>
+</li>
+<li>
+<p>A Spock-based test with the <code>testFramework</code> property set to <code>SPOCK</code></p>
+</li>
+</ul>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+You need only one of these test frameworks. MockMvc is the default. To use one
+of the other frameworks, add its library to your classpath.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The following listing shows samples for all frameworks:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">mockmvc</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Test
+public void validate_shouldMarkClientAsFraud() throws Exception {
+    // given:
+        MockMvcRequestSpecification request = given()
+                .header("Content-Type", "application/vnd.fraud.v1+json")
+                .body("{\"client.id\":\"1234567890\",\"loanAmount\":99999}");
+
+    // when:
+        ResponseOptions response = given().spec(request)
+                .put("/fraudcheck");
+
+    // then:
+        assertThat(response.statusCode()).isEqualTo(200);
+        assertThat(response.header("Content-Type")).matches("application/vnd.fraud.v1.json.*");
+    // and:
+        DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
+        assertThatJson(parsedJson).field("['fraudCheckStatus']").matches("[A-Z]{5}");
+        assertThatJson(parsedJson).field("['rejection.reason']").isEqualTo("Amount too high");
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">jaxrs</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@SuppressWarnings("rawtypes")
+public class FooTest {
+  WebTarget webTarget;
+
+  @Test
+  public void validate_() throws Exception {
+
+    // when:
+      Response response = webTarget
+              .path("/users")
+              .queryParam("limit", "10")
+              .queryParam("offset", "20")
+              .queryParam("filter", "email")
+              .queryParam("sort", "name")
+              .queryParam("search", "55")
+              .queryParam("age", "99")
+              .queryParam("name", "Denis.Stepanov")
+              .queryParam("email", "bob@email.com")
+              .request()
+              .build("GET")
+              .invoke();
+      String responseAsString = response.readEntity(String.class);
+
+    // then:
+      assertThat(response.getStatus()).isEqualTo(200);
+
+    // and:
+      DocumentContext parsedJson = JsonPath.parse(responseAsString);
+      assertThatJson(parsedJson).field("['property1']").isEqualTo("a");
+  }
+
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">webtestclient</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Test
+    public void validate_shouldRejectABeerIfTooYoung() throws Exception {
+        // given:
+            WebTestClientRequestSpecification request = given()
+                    .header("Content-Type", "application/json")
+                    .body("{\"age\":10}");
+
+        // when:
+            WebTestClientResponse response = given().spec(request)
+                    .post("/check");
+
+        // then:
+            assertThat(response.statusCode()).isEqualTo(200);
+            assertThat(response.header("Content-Type")).matches("application/json.*");
+        // and:
+            DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
+            assertThatJson(parsedJson).field("['status']").isEqualTo("NOT_OK");
+    }</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">spock</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">given:
+     ContractVerifierMessage inputMessage = contractVerifierMessaging.create(
+        \'\'\'{"bookName":"foo"}\'\'\',
+        ['sample': 'header']
+    )
+
+when:
+     contractVerifierMessaging.send(inputMessage, 'jms:delete')
+
+then:
+     noExceptionThrown()
+     bookWasDeleted()</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>As the implementation of the functionalities described by the contracts is not yet
+present, the tests fail.</p>
+</div>
+<div class="paragraph">
+<p>To make them pass, you must add the correct implementation of handling either HTTP
+requests or messages. Also, you must add a base test class for auto-generated
+tests to the project. This class is extended by all the auto-generated tests and should
+contain all the setup necessary information needed to run them (for example,
+<code>RestAssuredMockMvc</code> controller setup or messaging test setup).</p>
+</div>
+<div class="paragraph">
+<p>The following example, from <code>pom.xml</code>, shows how to specify the base test class:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre>&lt;build&gt;
+        &lt;plugins&gt;
+            &lt;plugin&gt;
+                &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+                &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+                &lt;version&gt;2.1.2.RELEASE&lt;/version&gt;
+                &lt;extensions&gt;true&lt;/extensions&gt;
+                &lt;configuration&gt;
+                    &lt;baseClassForTests&gt;com.example.contractTest.BaseTestClass&lt;/baseClassForTests&gt; <i class="conum" data-value="1"></i><b>(1)</b>
+                &lt;/configuration&gt;
+            &lt;/plugin&gt;
+            &lt;plugin&gt;
+                &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
+                &lt;artifactId&gt;spring-boot-maven-plugin&lt;/artifactId&gt;
+            &lt;/plugin&gt;
+        &lt;/plugins&gt;
+    &lt;/build&gt;</pre>
+</div>
+</div>
+<div class="colist arabic">
+<table>
+<tr>
+<td><i class="conum" data-value="1"></i><b>1</b></td>
+<td>The <code>baseClassForTests</code> element lets you specify your base test class. It must be a child
+of a <code>configuration</code> element within <code>spring-cloud-contract-maven-plugin</code>.</td>
+</tr>
+</table>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following example shows a minimal (but functional) base test class:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre>package com.example.contractTest;
+
+import org.junit.Before;
+
+import io.restassured.module.mockmvc.RestAssuredMockMvc;
+
+public class BaseTestClass {
+
+    @Before
+    public void setup() {
+        RestAssuredMockMvc.standaloneSetup(new FraudController());
+    }
+}</pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>This minimal class really is all you need to get your tests to work. It serves as a
+starting place to which the automatically generated tests attach.</p>
+</div>
+<div class="paragraph">
+<p>Now we can move on to the implementation. For that, we first need a data class, which we
+then use in our controller. The following listing shows the data class:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre>package com.example.Test;
+
+import com.fasterxml.jackson.annotation.JsonProperty;
+
+public class LoanRequest {
+
+    @JsonProperty("client.id")
+    private String clientId;
+
+    private Long loanAmount;
+
+    public String getClientId() {
+        return clientId;
+    }
+
+    public void setClientId(String clientId) {
+        this.clientId = clientId;
+    }
+
+    public Long getLoanAmount() {
+        return loanAmount;
+    }
+
+    public void setLoanRequestAmount(Long loanAmount) {
+        this.loanAmount = loanAmount;
+    }
+}</pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The preceding class provides an object in which we can store the parameters. Because the
+client ID in the contract is called <code>client.id</code>, we need to use the
+<code>@JsonProperty("client.id")</code> parameter to map it to the <code>clientId</code> field.</p>
+</div>
+<div class="paragraph">
+<p>Now we can move along to the controller, which the following listing shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre>package com.example.docTest;
+
+import org.springframework.web.bind.annotation.PutMapping;
+import org.springframework.web.bind.annotation.RequestBody;
+import org.springframework.web.bind.annotation.RestController;
+
+@RestController
+public class FraudController {
+
+    @PutMapping(value = "/fraudcheck", consumes="application/json", produces="application/json")
+    public String check(@RequestBody LoanRequest loanRequest) { <i class="conum" data-value="1"></i><b>(1)</b>
+
+        if (loanRequest.getLoanAmount() &gt; 10000) { <i class="conum" data-value="2"></i><b>(2)</b>
+            return "{fraudCheckStatus: FRAUD, rejection.reason: Amount too high}"; <i class="conum" data-value="3"></i><b>(3)</b>
+        } else {
+            return "{fraudCheckStatus: OK, acceptance.reason: Amount OK}"; <i class="conum" data-value="4"></i><b>(4)</b>
+        }
+    }
+}</pre>
+</div>
+</div>
+<div class="colist arabic">
+<table>
+<tr>
+<td><i class="conum" data-value="1"></i><b>1</b></td>
+<td>We map the incoming parameters to a <code>LoanRequest</code> object.</td>
+</tr>
+<tr>
+<td><i class="conum" data-value="2"></i><b>2</b></td>
+<td>We check the requested loan amount to see if it is too much.</td>
+</tr>
+<tr>
+<td><i class="conum" data-value="3"></i><b>3</b></td>
+<td>If it is too much, we return the JSON (created with a simple string here) that the
+test expects.</td>
+</tr>
+<tr>
+<td><i class="conum" data-value="4"></i><b>4</b></td>
+<td>If we had a test to catch when the amount is allowable, we could match it to this output.</td>
+</tr>
+</table>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The <code>FraudController</code> is about as simple as things get. You can do much more, including
+logging, validating the client ID, and so on.</p>
+</div>
+<div class="paragraph">
+<p>Once the implementation and the test base class are in place, the tests pass, and both the
+application and the stub artifacts are built and installed in the local Maven repository
+Information about installing the stubs jar to the local repository appears in the logs, as
+the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">[INFO] --- spring-cloud-contract-maven-plugin:1.0.0.BUILD-SNAPSHOT:generateStubs (default-generateStubs) @ http-server ---
+[INFO] Building jar: /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar
+[INFO]
+[INFO] --- maven-jar-plugin:2.6:jar (default-jar) @ http-server ---
+[INFO] Building jar: /some/path/http-server/target/http-server-0.0.1-SNAPSHOT.jar
+[INFO]
+[INFO] --- spring-boot-maven-plugin:1.5.5.BUILD-SNAPSHOT:repackage (default) @ http-server ---
+[INFO]
+[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ http-server ---
+[INFO] Installing /some/path/http-server/target/http-server-0.0.1-SNAPSHOT.jar to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT.jar
+[INFO] Installing /some/path/http-server/pom.xml to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT.pom
+[INFO] Installing /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You can now merge the changes and publish both the application and the stub artifacts
+in an online repository.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="getting-started-first-application-consumer"><a class="anchor" href="#getting-started-first-application-consumer"></a><a class="link" href="#getting-started-first-application-consumer">1.3.2. On the Consumer Side</a></h4>
+<div class="paragraph">
+<p>You can use Spring Cloud Contract Stub Runner in the integration tests to get a running
+WireMock instance or messaging route that simulates the actual service.</p>
+</div>
+<div class="paragraph">
+<p>To get started, add the dependency to <code>Spring Cloud Contract Stub Runner</code>, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-starter-contract-stub-runner&lt;/artifactId&gt;
+    &lt;scope&gt;test&lt;/scope&gt;
+&lt;/dependency&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You can get the Producer-side stubs installed in your Maven repository in either of two
+ways:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>By checking out the Producer side repository and adding contracts and generating the
+stubs by running the following commands:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ cd local-http-server-repo
+$ ./mvnw clean install -DskipTests</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+The tests are skipped because the Producer-side contract implementation is not yet
+in place, so the automatically-generated contract tests fail.
+</td>
+</tr>
+</table>
+</div>
+</li>
+<li>
+<p>Getting already existing producer service stubs from a remote repository. To do so,
+pass the stub artifact IDs and artifact repository URl as <code>Spring Cloud Contract Stub
+Runner</code> properties, as the following example shows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">stubrunner:
+  ids: 'com.example:http-server-dsl:+:stubs:8080'
+  repositoryRoot: https://repo.spring.io/libs-snapshot</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Now you can annotate your test class with <code>@AutoConfigureStubRunner</code>. In the annotation,
+provide the <code>group-id</code> and <code>artifact-id</code> for <code>Spring Cloud Contract Stub Runner</code> to run
+the collaborators' stubs for you, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
+@SpringBootTest(webEnvironment=WebEnvironment.NONE)
+@AutoConfigureStubRunner(ids = {"com.example:http-server-dsl:+:stubs:6565"},
+        stubsMode = StubRunnerProperties.StubsMode.LOCAL)
+public class LoanApplicationServiceTests {</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+Use the <code>REMOTE</code> <code>stubsMode</code> when downloading stubs from an online repository and
+<code>LOCAL</code> for offline work.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>In your integration test, you can receive stubbed versions of HTTP responses or messages
+that are expected to be emitted by the collaborator service. You can see entries similar
+to the following in the build logs:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">2016-07-19 14:22:25.403  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Desired version is + - will try to resolve the latest version
+2016-07-19 14:22:25.438  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Resolved version is 0.0.1-SNAPSHOT
+2016-07-19 14:22:25.439  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Resolving artifact com.example:http-server:jar:stubs:0.0.1-SNAPSHOT using remote repositories []
+2016-07-19 14:22:25.451  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Resolved artifact com.example:http-server:jar:stubs:0.0.1-SNAPSHOT to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar
+2016-07-19 14:22:25.465  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Unpacking stub from JAR [URI: file:/path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar]
+2016-07-19 14:22:25.475  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Unpacked file to [/var/folders/0p/xwq47sq106x1_g3dtv6qfm940000gq/T/contracts100276532569594265]
+2016-07-19 14:22:27.737  INFO 41050 --- [           main] o.s.c.c.stubrunner.StubRunnerExecutor    : All stubs are now running RunningStubs [namesAndPorts={com.example:http-server:0.0.1-SNAPSHOT:stubs=8080}]</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="getting-started-cdc"><a class="anchor" href="#getting-started-cdc"></a><a class="link" href="#getting-started-cdc">1.4. Step-by-step Guide to Consumer Driven Contracts (CDC) with Contracts on the Producer Side</a></h3>
+<div class="paragraph">
+<p>Consider an example of fraud detection and the loan issuance process. The business
+scenario is such that we want to issue loans to people but do not want them to steal from
+us. The current implementation of our system grants loans to everybody.</p>
+</div>
+<div class="paragraph">
+<p>Assume that <code>Loan Issuance</code> is a client to the <code>Fraud Detection</code> server. In the current
+sprint, we must develop a new feature: if a client wants to borrow too much money,
+we mark the client as a fraud.</p>
+</div>
+<div class="paragraph">
+<p>Technical remarks</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Fraud Detection has an <code>artifact-id</code> of <code>http-server</code></p>
+</li>
+<li>
+<p>Loan Issuance has an artifact-id of <code>http-client</code></p>
+</li>
+<li>
+<p>Both have a <code>group-id</code> of <code>com.example</code></p>
+</li>
+<li>
+<p>For the sake of this example the <code>Stub Storage</code> is Nexus/Artifactory</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Social remarks</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Both the client and the server development teams need to communicate directly and
+discuss changes while going through the process</p>
+</li>
+<li>
+<p>CDC is all about communication</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x///opt/jenkins/data/workspace/spring-cloud-contract-master-ci/samples/standalone/dsl/http-server">server-side
+code is available here</a> and <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x///opt/jenkins/data/workspace/spring-cloud-contract-master-ci/samples/standalone/dsl/http-client">the client code  is available here</a>.</p>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+In this case, the producer owns the contracts. Physically, all of the contracts are
+in the producer&#8217;s repository.
+</td>
+</tr>
+</table>
+</div>
+<div class="sect3">
+<h4 id="getting-started-cdc-technical-note"><a class="anchor" href="#getting-started-cdc-technical-note"></a><a class="link" href="#getting-started-cdc-technical-note">1.4.1. Technical Note</a></h4>
+<div class="paragraph">
+<p>If you use the SNAPSHOT, Milestone, or Release Candidate versions you need to add the
+following section to your build:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;repositories&gt;
+    &lt;repository&gt;
+        &lt;id&gt;spring-snapshots&lt;/id&gt;
+        &lt;name&gt;Spring Snapshots&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;true&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/repository&gt;
+    &lt;repository&gt;
+        &lt;id&gt;spring-milestones&lt;/id&gt;
+        &lt;name&gt;Spring Milestones&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;false&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/repository&gt;
+    &lt;repository&gt;
+        &lt;id&gt;spring-releases&lt;/id&gt;
+        &lt;name&gt;Spring Releases&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;false&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/repository&gt;
+&lt;/repositories&gt;
+&lt;pluginRepositories&gt;
+    &lt;pluginRepository&gt;
+        &lt;id&gt;spring-snapshots&lt;/id&gt;
+        &lt;name&gt;Spring Snapshots&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;true&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/pluginRepository&gt;
+    &lt;pluginRepository&gt;
+        &lt;id&gt;spring-milestones&lt;/id&gt;
+        &lt;name&gt;Spring Milestones&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;false&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/pluginRepository&gt;
+    &lt;pluginRepository&gt;
+        &lt;id&gt;spring-releases&lt;/id&gt;
+        &lt;name&gt;Spring Releases&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;false&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/pluginRepository&gt;
+&lt;/pluginRepositories&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">repositories {
+    mavenCentral()
+    mavenLocal()
+    maven { url "https://repo.spring.io/snapshot" }
+    maven { url "https://repo.spring.io/milestone" }
+    maven { url "https://repo.spring.io/release" }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>For simplicity, we use the following acronyms:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Loan Issuance (LI): The HTTP client</p>
+</li>
+<li>
+<p>Fraud Detection (FD): The HTTP server</p>
+</li>
+<li>
+<p>Spring Cloud Contract (SCC)</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="getting-started-cdc-consumer"><a class="anchor" href="#getting-started-cdc-consumer"></a><a class="link" href="#getting-started-cdc-consumer">1.4.2. The Consumer Side (Loan Issuance)</a></h4>
+<div class="paragraph">
+<p>As a developer of the Loan Issuance service (a consumer of the Fraud Detection server), you might do the following steps:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Start doing TDD by writing a test for your feature.</p>
+</li>
+<li>
+<p>Write the missing implementation.</p>
+</li>
+<li>
+<p>Clone the Fraud Detection service repository locally.</p>
+</li>
+<li>
+<p>Define the contract locally in the repo of the fraud detection service.</p>
+</li>
+<li>
+<p>Add the Spring Cloud Contract (SCC) plugin.</p>
+</li>
+<li>
+<p>Run the integration tests.</p>
+</li>
+<li>
+<p>File a pull request.</p>
+</li>
+<li>
+<p>Create an initial implementation.</p>
+</li>
+<li>
+<p>Take over the pull request.</p>
+</li>
+<li>
+<p>Write the missing implementation.</p>
+</li>
+<li>
+<p>Deploy your app.</p>
+</li>
+<li>
+<p>Work online.</p>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>We start with the loan issuance flow, which the following UML diagram shows:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/getting-started-cdc-client.png" alt="getting started cdc client" width="1138" height="1223">
+</div>
+</div>
+<div class="sect4">
+<h5 id="getting-started-cdc-consumer-start"><a class="anchor" href="#getting-started-cdc-consumer-start"></a><a class="link" href="#getting-started-cdc-consumer-start">Start Doing TDD by Writing a Test for Your Feature</a></h5>
+<div class="paragraph">
+<p>The following listing shows a test that we might use to check whether a loan amount is too
+large:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@Test
+public void shouldBeRejectedDueToAbnormalLoanAmount() {
+    // given:
+    LoanApplication application = new LoanApplication(new Client("1234567890"),
+            99999);
+    // when:
+    LoanApplicationResult loanApplication = service.loanApplication(application);
+    // then:
+    assertThat(loanApplication.getLoanApplicationStatus())
+            .isEqualTo(LoanApplicationStatus.LOAN_APPLICATION_REJECTED);
+    assertThat(loanApplication.getRejectionReason()).isEqualTo("Amount too high");
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Assume that you have written a test of your new feature. If a loan application for a big
+amount is received, the system should reject that loan application with some description.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="getting-started-cdc-consumer-write"><a class="anchor" href="#getting-started-cdc-consumer-write"></a><a class="link" href="#getting-started-cdc-consumer-write">Write the Missing Implementation</a></h5>
+<div class="paragraph">
+<p>At some point in time, you need to send a request to the Fraud Detection service. Assume
+that you need to send the request containing the ID of the client and the amount the
+client wants to borrow. You want to send it to the <code>/fraudcheck</code> URL by using the <code>PUT</code> method.
+To do so, you might use code similar to the following:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">ResponseEntity&lt;FraudServiceResponse&gt; response = restTemplate.exchange(
+        "http://localhost:" + port + "/fraudcheck", HttpMethod.PUT,
+        new HttpEntity&lt;&gt;(request, httpHeaders), FraudServiceResponse.class);</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>For simplicity, the port of the Fraud Detection service is set to <code>8080</code>, and the
+application runs on <code>8090</code>.</p>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+If you start the test at this point, it breaks, because no service currently runs on port
+<code>8080</code>.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect4">
+<h5 id="getting-started-cdc-consumer-clone"><a class="anchor" href="#getting-started-cdc-consumer-clone"></a><a class="link" href="#getting-started-cdc-consumer-clone">Clone the Fraud Detection service repository locally</a></h5>
+<div class="paragraph">
+<p>You can start by playing around with the server side contract. To do so, you must first
+clone it, by running the following command:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ git clone https://your-git-server.com/server-side.git local-http-server-repo</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="getting-started-cdc-consumer-define"><a class="anchor" href="#getting-started-cdc-consumer-define"></a><a class="link" href="#getting-started-cdc-consumer-define">Define the Contract Locally in the Repository of the Fraud Detection Service</a></h5>
+<div class="paragraph">
+<p>As a consumer, you need to define what exactly you want to achieve. You need to formulate
+your expectations. To do so, write the following contract:</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+Place the contract in the <code>src/test/resources/contracts/fraud</code> folder. The <code>fraud</code> folder
+is important because the producer&#8217;s test base class name references that folder.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The following example shows our contract, in both Groovy and YAML:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">/*
+ * Copyright 2013-2020 the original author or authors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *      https://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package contracts
+
+org.springframework.cloud.contract.spec.Contract.make {
+    request { // (1)
+        method 'PUT' // (2)
+        url '/fraudcheck' // (3)
+        body([ // (4)
+               "client.id": $(regex('[0-9]{10}')),
+               loanAmount : 99999
+        ])
+        headers { // (5)
+            contentType('application/json')
+        }
+    }
+    response { // (6)
+        status OK() // (7)
+        body([ // (8)
+               fraudCheckStatus  : "FRAUD",
+               "rejection.reason": "Amount too high"
+        ])
+        headers { // (9)
+            contentType('application/json')
+        }
+    }
+}
+
+/*
+From the Consumer perspective, when shooting a request in the integration test:
+
+(1) - If the consumer sends a request
+(2) - With the "PUT" method
+(3) - to the URL "/fraudcheck"
+(4) - with the JSON body that
+ * has a field `client.id` that matches a regular expression `[0-9]{10}`
+ * has a field `loanAmount` that is equal to `99999`
+(5) - with header `Content-Type` equal to `application/json`
+(6) - then the response will be sent with
+(7) - status equal `200`
+(8) - and JSON body equal to
+ { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
+(9) - with header `Content-Type` equal to `application/json`
+
+From the Producer perspective, in the autogenerated producer-side test:
+
+(1) - A request will be sent to the producer
+(2) - With the "PUT" method
+(3) - to the URL "/fraudcheck"
+(4) - with the JSON body that
+ * has a field `client.id` that will have a generated value that matches a regular expression `[0-9]{10}`
+ * has a field `loanAmount` that is equal to `99999`
+(5) - with header `Content-Type` equal to `application/json`
+(6) - then the test will assert if the response has been sent with
+(7) - status equal `200`
+(8) - and JSON body equal to
+ { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
+(9) - with header `Content-Type` matching `application/json.*`
+ */</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yaml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">request: # (1)
+  method: PUT # (2)
+  url: /yamlfraudcheck # (3)
+  body: # (4)
+    "client.id": 1234567890
+    loanAmount: 99999
+  headers: # (5)
+    Content-Type: application/json
+  matchers:
+    body:
+      - path: $.['client.id'] # (6)
+        type: by_regex
+        value: "[0-9]{10}"
+response: # (7)
+  status: 200 # (8)
+  body:  # (9)
+    fraudCheckStatus: "FRAUD"
+    "rejection.reason": "Amount too high"
+  headers: # (10)
+    Content-Type: application/json
+
+
+#From the Consumer perspective, when shooting a request in the integration test:
+#
+#(1) - If the consumer sends a request
+#(2) - With the "PUT" method
+#(3) - to the URL "/yamlfraudcheck"
+#(4) - with the JSON body that
+# * has a field `client.id`
+# * has a field `loanAmount` that is equal to `99999`
+#(5) - with header `Content-Type` equal to `application/json`
+#(6) - and a `client.id` json entry matches the regular expression `[0-9]{10}`
+#(7) - then the response will be sent with
+#(8) - status equal `200`
+#(9) - and JSON body equal to
+# { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
+#(10) - with header `Content-Type` equal to `application/json`
+#
+#From the Producer perspective, in the autogenerated producer-side test:
+#
+#(1) - A request will be sent to the producer
+#(2) - With the "PUT" method
+#(3) - to the URL "/yamlfraudcheck"
+#(4) - with the JSON body that
+# * has a field `client.id` `1234567890`
+# * has a field `loanAmount` that is equal to `99999`
+#(5) - with header `Content-Type` equal to `application/json`
+#(7) - then the test will assert if the response has been sent with
+#(8) - status equal `200`
+#(9) - and JSON body equal to
+# { "fraudCheckStatus": "FRAUD", "rejectionReason": "Amount too high" }
+#(10) - with header `Content-Type` equal to `application/json`</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The YML contract is quite straightforward. However, when you take a look at the Contract
+written with a statically typed Groovy DSL, you might wonder what the
+<code>value(client(&#8230;&#8203;), server(&#8230;&#8203;))</code> parts are. By using this notation, Spring Cloud
+Contract lets you define parts of a JSON block, a URL, or other structure that is dynamic. In case
+of an identifier or a timestamp, you need not hardcode a value. You want to allow some
+different ranges of values. To enable ranges of values, you can set regular expressions
+that match those values for the consumer side. You can provide the body by means of either
+a map notation or String with interpolations. We highly recommend using the map notation.</p>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+You must understand the map notation in order to set up contracts. See the
+<a href="https://groovy-lang.org/json.html">Groovy docs regarding JSON</a>.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The previously shown contract is an agreement between two sides that:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>If an HTTP request is sent with all of</p>
+<div class="ulist">
+<ul>
+<li>
+<p>A <code>PUT</code> method on the <code>/fraudcheck</code> endpoint</p>
+</li>
+<li>
+<p>A JSON body with a <code>client.id</code> that matches the regular expression <code>[0-9]{10}</code> and
+<code>loanAmount</code> equal to <code>99999</code>,</p>
+</li>
+<li>
+<p>A <code>Content-Type</code> header with a value of <code>application/vnd.fraud.v1+json</code></p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>Then an HTTP response is sent to the consumer that</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Has status <code>200</code></p>
+</li>
+<li>
+<p>Contains a JSON body with the <code>fraudCheckStatus</code> field containing a value of <code>FRAUD</code> and
+the <code>rejectionReason</code> field having a value of <code>Amount too high</code></p>
+</li>
+<li>
+<p>Has a <code>Content-Type</code> header with a value of <code>application/vnd.fraud.v1+json</code></p>
+</li>
+</ul>
+</div>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Once you are ready to check the API in practice in the integration tests, you need to
+install the stubs locally.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="getting-started-cdc-consumer-add"><a class="anchor" href="#getting-started-cdc-consumer-add"></a><a class="link" href="#getting-started-cdc-consumer-add">Add the Spring Cloud Contract Verifier Plugin</a></h5>
+<div class="paragraph">
+<p>We can add either a Maven or a Gradle plugin. In this example, we show how to add Maven.
+First, we add the <code>Spring Cloud Contract</code> BOM, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependencyManagement&gt;
+    &lt;dependencies&gt;
+        &lt;dependency&gt;
+            &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+            &lt;artifactId&gt;spring-cloud-dependencies&lt;/artifactId&gt;
+            &lt;version&gt;${spring-cloud-release.version}&lt;/version&gt;
+            &lt;type&gt;pom&lt;/type&gt;
+            &lt;scope&gt;import&lt;/scope&gt;
+        &lt;/dependency&gt;
+    &lt;/dependencies&gt;
+&lt;/dependencyManagement&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Next, add the <code>Spring Cloud Contract Verifier</code> Maven plugin, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">            &lt;plugin&gt;
+                &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+                &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+                &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+                &lt;extensions&gt;true&lt;/extensions&gt;
+                &lt;configuration&gt;
+                    &lt;packageWithBaseClasses&gt;com.example.fraud&lt;/packageWithBaseClasses&gt;
+&lt;!--                    &lt;convertToYaml&gt;true&lt;/convertToYaml&gt;--&gt;
+                &lt;/configuration&gt;
+                &lt;!-- if additional dependencies are needed e.g. for Pact --&gt;
+                &lt;dependencies&gt;
+                    &lt;dependency&gt;
+                        &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+                        &lt;artifactId&gt;spring-cloud-contract-pact&lt;/artifactId&gt;
+                        &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+                    &lt;/dependency&gt;
+                &lt;/dependencies&gt;
+            &lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Since the plugin was added, you get the <code>Spring Cloud Contract Verifier</code> features, which,
+from the provided contracts:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Generate and run tests</p>
+</li>
+<li>
+<p>Produce and install stubs</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>You do not want to generate tests, since you, as the consumer, want only to play with the
+stubs. You need to skip the test generation and execution. To do so, run the following commands:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ cd local-http-server-repo
+$ ./mvnw clean install -DskipTests</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Once you run those commands, you should you see something like the following content in the logs:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">[INFO] --- spring-cloud-contract-maven-plugin:1.0.0.BUILD-SNAPSHOT:generateStubs (default-generateStubs) @ http-server ---
+[INFO] Building jar: /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar
+[INFO]
+[INFO] --- maven-jar-plugin:2.6:jar (default-jar) @ http-server ---
+[INFO] Building jar: /some/path/http-server/target/http-server-0.0.1-SNAPSHOT.jar
+[INFO]
+[INFO] --- spring-boot-maven-plugin:1.5.5.BUILD-SNAPSHOT:repackage (default) @ http-server ---
+[INFO]
+[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ http-server ---
+[INFO] Installing /some/path/http-server/target/http-server-0.0.1-SNAPSHOT.jar to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT.jar
+[INFO] Installing /some/path/http-server/pom.xml to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT.pom
+[INFO] Installing /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following line is extremely important:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">[INFO] Installing /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>It confirms that the stubs of the <code>http-server</code> have been installed in the local
+repository.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="getting-started-cdc-consumer-run"><a class="anchor" href="#getting-started-cdc-consumer-run"></a><a class="link" href="#getting-started-cdc-consumer-run">Running the Integration Tests</a></h5>
+<div class="paragraph">
+<p>In order to profit from the Spring Cloud Contract Stub Runner functionality of automatic
+stub downloading, you must do the following in your consumer side project (<code>Loan
+Application service</code>):</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Add the <code>Spring Cloud Contract</code> BOM, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependencyManagement&gt;
+    &lt;dependencies&gt;
+        &lt;dependency&gt;
+            &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+            &lt;artifactId&gt;spring-cloud-dependencies&lt;/artifactId&gt;
+            &lt;version&gt;${spring-cloud-release-train.version}&lt;/version&gt;
+            &lt;type&gt;pom&lt;/type&gt;
+            &lt;scope&gt;import&lt;/scope&gt;
+        &lt;/dependency&gt;
+    &lt;/dependencies&gt;
+&lt;/dependencyManagement&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Add the dependency to <code>Spring Cloud Contract Stub Runner</code>, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-starter-contract-stub-runner&lt;/artifactId&gt;
+    &lt;scope&gt;test&lt;/scope&gt;
+&lt;/dependency&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Annotate your test class with <code>@AutoConfigureStubRunner</code>. In the annotation, provide the
+<code>group-id</code> and <code>artifact-id</code> for the Stub Runner to download the stubs of your
+collaborators. (Optional step) Because you are playing with the collaborators offline, you
+can also provide the offline work switch (<code>StubRunnerProperties.StubsMode.LOCAL</code>).</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@SpringBootTest(webEnvironment = WebEnvironment.NONE)
+@AutoConfigureStubRunner(ids = {
+        "com.example:http-server-dsl:0.0.1:stubs" }, stubsMode = StubRunnerProperties.StubsMode.LOCAL)
+public class LoanApplicationServiceTests {</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>Now, when you run your tests, you see something like the following output in the logs:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">2016-07-19 14:22:25.403  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Desired version is + - will try to resolve the latest version
+2016-07-19 14:22:25.438  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Resolved version is 0.0.1-SNAPSHOT
+2016-07-19 14:22:25.439  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Resolving artifact com.example:http-server:jar:stubs:0.0.1-SNAPSHOT using remote repositories []
+2016-07-19 14:22:25.451  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Resolved artifact com.example:http-server:jar:stubs:0.0.1-SNAPSHOT to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar
+2016-07-19 14:22:25.465  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Unpacking stub from JAR [URI: file:/path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar]
+2016-07-19 14:22:25.475  INFO 41050 --- [           main] o.s.c.c.stubrunner.AetherStubDownloader  : Unpacked file to [/var/folders/0p/xwq47sq106x1_g3dtv6qfm940000gq/T/contracts100276532569594265]
+2016-07-19 14:22:27.737  INFO 41050 --- [           main] o.s.c.c.stubrunner.StubRunnerExecutor    : All stubs are now running RunningStubs [namesAndPorts={com.example:http-server:0.0.1-SNAPSHOT:stubs=8080}]</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>This output means that Stub Runner has found your stubs and started a server for your application
+with a group ID of <code>com.example</code> and an artifact ID of <code>http-server</code> with version <code>0.0.1-SNAPSHOT</code> of
+the stubs and with the <code>stubs</code> classifier on port <code>8080</code>.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="getting-started-cdc-consumer-file"><a class="anchor" href="#getting-started-cdc-consumer-file"></a><a class="link" href="#getting-started-cdc-consumer-file">Filing a Pull Request</a></h5>
+<div class="paragraph">
+<p>What you have done until now is an iterative process. You can play around with the
+contract, install it locally, and work on the consumer side until the contract works as
+you wish.</p>
+</div>
+<div class="paragraph">
+<p>Once you are satisfied with the results and the test passes, you can publish a pull request to
+the server side. Currently, the consumer side work is done.</p>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="getting-started-cdc-producer"><a class="anchor" href="#getting-started-cdc-producer"></a><a class="link" href="#getting-started-cdc-producer">1.4.3. The Producer Side (Fraud Detection server)</a></h4>
+<div class="paragraph">
+<p>As a developer of the Fraud Detection server (a server to the Loan Issuance service), you
+might want to do the following</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Take over the pull request</p>
+</li>
+<li>
+<p>Write the missing implementation</p>
+</li>
+<li>
+<p>Deploy the application</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The following UML diagram shows the fraud detection flow:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/getting-started-cdc-server.png" alt="getting started cdc server" width="688" height="903">
+</div>
+</div>
+<div class="sect4">
+<h5 id="getting-started-cdc-producer-pr"><a class="anchor" href="#getting-started-cdc-producer-pr"></a><a class="link" href="#getting-started-cdc-producer-pr">Taking over the Pull Request</a></h5>
+<div class="paragraph">
+<p>As a reminder, the following listing shows the initial implementation:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RequestMapping(value = "/fraudcheck", method = PUT)
+public FraudCheckResult fraudCheck(@RequestBody FraudCheck fraudCheck) {
+return new FraudCheckResult(FraudCheckStatus.OK, NO_REASON);
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Then you can run the following commands:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ git checkout -b contract-change-pr master
+$ git pull https://your-git-server.com/server-side-fork.git contract-change-pr</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You must add the dependencies needed by the autogenerated tests, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-starter-contract-verifier&lt;/artifactId&gt;
+    &lt;scope&gt;test&lt;/scope&gt;
+&lt;/dependency&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>In the configuration of the Maven plugin, you must pass the <code>packageWithBaseClasses</code> property, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">            &lt;plugin&gt;
+                &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+                &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+                &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+                &lt;extensions&gt;true&lt;/extensions&gt;
+                &lt;configuration&gt;
+                    &lt;packageWithBaseClasses&gt;com.example.fraud&lt;/packageWithBaseClasses&gt;
+&lt;!--                    &lt;convertToYaml&gt;true&lt;/convertToYaml&gt;--&gt;
+                &lt;/configuration&gt;
+                &lt;!-- if additional dependencies are needed e.g. for Pact --&gt;
+                &lt;dependencies&gt;
+                    &lt;dependency&gt;
+                        &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+                        &lt;artifactId&gt;spring-cloud-contract-pact&lt;/artifactId&gt;
+                        &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+                    &lt;/dependency&gt;
+                &lt;/dependencies&gt;
+            &lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+This example uses &#8220;convention-based&#8221; naming by setting the
+<code>packageWithBaseClasses</code> property. Doing so means that the two last packages combine to
+make the name of the base test class. In our case, the contracts were placed under
+<code>src/test/resources/contracts/fraud</code>. Since you do not have two packages starting from
+the <code>contracts</code> folder, pick only one, which should be <code>fraud</code>. Add the <code>Base</code> suffix and
+capitalize <code>fraud</code>. That gives you the <code>FraudBase</code> test class name.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>All the generated tests extend that class. Over there, you can set up your Spring Context
+or whatever is necessary. In this case, you should use <a href="https://github.com/rest-assured/rest-assured">Rest Assured MVC</a> to
+start the server side <code>FraudDetectionController</code>. The following listing shows the
+<code>FraudBase</code> class:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">/*
+ * Copyright 2013-2020 the original author or authors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *      https://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package com.example.fraud;
+
+import io.restassured.module.mockmvc.RestAssuredMockMvc;
+import org.junit.jupiter.api.BeforeEach;
+
+public class FraudBase {
+
+    @BeforeEach
+    public void setup() {
+        RestAssuredMockMvc.standaloneSetup(new FraudDetectionController(),
+                new FraudStatsController(stubbedStatsProvider()));
+    }
+
+    private StatsProvider stubbedStatsProvider() {
+        return fraudType -&gt; {
+            switch (fraudType) {
+            case DRUNKS:
+                return 100;
+            case ALL:
+                return 200;
+            }
+            return 0;
+        };
+    }
+
+    public void assertThatRejectionReasonIsNull(Object rejectionReason) {
+        assert rejectionReason == null;
+    }
+
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Now, if you run the <code>./mvnw clean install</code>, you get something like the following output:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">Results :
+
+Tests in error:
+  ContractVerifierTest.validate_shouldMarkClientAsFraud:32 » IllegalState Parsed...</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>This error occurs because you have a new contract from which a test was generated and it
+failed since you have not implemented the feature. The auto-generated test would look
+like the following test method:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Test
+public void validate_shouldMarkClientAsFraud() throws Exception {
+    // given:
+        MockMvcRequestSpecification request = given()
+                .header("Content-Type", "application/vnd.fraud.v1+json")
+                .body("{\"client.id\":\"1234567890\",\"loanAmount\":99999}");
+
+    // when:
+        ResponseOptions response = given().spec(request)
+                .put("/fraudcheck");
+
+    // then:
+        assertThat(response.statusCode()).isEqualTo(200);
+        assertThat(response.header("Content-Type")).matches("application/vnd.fraud.v1.json.*");
+    // and:
+        DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
+        assertThatJson(parsedJson).field("['fraudCheckStatus']").matches("[A-Z]{5}");
+        assertThatJson(parsedJson).field("['rejection.reason']").isEqualTo("Amount too high");
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>If you used the Groovy DSL, you can see that all of the <code>producer()</code> parts of the Contract that were present in the
+<code>value(consumer(&#8230;&#8203;), producer(&#8230;&#8203;))</code> blocks got injected into the test.
+In case of using YAML, the same applied for the <code>matchers</code> sections of the <code>response</code>.</p>
+</div>
+<div class="paragraph">
+<p>Note that, on the producer side, you are also doing TDD. The expectations are expressed
+in the form of a test. This test sends a request to our own application with the URL,
+headers, and body defined in the contract. It is also expecting precisely defined values
+in the response. In other words, you have the <code>red</code> part of <code>red</code>, <code>green</code>, and
+<code>refactor</code>. It is time to convert the <code>red</code> into the <code>green</code>.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="getting-started-cdc-producer-impl"><a class="anchor" href="#getting-started-cdc-producer-impl"></a><a class="link" href="#getting-started-cdc-producer-impl">Write the Missing Implementation</a></h5>
+<div class="paragraph">
+<p>Because you know the expected input and expected output, you can write the missing
+implementation as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RequestMapping(value = "/fraudcheck", method = PUT)
+public FraudCheckResult fraudCheck(@RequestBody FraudCheck fraudCheck) {
+if (amountGreaterThanThreshold(fraudCheck)) {
+    return new FraudCheckResult(FraudCheckStatus.FRAUD, AMOUNT_TOO_HIGH);
+}
+return new FraudCheckResult(FraudCheckStatus.OK, NO_REASON);
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>When you run <code>./mvnw clean install</code> again, the tests pass. Since the <code>Spring Cloud
+Contract Verifier</code> plugin adds the tests to the <code>generated-test-sources</code>, you can
+actually run those tests from your IDE.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="getting-started-cdc-producer-deploy"><a class="anchor" href="#getting-started-cdc-producer-deploy"></a><a class="link" href="#getting-started-cdc-producer-deploy">Deploying Your Application</a></h5>
+<div class="paragraph">
+<p>Once you finish your work, you can deploy your changes. To do so, you must first merge the
+branch by running the following commands:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ git checkout master
+$ git merge --no-ff contract-change-pr
+$ git push origin master</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Your CI might run something a command such as <code>./mvnw clean deploy</code>, which would publish both the
+application and the stub artifacts.</p>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="getting-started-cdc-consumer-final"><a class="anchor" href="#getting-started-cdc-consumer-final"></a><a class="link" href="#getting-started-cdc-consumer-final">1.4.4. Consumer Side (Loan Issuance), Final Step</a></h4>
+<div class="paragraph">
+<p>As a developer of the loan issuance service (a consumer of the Fraud Detection server), I want to:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Merge our feature branch to <code>master</code></p>
+</li>
+<li>
+<p>Switch to online mode of working</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The following UML diagram shows the final state of the process:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/getting-started-cdc-client-final.png" alt="getting started cdc client final" width="590" height="685">
+</div>
+</div>
+<div class="sect4">
+<h5 id="getting-started-cdc-consumer-final-merge"><a class="anchor" href="#getting-started-cdc-consumer-final-merge"></a><a class="link" href="#getting-started-cdc-consumer-final-merge">Merging a Branch to Master</a></h5>
+<div class="paragraph">
+<p>The following commands show one way to merge a branch into master with Git:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ git checkout master
+$ git merge --no-ff contract-change-pr</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="getting-started-cdc-consumer-final-online"><a class="anchor" href="#getting-started-cdc-consumer-final-online"></a><a class="link" href="#getting-started-cdc-consumer-final-online">Working Online</a></h5>
+<div class="paragraph">
+<p>Now you can disable the offline work for Spring Cloud Contract Stub Runner and indicate
+where the repository with your stubs is located. At this moment, the stubs of the server
+side are automatically downloaded from Nexus/Artifactory. You can set the value of
+<code>stubsMode</code> to <code>REMOTE</code>. The following code shows an example of
+achieving the same thing by changing the properties:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">stubrunner:
+  ids: 'com.example:http-server-dsl:+:stubs:8080'
+  repositoryRoot: https://repo.spring.io/libs-snapshot</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>That&#8217;s it. You have finished the tutorial.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="getting-started-whats-next"><a class="anchor" href="#getting-started-whats-next"></a><a class="link" href="#getting-started-whats-next">1.5. Next Steps</a></h3>
+<div class="paragraph">
+<p>Hopefully, this section provided some of the Spring Cloud Contract basics and got you on your way
+to writing your own applications. If you are a task-oriented type of developer, you might
+want to jump over to <a href="https://spring.io" class="bare">spring.io</a> and check out some of the
+<a href="https://spring.io/guides/">getting started</a> guides that solve specific &#8220;How do I do that
+with Spring?&#8221; problems. We also have Spring Cloud Contract-specific
+&#8220;<a href="#howto">how-to</a>&#8221; reference documentation.</p>
+</div>
+<div class="paragraph">
+<p>Otherwise, the next logical step is to read <a href="#using">Using Spring Cloud Contract</a>. If
+you are really impatient, you could also jump ahead and read about
+<a href="#project-features">Spring Cloud Contract features</a>.</p>
+</div>
+<div class="paragraph">
+<p>In addition to that you can check out the following videos:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>"Consumer Driven Contracts and Your Microservice Architecture" by Olga Maciaszek-Sharma and Marcin Grzejszczak</p>
+</li>
+</ul>
+</div>
+<div class="videoblock">
+<div class="content">
+<iframe width="640" height="480" src="https://www.youtube.com/embed/pDkC_00hhvA?rel=0" frameborder="0" allowfullscreen></iframe>
+</div>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>"Contract Tests in the Enterprise" by Marcin Grzejszczak</p>
+</li>
+</ul>
+</div>
+<div class="videoblock">
+<div class="content">
+<iframe width="640" height="480" src="https://www.youtube.com/embed/ZyHG-VOzPZg?rel=0" frameborder="0" allowfullscreen></iframe>
+</div>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>"Why Contract Tests Matter?" by Marcin Grzejszczak</p>
+</li>
+</ul>
+</div>
+<div class="videoblock">
+<div class="content">
+<iframe width="640" height="480" src="https://www.youtube.com/embed/TvpkZu1e2Dc?rel=0&amp;start=6262" frameborder="0" allowfullscreen></iframe>
+</div>
+</div>
+<div class="paragraph">
+<p>You can find the default project samples at
+<a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples">samples</a>.</p>
+</div>
+<div class="paragraph">
+<p>You can find the Spring Cloud Contract workshops <a href="https://cloud-samples.spring.io/spring-cloud-contract-samples/">here</a>.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="using"><a class="anchor" href="#using"></a><a class="link" href="#using">2. Using Spring Cloud Contract</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>This section goes into more detail about how you should use Spring Cloud Contract. It covers topics
+such as flows of how to work with Spring Cloud Contract. We also
+cover some Spring Cloud Contract best practices.</p>
+</div>
+<div class="paragraph">
+<p>If you are starting out with Spring Cloud Contract, you should probably read the
+<a href="#getting-started">Getting Started</a> guide before diving into this
+section.</p>
+</div>
+<div class="sect2">
+<h3 id="flows-provider-nexus"><a class="anchor" href="#flows-provider-nexus"></a><a class="link" href="#flows-provider-nexus">2.1. Provider Contract Testing with Stubs in Nexus or Artifactory</a></h3>
+<div class="paragraph">
+<p>You can check the <a href="#getting-started-first-application">Developing Your First Spring Cloud Contract based application</a> link to see the provider contract testing with stubs in the Nexus or Artifactory flow.</p>
+</div>
+<div class="paragraph">
+<p>You can also check the <a href="https://cloud-samples.spring.io/spring-cloud-contract-samples/tutorials/contracts_on_the_producer_side.html">workshop page</a> for a step-by-step instruction on how to do this flow.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="flows-provider-git"><a class="anchor" href="#flows-provider-git"></a><a class="link" href="#flows-provider-git">2.2. Provider Contract Testing with Stubs in Git</a></h3>
+<div class="paragraph">
+<p>In this flow, we perform the provider contract testing (the producer has no knowledge of how consumers use their API). The stubs are uploaded to a separate repository (they are not uploaded to Artifactory or Nexus).</p>
+</div>
+<div class="sect3">
+<h4 id="prerequisites"><a class="anchor" href="#prerequisites"></a><a class="link" href="#prerequisites">2.2.1. Prerequisites</a></h4>
+<div class="paragraph">
+<p>Before testing provider contracts with stubs in git, you must provide a git repository
+that contains all the stubs for each producer. For an example of such a project, see
+<a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x//contract_git">this samples </a> or <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x//contract_git">this sample</a>.
+As a result of pushing stubs there, the repository has the following structure:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre>$ tree .
+└── META-INF
+   └── folder.with.group.id.as.its.name
+       └── folder-with-artifact-id
+           └── folder-with-version
+               ├── contractA.groovy
+               ├── contractB.yml
+               └── contractC.groovy</pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You must also provide consumer code that has Spring Cloud Contract Stub Runner set up. For
+an example of such a project, see <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x//consumer">this sample</a> and search for a
+<code>BeerControllerGitTest</code> test. You must also provide producer code that has Spring Cloud
+Contract set up, together with a plugin. For an example of such a project, see
+<a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x//producer_with_empty_git">this sample</a>.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="flows-provider-git-flow"><a class="anchor" href="#flows-provider-git-flow"></a><a class="link" href="#flows-provider-git-flow">2.2.2. The Flow</a></h4>
+<div class="paragraph">
+<p>The flow looks exactly as the one presented in
+<a href="#getting-started-first-application">Developing Your First Spring Cloud Contract based application</a>,
+but the <code>Stub Storage</code> implementation is a git repository.</p>
+</div>
+<div class="paragraph">
+<p>You can read more about setting up a git repository and setting consumer and producer side
+in the <a href="#how-to-use-git-as-storage">How To page</a> of the documentation.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="flows-provider-git-consumer"><a class="anchor" href="#flows-provider-git-consumer"></a><a class="link" href="#flows-provider-git-consumer">2.2.3. Consumer setup</a></h4>
+<div class="paragraph">
+<p>In order to fetch the stubs from a git repository instead of Nexus or Artifactory, you
+need to use the <code>git</code> protocol in the URL of the <code>repositoryRoot</code> property in Stub Runner.
+The following example shows how to set it up:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Annotation</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(
+stubsMode = StubRunnerProperties.StubsMode.REMOTE,
+        repositoryRoot = "git://git@github.com:spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git",
+        ids = "com.example:artifact-id:0.0.1")</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">JUnit 4 Rule</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Rule
+    public StubRunnerRule rule = new StubRunnerRule()
+            .downloadStub("com.example","artifact-id", "0.0.1")
+            .repoRoot("git://git@github.com:spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git")
+            .stubsMode(StubRunnerProperties.StubsMode.REMOTE);</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">JUnit 5 Extension</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RegisterExtension
+    public StubRunnerExtension stubRunnerExtension = new StubRunnerExtension()
+            .downloadStub("com.example","artifact-id", "0.0.1")
+            .repoRoot("git://git@github.com:spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git")
+            .stubsMode(StubRunnerProperties.StubsMode.REMOTE);</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="flows-provider-git-producer"><a class="anchor" href="#flows-provider-git-producer"></a><a class="link" href="#flows-provider-git-producer">2.2.4. Setting up the Producer</a></h4>
+<div class="paragraph">
+<p>In order to push the stubs to a git repository instead of Nexus or Artifactory, you need
+to use the <code>git</code> protocol in the URL of the plugin setup. Also you need to explicitly tell
+the plugin to push the stubs at the end of the build process. The following example shows
+how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;!-- Base class mappings etc. --&gt;
+
+        &lt;!-- We want to pick contracts from a Git repository --&gt;
+        &lt;contractsRepositoryUrl&gt;git://git://git@github.com:spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git&lt;/contractsRepositoryUrl&gt;
+
+        &lt;!-- We reuse the contract dependency section to set up the path
+        to the folder that contains the contract definitions. In our case the
+        path will be /groupId/artifactId/version/contracts --&gt;
+        &lt;contractDependency&gt;
+            &lt;groupId&gt;${project.groupId}&lt;/groupId&gt;
+            &lt;artifactId&gt;${project.artifactId}&lt;/artifactId&gt;
+            &lt;version&gt;${project.version}&lt;/version&gt;
+        &lt;/contractDependency&gt;
+
+        &lt;!-- The contracts mode can't be classpath --&gt;
+        &lt;contractsMode&gt;REMOTE&lt;/contractsMode&gt;
+    &lt;/configuration&gt;
+    &lt;executions&gt;
+        &lt;execution&gt;
+            &lt;phase&gt;package&lt;/phase&gt;
+            &lt;goals&gt;
+                &lt;!-- By default we will not push the stubs back to SCM,
+                you have to explicitly add it as a goal --&gt;
+                &lt;goal&gt;pushStubsToScm&lt;/goal&gt;
+            &lt;/goals&gt;
+        &lt;/execution&gt;
+    &lt;/executions&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
+    // We want to pick contracts from a Git repository
+    contractDependency {
+        stringNotation = "${project.group}:${project.name}:${project.version}"
+    }
+    /*
+    We reuse the contract dependency section to set up the path
+    to the folder that contains the contract definitions. In our case the
+    path will be /groupId/artifactId/version/contracts
+     */
+    contractRepository {
+        repositoryUrl = "git://git://git@github.com:spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git"
+    }
+    // The mode can't be classpath
+    contractsMode = "REMOTE"
+    // Base class mappings etc.
+}
+
+/*
+In this scenario we want to publish stubs to SCM whenever
+the `publish` task is executed
+*/
+publish.dependsOn("publishStubsToScm")</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You can read more about setting up a git repository in the
+<a href="#how-to-use-git-as-storage">How To page</a> of the documentation.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="flows-cdc-contracts-producer"><a class="anchor" href="#flows-cdc-contracts-producer"></a><a class="link" href="#flows-cdc-contracts-producer">2.3. Consumer Driven Contracts with Contracts on the Producer Side</a></h3>
+<div class="paragraph">
+<p>See <a href="#getting-started-cdc">Step-by-step Guide to Consumer Driven
+Contracts (CDC) with Contracts on the Producer Side</a> to see the Consumer Driven Contracts
+with contracts on the producer side flow.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="flows-cdc-contracts-external"><a class="anchor" href="#flows-cdc-contracts-external"></a><a class="link" href="#flows-cdc-contracts-external">2.4. Consumer Driven Contracts with Contracts in an External Repository</a></h3>
+<div class="paragraph">
+<p>In this flow, we perform Consumer Driven Contract testing. The contract definitions are
+stored in a separate repository.</p>
+</div>
+<div class="paragraph">
+<p>See the <a href="https://cloud-samples.spring.io/spring-cloud-contract-samples/tutorials/contracts_on_the_producer_side.html">workshop page</a>
+for step-by-step instructions on how to do this flow.</p>
+</div>
+<div class="sect3">
+<h4 id="prerequisites-2"><a class="anchor" href="#prerequisites-2"></a><a class="link" href="#prerequisites-2">2.4.1. Prerequisites</a></h4>
+<div class="paragraph">
+<p>To use consumer-driven contracts with the contracts held in an external repository, you need to set up a git repository that:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Contains all the contract definitions for each producer.</p>
+</li>
+<li>
+<p>Can package the contract definitions in a JAR.</p>
+</li>
+<li>
+<p>For each contract producer, contains a way (for example, <code>pom.xml</code>) to install stubs
+locally through the Spring Cloud Contract Plugin (SCC Plugin)</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>For more information, see the <a href="#how-to-common-repo-with-contracts">How To section</a>,
+where we describe how to set up such a repository
+For an example of such a project, see <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x//beer_contracts">this sample</a>.</p>
+</div>
+<div class="paragraph">
+<p>You also need consumer code that has Spring Cloud Contract Stub Runner set up.
+For an example of such a project, see <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x//consumer">this sample</a>.
+You also need producer code that has Spring Cloud Contract set up, together with a plugin.
+For an example of such a project, see <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x//producer_with_external_contracts">this sample</a>.
+The stub storage is Nexus or Artifactory</p>
+</div>
+<div class="paragraph">
+<p>At a high level, the flow looks as follows:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>The consumer works with the contract definitions from the separate repository</p>
+</li>
+<li>
+<p>Once the consumer&#8217;s work is done, a branch with working code is done on the consumer
+side and a pull request is made to the separate repository that holds the contract definitions.</p>
+</li>
+<li>
+<p>The producer takes over the pull request to the separate repository with contract
+definitions and installs the JAR with all contracts locally.</p>
+</li>
+<li>
+<p>The producer generates tests from the locally stored JAR and writes the missing
+implementation to make the tests pass.</p>
+</li>
+<li>
+<p>Once the producer&#8217;s work is done, the pull request to the repository that holds the
+contract definitions is merged.</p>
+</li>
+<li>
+<p>After the CI tool builds the repository with the contract definitions and the JAR with
+contract definitions gets uploaded to Nexus or Artifactory, the producer can merge its branch.</p>
+</li>
+<li>
+<p>Finally, the consumer can switch to working online to fetch stubs of the producer from a
+remote location, and the branch can be merged to master.</p>
+</li>
+</ol>
+</div>
+</div>
+<div class="sect3">
+<h4 id="flows-cdc-contracts-external-consumer"><a class="anchor" href="#flows-cdc-contracts-external-consumer"></a><a class="link" href="#flows-cdc-contracts-external-consumer">2.4.2. Consumer Flow</a></h4>
+<div class="paragraph">
+<p>The consumer:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Writes a test that would send a request to the producer.</p>
+<div class="paragraph">
+<p>The test fails due to no server being present.</p>
+</div>
+</li>
+<li>
+<p>Clones the repository that holds the contract definitions.</p>
+</li>
+<li>
+<p>Set up the requirements as contracts under the folder with the consumer name as a subfolder of the producer.</p>
+<div class="paragraph">
+<p>For example, for a producer named <code>producer</code> and a consumer named <code>consumer</code>, the contracts would be stored under <code>src/main/resources/contracts/producer/consumer/</code>)</p>
+</div>
+</li>
+<li>
+<p>Once the contracts are defined, installs the producer stubs to local storage, as the following example shows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre>$ cd src/main/resource/contracts/producer
+$ ./mvnw clean install</pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Sets up Spring Cloud Contract (SCC) Stub Runner in the consumer tests, to:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Fetch the producer stubs from local storage.</p>
+</li>
+<li>
+<p>Work in the stubs-per-consumer mode (this enables consumer driven contracts mode).</p>
+<div class="paragraph">
+<p>The SCC Stub Runner:</p>
+</div>
+</li>
+<li>
+<p>Fetches the producer stubs.</p>
+</li>
+<li>
+<p>Runs an in-memory HTTP server stub with the producer stubs.</p>
+</li>
+<li>
+<p>Now your test communicates with the HTTP server stub and your tests pass</p>
+</li>
+<li>
+<p>Create a pull request to the repository with contract definitions, with the new contracts for the producer</p>
+</li>
+<li>
+<p>Branch your consumer code, until the producer team has merged their code</p>
+</li>
+</ul>
+</div>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>The following UML diagram shows the consumer flow:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/flow-overview-consumer-cdc-external-consumer.png" alt="flow overview consumer cdc external consumer" width="886" height="676">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="flows-cdc-contracts-external-producer"><a class="anchor" href="#flows-cdc-contracts-external-producer"></a><a class="link" href="#flows-cdc-contracts-external-producer">2.4.3. Producer Flow</a></h4>
+<div class="paragraph">
+<p>The producer:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Takes over the pull request to the repository with contract definitions. You can do it
+from the command line, as follows</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre>$ git checkout -b the_branch_with_pull_request master
+git pull https://github.com/user_id/project_name.git the_branch_with_pull_request</pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Installs the contract definitions, as follows</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre>$ ./mvnw clean install</pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Sets up the plugin to fetch the contract definitions from a JAR instead of from
+<code>src/test/resources/contracts</code>, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;!-- We want to use the JAR with contracts with the following coordinates --&gt;
+        &lt;contractDependency&gt;
+            &lt;groupId&gt;com.example&lt;/groupId&gt;
+            &lt;artifactId&gt;beer-contracts&lt;/artifactId&gt;
+        &lt;/contractDependency&gt;
+        &lt;!-- The JAR with contracts should be taken from Maven local --&gt;
+        &lt;contractsMode&gt;LOCAL&lt;/contractsMode&gt;
+        &lt;!-- ... additional configuration --&gt;
+    &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
+    // We want to use the JAR with contracts with the following coordinates
+    // group id `com.example`, artifact id `beer-contracts`, LATEST version and NO classifier
+    contractDependency {
+        stringNotation = 'com.example:beer-contracts:+:'
+    }
+    // The JAR with contracts should be taken from Maven local
+    contractsMode = "LOCAL"
+    // Additional configuration
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Runs the build to generate tests and stubs, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">./mvnw clean install</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">./gradlew clean build</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Writes the missing implementation, to make the tests pass.</p>
+</li>
+<li>
+<p>Merges the pull request to the repository with contract definitions, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre>$ git commit -am "Finished the implementation to make the contract tests pass"
+$ git checkout master
+$ git merge --no-ff the_branch_with_pull_request
+$ git push origin master</pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>The CI system builds the project with the contract definitions and uploads the JAR with
+the contract definitions to Nexus or Artifactory.</p>
+</li>
+<li>
+<p>Switches to working remotely.</p>
+</li>
+<li>
+<p>Sets up the plugin so that the contract definitions are no longer taken from the local
+storage but from a remote location, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;!-- We want to use the JAR with contracts with the following coordinates --&gt;
+        &lt;contractDependency&gt;
+            &lt;groupId&gt;com.example&lt;/groupId&gt;
+            &lt;artifactId&gt;beer-contracts&lt;/artifactId&gt;
+        &lt;/contractDependency&gt;
+        &lt;!-- The JAR with contracts should be taken from a remote location --&gt;
+        &lt;contractsMode&gt;REMOTE&lt;/contractsMode&gt;
+        &lt;!-- ... additional configuration --&gt;
+    &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
+    // We want to use the JAR with contracts with the following coordinates
+    // group id `com.example`, artifact id `beer-contracts`, LATEST version and NO classifier
+    contractDependency {
+        stringNotation = 'com.example:beer-contracts:+:'
+    }
+    // The JAR with contracts should be taken from a remote location
+    contractsMode = "REMOTE"
+    // Additional configuration
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Merges the producer code with the new implementation.</p>
+</li>
+<li>
+<p>The CI system:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Builds the project</p>
+</li>
+<li>
+<p>Generates tests, stubs, and the stub JAR</p>
+</li>
+<li>
+<p>Uploads the artifact with the application and the stubs to Nexus or Artifactory.</p>
+</li>
+</ul>
+</div>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>The following UML diagram shows the producer process:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/flow-overview-consumer-cdc-external-producer.png" alt="flow overview consumer cdc external producer" width="1213" height="1341">
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="flows-cdc-contracts-stubs-git"><a class="anchor" href="#flows-cdc-contracts-stubs-git"></a><a class="link" href="#flows-cdc-contracts-stubs-git">2.5. Consumer Driven Contracts with Contracts on the Producer Side, Pushed to Git</a></h3>
+<div class="paragraph">
+<p>You can check <a href="#getting-started-cdc">Step-by-step Guide to Consumer Driven Contracts (CDC) with contracts laying on the producer side</a> to see the consumer driven contracts with contracts on the producer side flow.</p>
+</div>
+<div class="paragraph">
+<p>The stub storage implementation is a git repository. We describe its setup in the
+<a href="#flows-provider-git">Provider Contract Testing with Stubs in Git</a> section.</p>
+</div>
+<div class="paragraph">
+<p>You can read more about setting up a git repository for the consumer and producer sides in
+the <a href="#how-to-use-git-as-storage">How To page</a> of the documentation.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="flows-provider-non-spring"><a class="anchor" href="#flows-provider-non-spring"></a><a class="link" href="#flows-provider-non-spring">2.6. Provider Contract Testing with Stubs in Artifactory for a non-Spring Application</a></h3>
+<div class="sect3">
+<h4 id="flows-provider-non-spring-flow"><a class="anchor" href="#flows-provider-non-spring-flow"></a><a class="link" href="#flows-provider-non-spring-flow">2.6.1. The Flow</a></h4>
+<div class="paragraph">
+<p>You can check <a href="#getting-started-first-application">Developing Your First Spring Cloud Contract based application</a> to see the flow for provider contract testing with stubs in Nexus or Artifactory.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="flows-provider-non-spring-consumer"><a class="anchor" href="#flows-provider-non-spring-consumer"></a><a class="link" href="#flows-provider-non-spring-consumer">2.6.2. Setting up the Consumer</a></h4>
+<div class="paragraph">
+<p>For the consumer side, you can use a JUnit rule. That way, you need not start a Spring context. The follwoing listing shows such a rule (in JUnit4 and JUnit 5);</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">JUnit 4 Rule</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Rule
+    public StubRunnerRule rule = new StubRunnerRule()
+            .downloadStub("com.example","artifact-id", "0.0.1")
+            .repoRoot("git://git@github.com:spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git")
+            .stubsMode(StubRunnerProperties.StubsMode.REMOTE);</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">JUnit 5 Extension</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Rule
+    public StubRunnerExtension stubRunnerExtension = new StubRunnerExtension()
+            .downloadStub("com.example","artifact-id", "0.0.1")
+            .repoRoot("git://git@github.com:spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git")
+            .stubsMode(StubRunnerProperties.StubsMode.REMOTE);</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="flows-provider-non-spring-producer"><a class="anchor" href="#flows-provider-non-spring-producer"></a><a class="link" href="#flows-provider-non-spring-producer">2.6.3. Setting up the Producer</a></h4>
+<div class="paragraph">
+<p>By default, the Spring Cloud Contract Plugin uses Rest Assured&#8217;s <code>MockMvc</code> setup for the
+generated tests. Since non-Spring applications do not use <code>MockMvc</code>, you can change the
+<code>testMode</code> to <code>EXPLICIT</code> to send a real request to an application bound at a specific port.</p>
+</div>
+<div class="paragraph">
+<p>In this example, we use a framework called <a href="https://javalin.io">Javalin</a> to start a
+non-Spring HTTP server.</p>
+</div>
+<div class="paragraph">
+<p>Assume that we have the following application:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package com.example.demo;
+
+import io.javalin.Javalin;
+
+public class DemoApplication {
+
+    public static void main(String[] args) {
+        new DemoApplication().run(7000);
+    }
+
+    public Javalin start(int port) {
+        return Javalin.create().start(port);
+    }
+
+    public Javalin registerGet(Javalin app) {
+        return app.get("/", ctx -&gt; ctx.result("Hello World"));
+    }
+
+    public Javalin run(int port) {
+        return registerGet(start(port));
+    }
+
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Given that application, we can set up the plugin to use the <code>EXPLICIT</code> mode (that is, to
+send out requests to a real port), as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;baseClassForTests&gt;com.example.demo.BaseClass&lt;/baseClassForTests&gt;
+        &lt;!-- This will setup the EXPLICIT mode for the tests --&gt;
+        &lt;testMode&gt;EXPLICIT&lt;/testMode&gt;
+    &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
+    // This will setup the EXPLICIT mode for the tests
+    testMode = "EXPLICIT"
+    baseClassForTests = "com.example.demo.BaseClass"
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The base class might resemble the following:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import io.javalin.Javalin;
+import io.restassured.RestAssured;
+import org.junit.After;
+import org.junit.Before;
+import org.springframework.util.SocketUtils;
+
+public class BaseClass {
+
+    Javalin app;
+
+    @Before
+    public void setup() {
+        // pick a random port
+        int port = SocketUtils.findAvailableTcpPort();
+        // start the application at a random port
+        this.app = start(port);
+        // tell Rest Assured where the started application is
+        RestAssured.baseURI = "http://localhost:" + port;
+    }
+
+    @After
+    public void close() {
+        // stop the server after each test
+        this.app.stop();
+    }
+
+    private Javalin start(int port) {
+        // reuse the production logic to start a server
+        return new DemoApplication().run(port);
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>With such a setup:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>We have setup the Spring Cloud Contract plugin to use the <code>EXPLICIT</code> mode to send real
+requests instead of mocked ones.</p>
+</li>
+<li>
+<p>We have defined a base class that:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Starts the HTTP server on a random port for each test.</p>
+</li>
+<li>
+<p>Sets Rest Assured to send requests to that port.</p>
+</li>
+<li>
+<p>Closes the HTTP server after each test.</p>
+</li>
+</ul>
+</div>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="flows-provider-non-jvm"><a class="anchor" href="#flows-provider-non-jvm"></a><a class="link" href="#flows-provider-non-jvm">2.7. Provider Contract Testing with Stubs in Artifactory in a non-JVM World</a></h3>
+<div class="paragraph">
+<p>In this flow, we assume that:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>The API Producer and API Consumer are non-JVM applications.</p>
+</li>
+<li>
+<p>The contract definitions are written in YAML.</p>
+</li>
+<li>
+<p>The Stub Storage is Artifactory or Nexus.</p>
+</li>
+<li>
+<p>Spring Cloud Contract Docker (SCC Docker) and Spring Cloud Contract Stub Runner Docker
+(SCC Stub Runner Docker) images are used.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>You can read more about how to use Spring Cloud Contract with Docker <a href="docker-project.html">in this page</a>.</p>
+</div>
+<div class="paragraph">
+<p><a href="https://spring.io/blog/2018/02/13/spring-cloud-contract-in-a-polyglot-world">Here</a>, you can
+read a blog post about how to use Spring Cloud Contract in a polyglot world.</p>
+</div>
+<div class="paragraph">
+<p><a href="https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs/">Here</a>, you can find
+a sample of a NodeJS application that uses Spring Cloud Contract both as a producer and a
+consumer.</p>
+</div>
+<div class="sect3">
+<h4 id="flows-provider-non-jvm-producer"><a class="anchor" href="#flows-provider-non-jvm-producer"></a><a class="link" href="#flows-provider-non-jvm-producer">2.7.1. Producer Flow</a></h4>
+<div class="paragraph">
+<p>At a high level, the producer:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Writes contract definitions (for example, in YAML).</p>
+</li>
+<li>
+<p>Sets up the build tool to:</p>
+<div class="olist loweralpha">
+<ol class="loweralpha" type="a">
+<li>
+<p>Start the application with mocked services on a given port.</p>
+<div class="paragraph">
+<p>If mocking is not possible, you can setup the infrastructure and define tests in a stateful way.</p>
+</div>
+</li>
+<li>
+<p>Run the Spring Cloud Contract Docker image and pass the port of a running application as an environment variable.</p>
+</li>
+</ol>
+</div>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>The SCC Docker image:
+* Generates the tests from the attached volume.
+* Runs the tests against the running application.</p>
+</div>
+<div class="paragraph">
+<p>Upon test completion, stubs get uploaded to a stub storage site (such as Artifactory or Git).</p>
+</div>
+<div class="paragraph">
+<p>The following UML diagram shows the producer flow:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/flows-provider-non-jvm-producer.png" alt="flows provider non jvm producer" width="930" height="810">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="flows-provider-non-jvm-consumer"><a class="anchor" href="#flows-provider-non-jvm-consumer"></a><a class="link" href="#flows-provider-non-jvm-consumer">2.7.2. Consumer Flow</a></h4>
+<div class="paragraph">
+<p>At a high level, the consumer:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Sets up the build tool to:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Start the Spring Cloud Contract Stub Runner Docker image and start the stubs.</p>
+<div class="paragraph">
+<p>The environment variables configure:</p>
+</div>
+</li>
+<li>
+<p>The stubs to fetch.</p>
+</li>
+<li>
+<p>The location of the repositories.</p>
+<div class="paragraph">
+<p>Note that:</p>
+</div>
+</li>
+<li>
+<p>To use the local storage, you can also attach it as a volume.</p>
+</li>
+<li>
+<p>The ports at which the stubs are running need to be exposed.</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>Run the application tests against the running stubs.</p>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>The following UML diagram shows the consumer flow:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/flows-provider-non-jvm-consumer.png" alt="flows provider non jvm consumer" width="815" height="618">
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="flows-provider-rest-docs"><a class="anchor" href="#flows-provider-rest-docs"></a><a class="link" href="#flows-provider-rest-docs">2.8. Provider Contract Testing with REST Docs and Stubs in Nexus or Artifactory</a></h3>
+<div class="paragraph">
+<p>In this flow, we do not use a Spring Cloud Contract plugin to generate tests and stubs. We write <a href="https://spring.io/projects/spring-restdocs">Spring RESTDocs</a> and, from them, we automatically generate stubs. Finally, we set up our builds to package the stubs and upload them to the stub storage site&#8201;&#8212;&#8201;in our case, Nexus or Artifactory.</p>
+</div>
+<div class="paragraph">
+<p>See the <a href="https://cloud-samples.spring.io/spring-cloud-contract-samples/tutorials/rest_docs.html">workshop page</a> for a step-by-step instruction on how to use this flow.</p>
+</div>
+<div class="sect3">
+<h4 id="flows-provider-rest-docs-producer"><a class="anchor" href="#flows-provider-rest-docs-producer"></a><a class="link" href="#flows-provider-rest-docs-producer">2.8.1. Producer Flow</a></h4>
+<div class="paragraph">
+<p>As a producer, we:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>We write RESTDocs tests of our API.</p>
+</li>
+<li>
+<p>We add Spring Cloud Contract Stub Runner starter to our build (<code>spring-cloud-starter-contract-stub-runner</code>), as follows</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependencies&gt;
+    &lt;dependency&gt;
+        &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+        &lt;artifactId&gt;spring-cloud-starter-contract-stub-runner&lt;/artifactId&gt;
+        &lt;scope&gt;test&lt;/scope&gt;
+    &lt;/dependency&gt;
+&lt;/dependencies&gt;
+
+&lt;dependencyManagement&gt;
+    &lt;dependencies&gt;
+        &lt;dependency&gt;
+            &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+            &lt;artifactId&gt;spring-cloud-dependencies&lt;/artifactId&gt;
+            &lt;version&gt;${spring-cloud.version}&lt;/version&gt;
+            &lt;type&gt;pom&lt;/type&gt;
+            &lt;scope&gt;import&lt;/scope&gt;
+        &lt;/dependency&gt;
+    &lt;/dependencies&gt;
+&lt;/dependencyManagement&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">dependencies {
+    testImplementation 'org.springframework.cloud:spring-cloud-starter-contract-stub-runner'
+}
+
+dependencyManagement {
+    imports {
+        mavenBom "org.springframework.cloud:spring-cloud-dependencies:${springCloudVersion}"
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>We set up the build tool to package our stubs, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;!-- pom.xml --&gt;
+&lt;plugins&gt;
+    &lt;plugin&gt;
+        &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
+        &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
+        &lt;executions&gt;
+            &lt;execution&gt;
+                &lt;id&gt;stub&lt;/id&gt;
+                &lt;phase&gt;prepare-package&lt;/phase&gt;
+                &lt;goals&gt;
+                    &lt;goal&gt;single&lt;/goal&gt;
+                &lt;/goals&gt;
+                &lt;inherited&gt;false&lt;/inherited&gt;
+                &lt;configuration&gt;
+                    &lt;attach&gt;true&lt;/attach&gt;
+                    &lt;descriptors&gt;
+                        ${basedir}/src/assembly/stub.xml
+                    &lt;/descriptors&gt;
+                &lt;/configuration&gt;
+            &lt;/execution&gt;
+        &lt;/executions&gt;
+    &lt;/plugin&gt;
+&lt;/plugins&gt;
+
+&lt;!-- src/assembly/stub.xml --&gt;
+&lt;assembly
+    xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3"
+    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3 http://maven.apache.org/xsd/assembly-1.1.3.xsd"&gt;
+    &lt;id&gt;stubs&lt;/id&gt;
+    &lt;formats&gt;
+        &lt;format&gt;jar&lt;/format&gt;
+    &lt;/formats&gt;
+    &lt;includeBaseDirectory&gt;false&lt;/includeBaseDirectory&gt;
+    &lt;fileSets&gt;
+        &lt;fileSet&gt;
+            &lt;directory&gt;${project.build.directory}/generated-snippets/stubs&lt;/directory&gt;
+            &lt;outputDirectory&gt;META-INF/${project.groupId}/${project.artifactId}/${project.version}/mappings&lt;/outputDirectory&gt;
+            &lt;includes&gt;
+                &lt;include&gt;**/*&lt;/include&gt;
+            &lt;/includes&gt;
+        &lt;/fileSet&gt;
+    &lt;/fileSets&gt;
+&lt;/assembly&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">task stubsJar(type: Jar) {
+    classifier = "stubs"
+    into("META-INF/${project.group}/${project.name}/${project.version}/mappings") {
+        include('**/*.*')
+        from("${project.buildDir}/generated-snippets/stubs")
+    }
+}
+// we need the tests to pass to build the stub jar
+stubsJar.dependsOn(test)
+bootJar.dependsOn(stubsJar)</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>Now, when we run the tests, stubs are automatically published and packaged.</p>
+</div>
+<div class="paragraph">
+<p>The following UML diagram shows the producer flow:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/flows-provider-rest-docs-producer.png" alt="flows provider rest docs producer" width="783" height="677">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="flows-provider-rest-docs-consumer"><a class="anchor" href="#flows-provider-rest-docs-consumer"></a><a class="link" href="#flows-provider-rest-docs-consumer">2.8.2. Consumer Flow</a></h4>
+<div class="paragraph">
+<p>Since the consumer flow is not affected by the tool used to generate the stubs, you can check <a href="#getting-started-first-application-consumer">Developing Your First Spring Cloud Contract based application</a> to see the flow for consumer side of the provider contract testing with stubs in Nexus or Artifactory.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="using-whats-next"><a class="anchor" href="#using-whats-next"></a><a class="link" href="#using-whats-next">2.9. What to Read Next</a></h3>
+<div class="paragraph">
+<p>You should now understand how you can use Spring Cloud Contract and some best practices that you
+should follow. You can now go on to learn about specific
+<a href="#project-features">Spring Cloud Contract features</a>, or you could
+skip ahead and read about the <a href="advanced.html">advanced features of Spring Cloud Contract</a>.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="features"><a class="anchor" href="#features"></a><a class="link" href="#features">3. Spring Cloud Contract Features</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>This section dives into the details of Spring Cloud Contract. Here you can learn about the key
+features that you may want to use and customize. If you have not already done so, you
+might want to read the "<a href="#getting-started">Getting Started</a>" and
+"<a href="#using">Using Spring Cloud Contract</a>" sections, so that you have a good grounding of the
+basics.</p>
+</div>
+<div class="sect2">
+<h3 id="contract-dsl"><a class="anchor" href="#contract-dsl"></a><a class="link" href="#contract-dsl">3.1. Contract DSL</a></h3>
+<div class="paragraph">
+<p>Spring Cloud Contract supports the DSLs written in the following languages:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Groovy</p>
+</li>
+<li>
+<p>YAML</p>
+</li>
+<li>
+<p>Java</p>
+</li>
+<li>
+<p>Kotlin</p>
+</li>
+</ul>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+Spring Cloud Contract supports defining multiple contracts in a single file.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The following example shows a contract definition:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        method 'PUT'
+        url '/api/12'
+        headers {
+            header 'Content-Type': 'application/vnd.org.springframework.cloud.contract.verifier.twitter-places-analyzer.v1+json'
+        }
+        body '''\
+    [{
+        "created_at": "Sat Jul 26 09:38:57 +0000 2014",
+        "id": 492967299297845248,
+        "id_str": "492967299297845248",
+        "text": "Gonna see you at Warsaw",
+        "place":
+        {
+            "attributes":{},
+            "bounding_box":
+            {
+                "coordinates":
+                    [[
+                        [-77.119759,38.791645],
+                        [-76.909393,38.791645],
+                        [-76.909393,38.995548],
+                        [-77.119759,38.995548]
+                    ]],
+                "type":"Polygon"
+            },
+            "country":"United States",
+            "country_code":"US",
+            "full_name":"Washington, DC",
+            "id":"01fbe706f872cb32",
+            "name":"Washington",
+            "place_type":"city",
+            "url": "https://api.twitter.com/1/geo/id/01fbe706f872cb32.json"
+        }
+    }]
+'''
+    }
+    response {
+        status OK()
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">description: Some description
+name: some name
+priority: 8
+ignored: true
+request:
+  url: /foo
+  queryParameters:
+    a: b
+    b: c
+  method: PUT
+  headers:
+    foo: bar
+    fooReq: baz
+  body:
+    foo: bar
+  matchers:
+    body:
+      - path: $.foo
+        type: by_regex
+        value: bar
+    headers:
+      - key: foo
+        regex: bar
+response:
+  status: 200
+  headers:
+    foo2: bar
+    foo3: foo33
+    fooRes: baz
+  body:
+    foo2: bar
+    foo3: baz
+    nullValue: null
+  matchers:
+    body:
+      - path: $.foo2
+        type: by_regex
+        value: bar
+      - path: $.foo3
+        type: by_command
+        value: executeMe($it)
+      - path: $.nullValue
+        type: by_null
+        value: null
+    headers:
+      - key: foo2
+        regex: bar
+      - key: foo3
+        command: andMeToo($it)</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import java.util.Collection;
+import java.util.Collections;
+import java.util.function.Supplier;
+
+import org.springframework.cloud.contract.spec.Contract;
+import org.springframework.cloud.contract.verifier.util.ContractVerifierUtil;
+
+class contract_rest implements Supplier&lt;Collection&lt;Contract&gt;&gt; {
+
+    @Override
+    public Collection&lt;Contract&gt; get() {
+        return Collections.singletonList(Contract.make(c -&gt; {
+            c.description("Some description");
+            c.name("some name");
+            c.priority(8);
+            c.ignored();
+            c.request(r -&gt; {
+                r.url("/foo", u -&gt; {
+                    u.queryParameters(q -&gt; {
+                        q.parameter("a", "b");
+                        q.parameter("b", "c");
+                    });
+                });
+                r.method(r.PUT());
+                r.headers(h -&gt; {
+                    h.header("foo", r.value(r.client(r.regex("bar")), r.server("bar")));
+                    h.header("fooReq", "baz");
+                });
+                r.body(ContractVerifierUtil.map().entry("foo", "bar"));
+                r.bodyMatchers(m -&gt; {
+                    m.jsonPath("$.foo", m.byRegex("bar"));
+                });
+            });
+            c.response(r -&gt; {
+                r.fixedDelayMilliseconds(1000);
+                r.status(r.OK());
+                r.headers(h -&gt; {
+                    h.header("foo2", r.value(r.server(r.regex("bar")), r.client("bar")));
+                    h.header("foo3", r.value(r.server(r.execute("andMeToo($it)")),
+                            r.client("foo33")));
+                    h.header("fooRes", "baz");
+                });
+                r.body(ContractVerifierUtil.map().entry("foo2", "bar")
+                        .entry("foo3", "baz").entry("nullValue", null));
+                r.bodyMatchers(m -&gt; {
+                    m.jsonPath("$.foo2", m.byRegex("bar"));
+                    m.jsonPath("$.foo3", m.byCommand("executeMe($it)"));
+                    m.jsonPath("$.nullValue", m.byNull());
+                });
+            });
+        }));
+    }
+
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">import org.springframework.cloud.contract.spec.ContractDsl.Companion.contract
+import org.springframework.cloud.contract.spec.withQueryParameters
+
+contract {
+    name = "some name"
+    description = "Some description"
+    priority = 8
+    ignored = true
+    request {
+        url = url("/foo") withQueryParameters  {
+            parameter("a", "b")
+            parameter("b", "c")
+        }
+        method = PUT
+        headers {
+            header("foo", value(client(regex("bar")), server("bar")))
+            header("fooReq", "baz")
+        }
+        body = body(mapOf("foo" to "bar"))
+        bodyMatchers {
+            jsonPath("$.foo", byRegex("bar"))
+        }
+    }
+    response {
+        delay = fixedMilliseconds(1000)
+        status = OK
+        headers {
+            header("foo2", value(server(regex("bar")), client("bar")))
+            header("foo3", value(server(execute("andMeToo(\$it)")), client("foo33")))
+            header("fooRes", "baz")
+        }
+        body = body(mapOf(
+                "foo" to "bar",
+                "foo3" to "baz",
+                "nullValue" to null
+        ))
+        bodyMatchers {
+            jsonPath("$.foo2", byRegex("bar"))
+            jsonPath("$.foo3", byCommand("executeMe(\$it)"))
+            jsonPath("$.nullValue", byNull)
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+<div class="paragraph">
+<p>You can compile contracts to stubs mapping by using  the following standalone Maven command:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>mvn org.springframework.cloud:spring-cloud-contract-maven-plugin:convert</pre>
+</div>
+</div>
+</td>
+</tr>
+</table>
+</div>
+<div class="sect3">
+<h4 id="contract-groovy"><a class="anchor" href="#contract-groovy"></a><a class="link" href="#contract-groovy">3.1.1. Contract DSL in Groovy</a></h4>
+<div class="paragraph">
+<p>If you are not familiar with Groovy, do not worry - you can use Java syntax in the
+Groovy DSL files as well.</p>
+</div>
+<div class="paragraph">
+<p>If you decide to write the contract in Groovy, do not be alarmed if you have not used Groovy
+before. Knowledge of the language is not really needed, as the Contract DSL uses only a
+tiny subset of it (only literals, method calls, and closures). Also, the DSL is statically
+typed, to make it programmer-readable without any knowledge of the DSL itself.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+Remember that, inside the Groovy contract file, you have to provide the fully
+qualified name to the <code>Contract</code> class and <code>make</code> static imports, such as
+<code>org.springframework.cloud.spec.Contract.make { &#8230;&#8203; }</code>. You can also provide an import to
+the <code>Contract</code> class (<code>import org.springframework.cloud.spec.Contract</code>) and then call
+<code>Contract.make { &#8230;&#8203; }</code>.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="contract-java"><a class="anchor" href="#contract-java"></a><a class="link" href="#contract-java">3.1.2. Contract DSL in Java</a></h4>
+<div class="paragraph">
+<p>To write a contract definition in Java, you need to create a class, that implements either the <code>Supplier&lt;Contract&gt;</code> interface for a single contract or <code>Supplier&lt;Collection&lt;Contract&gt;&gt;</code> for multiple contracts.</p>
+</div>
+<div class="paragraph">
+<p>You can also write the contract definitions under <code>src/test/java</code> (e.g. <code>src/test/java/contracts</code>) so that you don&#8217;t have to modify the classpath of your project. In this case you&#8217;ll have to provide a new location of contract definitions to your Spring Cloud Contract plugin.</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;contractsDirectory&gt;src/test/java/contracts&lt;/contractsDirectory&gt;
+    &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
+    contractsDslDir = new File(project.rootDir, "src/test/java/contracts")
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="contract-kotlin"><a class="anchor" href="#contract-kotlin"></a><a class="link" href="#contract-kotlin">3.1.3. Contract DSL in Kotlin</a></h4>
+<div class="paragraph">
+<p>To get started with writing contracts in Kotlin you would need to start with a (newly created) Kotlin Script file (.kts).
+Just like the with the Java DSL you can put your contracts in any directory of your choice.
+The Maven and Gradle plugins will look at the <code>src/test/resources/contracts</code> directory by default.</p>
+</div>
+<div class="paragraph">
+<p>You need to explicitly pass the the <code>spring-cloud-contract-spec-kotlin</code> dependency to your project plugin setup.</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;!-- some config --&gt;
+    &lt;/configuration&gt;
+    &lt;dependencies&gt;
+        &lt;dependency&gt;
+            &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+            &lt;artifactId&gt;spring-cloud-contract-spec-kotlin&lt;/artifactId&gt;
+            &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+        &lt;/dependency&gt;
+    &lt;/dependencies&gt;
+&lt;/plugin&gt;
+
+&lt;dependencies&gt;
+        &lt;!-- Remember to add this for the DSL support in the IDE and on the consumer side --&gt;
+        &lt;dependency&gt;
+            &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+            &lt;artifactId&gt;spring-cloud-contract-spec-kotlin&lt;/artifactId&gt;
+            &lt;scope&gt;test&lt;/scope&gt;
+        &lt;/dependency&gt;
+&lt;/dependencies&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">buildscript {
+    repositories {
+        // ...
+    }
+    dependencies {
+        classpath "org.springframework.cloud:spring-cloud-contract-gradle-plugin:${scContractVersion}"
+        // remember to add this:
+        classpath "org.springframework.cloud:spring-cloud-contract-spec-kotlin:${scContractVersion}"
+    }
+}
+
+dependencies {
+    // ...
+
+    // Remember to add this for the DSL support in the IDE and on the consumer side
+    testImplementation "org.springframework.cloud:spring-cloud-contract-spec-kotlin"
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+Remember that, inside the Kotlin Script file, you have to provide the fully qualified name to the <code>ContractDSL</code> class.
+Generally you would use its contract function like this: <code>org.springframework.cloud.contract.spec.ContractDsl.contract { &#8230;&#8203; }</code>.
+You can also provide an import to the <code>contract</code> function (<code>import org.springframework.cloud.contract.spec.ContractDsl.Companion.contract</code>) and then call <code>contract { &#8230;&#8203; }</code>.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="contract-yml"><a class="anchor" href="#contract-yml"></a><a class="link" href="#contract-yml">3.1.4. Contract DSL in YML</a></h4>
+<div class="paragraph">
+<p>In order to see a schema of a YAML contract, you can check out the <a href="yml-schema.html">YML Schema</a> page.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="contract-limitations"><a class="anchor" href="#contract-limitations"></a><a class="link" href="#contract-limitations">3.1.5. Limitations</a></h4>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-warning" title="Warning"></i>
+</td>
+<td class="content">
+The support for verifying the size of JSON arrays is experimental. If you want
+to turn it on, set the value of the following system property to <code>true</code>:
+<code>spring.cloud.contract.verifier.assert.size</code>. By default, this feature is set to <code>false</code>.
+You can also set the <code>assertJsonSize</code> property in the plugin configuration.
+</td>
+</tr>
+</table>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-warning" title="Warning"></i>
+</td>
+<td class="content">
+Because JSON structure can have any form, it can be impossible to parse it
+properly when using the Groovy DSL and the <code>value(consumer(&#8230;&#8203;), producer(&#8230;&#8203;))</code> notation in <code>GString</code>. That
+is why you should use the Groovy Map notation.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="contract-common-top-elements"><a class="anchor" href="#contract-common-top-elements"></a><a class="link" href="#contract-common-top-elements">3.1.6. Common Top-Level Elements</a></h4>
+<div class="paragraph">
+<p>The following sections describe the most common top-level elements:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="#contract-dsl-description">Description</a></p>
+</li>
+<li>
+<p><a href="#contract-dsl-name">Name</a></p>
+</li>
+<li>
+<p><a href="#contract-dsl-ignoring-contracts">Ignoring Contracts</a></p>
+</li>
+<li>
+<p><a href="#contract-dsl-in-progress">Contracts in Progress</a></p>
+</li>
+<li>
+<p><a href="#contract-dsl-passing-values-from-files">Passing Values from Files</a></p>
+</li>
+</ul>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-description"><a class="anchor" href="#contract-dsl-description"></a><a class="link" href="#contract-dsl-description">Description</a></h5>
+<div class="paragraph">
+<p>You can add a <code>description</code> to your contract. The description is arbitrary text. The
+following code shows an example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">            org.springframework.cloud.contract.spec.Contract.make {
+                description('''
+given:
+    An input
+when:
+    Sth happens
+then:
+    Output
+''')
+            }</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">description: Some description
+name: some name
+priority: 8
+ignored: true
+request:
+  url: /foo
+  queryParameters:
+    a: b
+    b: c
+  method: PUT
+  headers:
+    foo: bar
+    fooReq: baz
+  body:
+    foo: bar
+  matchers:
+    body:
+      - path: $.foo
+        type: by_regex
+        value: bar
+    headers:
+      - key: foo
+        regex: bar
+response:
+  status: 200
+  headers:
+    foo2: bar
+    foo3: foo33
+    fooRes: baz
+  body:
+    foo2: bar
+    foo3: baz
+    nullValue: null
+  matchers:
+    body:
+      - path: $.foo2
+        type: by_regex
+        value: bar
+      - path: $.foo3
+        type: by_command
+        value: executeMe($it)
+      - path: $.nullValue
+        type: by_null
+        value: null
+    headers:
+      - key: foo2
+        regex: bar
+      - key: foo3
+        command: andMeToo($it)</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">Contract.make(c -&gt; {
+    c.description("Some description");
+}));</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    description = """
+given:
+    An input
+when:
+    Sth happens
+then:
+    Output
+"""
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-name"><a class="anchor" href="#contract-dsl-name"></a><a class="link" href="#contract-dsl-name">Name</a></h5>
+<div class="paragraph">
+<p>You can provide a name for your contract. Assume that you provided the following name:
+<code>should register a user</code>. If you do so, the name of the autogenerated test is
+<code>validate_should_register_a_user</code>. Also, the name of the stub in a WireMock stub is
+<code>should_register_a_user.json</code>.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+You must ensure that the name does not contain any characters that make the
+generated test not compile. Also, remember that, if you provide the same name for
+multiple contracts, your autogenerated tests fail to compile and your generated stubs
+override each other.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The following example shows how to add a name to a contract:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    name("some_special_name")
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">name: some name</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">Contract.make(c -&gt; {
+    c.name("some name");
+}));</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    name = "some_special_name"
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-ignoring-contracts"><a class="anchor" href="#contract-dsl-ignoring-contracts"></a><a class="link" href="#contract-dsl-ignoring-contracts">Ignoring Contracts</a></h5>
+<div class="paragraph">
+<p>If you want to ignore a contract, you can either set a value for ignored contracts in the
+plugin configuration or set the <code>ignored</code> property on the contract itself. The following
+example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    ignored()
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">ignored: true</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">Contract.make(c -&gt; {
+    c.ignored();
+}));</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    ignored = true
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-in-progress"><a class="anchor" href="#contract-dsl-in-progress"></a><a class="link" href="#contract-dsl-in-progress">Contracts in Progress</a></h5>
+<div class="paragraph">
+<p>A contract in progress will not generate tests on the producer side, but will allow generation of stubs.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+Use this feature with caution as it may lead to false positives. You generate stubs for your consumers to use without actually having the implementation in place!
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>If you want to set a contract in progress the following
+example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    inProgress()
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">inProgress: true</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">Contract.make(c -&gt; {
+    c.inProgress();
+}));</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    inProgress = true
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You can set the value of the <code>failOnInProgress</code> Spring Cloud Contract plugin property to ensure that your build will break when at least one contract in progress remains in your sources.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-passing-values-from-files"><a class="anchor" href="#contract-dsl-passing-values-from-files"></a><a class="link" href="#contract-dsl-passing-values-from-files">Passing Values from Files</a></h5>
+<div class="paragraph">
+<p>Starting with version <code>1.2.0</code>, you can pass values from files. Assume that you have the
+following resources in your project:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── src
+    └── test
+        └── resources
+            └── contracts
+                ├── readFromFile.groovy
+                ├── request.json
+                └── response.json</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Further assume that your contract is as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">/*
+ * Copyright 2013-2020 the original author or authors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *      https://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+import org.springframework.cloud.contract.spec.Contract
+
+Contract.make {
+    request {
+        method('PUT')
+        headers {
+            contentType(applicationJson())
+        }
+        body(file("request.json"))
+        url("/1")
+    }
+    response {
+        status OK()
+        body(file("response.json"))
+        headers {
+            contentType(applicationJson())
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">request:
+  method: GET
+  url: /foo
+  bodyFromFile: request.json
+response:
+  status: 200
+  bodyFromFile: response.json</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import java.util.Collection;
+import java.util.Collections;
+import java.util.function.Supplier;
+
+import org.springframework.cloud.contract.spec.Contract;
+
+class contract_rest_from_file implements Supplier&lt;Collection&lt;Contract&gt;&gt; {
+
+    @Override
+    public Collection&lt;Contract&gt; get() {
+        return Collections.singletonList(Contract.make(c -&gt; {
+            c.request(r -&gt; {
+                r.url("/foo");
+                r.method(r.GET());
+                r.body(r.file("request.json"));
+            });
+            c.response(r -&gt; {
+                r.status(r.OK());
+                r.body(r.file("response.json"));
+            });
+        }));
+    }
+
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">import org.springframework.cloud.contract.spec.ContractDsl.Companion.contract
+
+contract {
+    request {
+        url = url("/1")
+        method = PUT
+        headers {
+            contentType = APPLICATION_JSON
+        }
+        body = bodyFromFile("request.json")
+    }
+    response {
+        status = OK
+        body = bodyFromFile("response.json")
+        headers {
+            contentType = APPLICATION_JSON
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Further assume that the JSON files is as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">request.json</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
+  "status": "REQUEST"
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">response.json</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">{
+  "status": "RESPONSE"
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>When test or stub generation takes place, the contents of the <code>request.json</code> and <code>response.json</code> files are passed to the body
+of a request or a response. The name of the file needs to be a file with location
+relative to the folder in which the contract lays.</p>
+</div>
+<div class="paragraph">
+<p>If you need to pass the contents of a file in binary form,
+you can use the <code>fileAsBytes</code> method in the coded DSL or a <code>bodyFromFileAsBytes</code> field in YAML.</p>
+</div>
+<div class="paragraph">
+<p>The following example shows how to pass the contents of binary files:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">import org.springframework.cloud.contract.spec.Contract
+
+Contract.make {
+    request {
+        url("/1")
+        method(PUT())
+        headers {
+            contentType(applicationOctetStream())
+        }
+        body(fileAsBytes("request.pdf"))
+    }
+    response {
+        status 200
+        body(fileAsBytes("response.pdf"))
+        headers {
+            contentType(applicationOctetStream())
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">request:
+  url: /1
+  method: PUT
+  headers:
+    Content-Type: application/octet-stream
+  bodyFromFileAsBytes: request.pdf
+response:
+  status: 200
+  bodyFromFileAsBytes: response.pdf
+  headers:
+    Content-Type: application/octet-stream</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import java.util.Collection;
+import java.util.Collections;
+import java.util.function.Supplier;
+
+import org.springframework.cloud.contract.spec.Contract;
+
+class contract_rest_from_pdf implements Supplier&lt;Collection&lt;Contract&gt;&gt; {
+
+    @Override
+    public Collection&lt;Contract&gt; get() {
+        return Collections.singletonList(Contract.make(c -&gt; {
+            c.request(r -&gt; {
+                r.url("/1");
+                r.method(r.PUT());
+                r.body(r.fileAsBytes("request.pdf"));
+                r.headers(h -&gt; {
+                    h.contentType(h.applicationOctetStream());
+                });
+            });
+            c.response(r -&gt; {
+                r.status(r.OK());
+                r.body(r.fileAsBytes("response.pdf"));
+                r.headers(h -&gt; {
+                    h.contentType(h.applicationOctetStream());
+                });
+            });
+        }));
+    }
+
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">import org.springframework.cloud.contract.spec.ContractDsl.Companion.contract
+
+contract {
+    request {
+        url = url("/1")
+        method = PUT
+        headers {
+            contentType = APPLICATION_OCTET_STREAM
+        }
+        body = bodyFromFileAsBytes("contracts/request.pdf")
+    }
+    response {
+        status = OK
+        body = bodyFromFileAsBytes("contracts/response.pdf")
+        headers {
+            contentType = APPLICATION_OCTET_STREAM
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+You should use this approach whenever you want to work with binary payloads,
+ both for HTTP and messaging.
+</td>
+</tr>
+</table>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="features-http"><a class="anchor" href="#features-http"></a><a class="link" href="#features-http">3.2. Contracts for HTTP</a></h3>
+<div class="paragraph">
+<p>Spring Cloud Contract lets you verify applications that use REST or HTTP as a
+means of communication. Spring Cloud Contract verifies that, for a request that matches the
+criteria from the <code>request</code> part of the contract, the server provides a response that is in
+keeping with the <code>response</code> part of the contract. Subsequently, the contracts are used to
+generate WireMock stubs that, for any request matching the provided criteria, provide a
+suitable response.</p>
+</div>
+<div class="sect3">
+<h4 id="contract-dsl-http-top-level-elements"><a class="anchor" href="#contract-dsl-http-top-level-elements"></a><a class="link" href="#contract-dsl-http-top-level-elements">3.2.1. HTTP Top-Level Elements</a></h4>
+<div class="paragraph">
+<p>You can call the following methods in the top-level closure of a contract definition:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>request</code>: Mandatory</p>
+</li>
+<li>
+<p><code>response</code> : Mandatory</p>
+</li>
+<li>
+<p><code>priority</code>: Optional</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The following example shows how to define an HTTP request contract:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    // Definition of HTTP request part of the contract
+    // (this can be a valid request or invalid depending
+    // on type of contract being specified).
+    request {
+        method GET()
+        url "/foo"
+        //...
+    }
+
+    // Definition of HTTP response part of the contract
+    // (a service implementing this contract should respond
+    // with following response after receiving request
+    // specified in "request" part above).
+    response {
+        status 200
+        //...
+    }
+
+    // Contract priority, which can be used for overriding
+    // contracts (1 is highest). Priority is optional.
+    priority 1
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">priority: 8
+request:
+...
+response:
+...</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">org.springframework.cloud.contract.spec.Contract.make(c -&gt; {
+    // Definition of HTTP request part of the contract
+    // (this can be a valid request or invalid depending
+    // on type of contract being specified).
+    c.request(r -&gt; {
+        r.method(r.GET());
+        r.url("/foo");
+        // ...
+    });
+
+    // Definition of HTTP response part of the contract
+    // (a service implementing this contract should respond
+    // with following response after receiving request
+    // specified in "request" part above).
+    c.response(r -&gt; {
+        r.status(200);
+        // ...
+    });
+
+    // Contract priority, which can be used for overriding
+    // contracts (1 is highest). Priority is optional.
+    c.priority(1);
+});</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    // Definition of HTTP request part of the contract
+    // (this can be a valid request or invalid depending
+    // on type of contract being specified).
+    request {
+        method = GET
+        url = url("/foo")
+        // ...
+    }
+
+    // Definition of HTTP response part of the contract
+    // (a service implementing this contract should respond
+    // with following response after receiving request
+    // specified in "request" part above).
+    response {
+        status = OK
+        // ...
+    }
+
+    // Contract priority, which can be used for overriding
+    // contracts (1 is highest). Priority is optional.
+    priority = 1
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+If you want to make your contract have a higher priority,
+you need to pass a lower number to the <code>priority</code> tag or method. For example, a <code>priority</code> with
+a value of <code>5</code> has higher priority than a <code>priority</code> with a value of <code>10</code>.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="contract-dsl-request"><a class="anchor" href="#contract-dsl-request"></a><a class="link" href="#contract-dsl-request">3.2.2. HTTP Request</a></h4>
+<div class="paragraph">
+<p>The HTTP protocol requires only the method and the URL to be specified in a request. The
+same information is mandatory in request definition of the contract.</p>
+</div>
+<div class="paragraph">
+<p>The following example shows a contract for a request:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        // HTTP request method (GET/POST/PUT/DELETE).
+        method 'GET'
+
+        // Path component of request URL is specified as follows.
+        urlPath('/users')
+    }
+
+    response {
+        //...
+        status 200
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">method: PUT
+url: /foo</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">org.springframework.cloud.contract.spec.Contract.make(c -&gt; {
+    c.request(r -&gt; {
+        // HTTP request method (GET/POST/PUT/DELETE).
+        r.method("GET");
+
+        // Path component of request URL is specified as follows.
+        r.urlPath("/users");
+    });
+
+    c.response(r -&gt; {
+        // ...
+        r.status(200);
+    });
+});</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    request {
+        // HTTP request method (GET/POST/PUT/DELETE).
+        method = method("GET")
+
+        // Path component of request URL is specified as follows.
+        urlPath = path("/users")
+    }
+    response {
+        // ...
+        status = code(200)
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You can specify an absolute rather than a relative <code>url</code>, but using <code>urlPath</code> is
+the recommended way, as doing so makes the tests be host-independent.</p>
+</div>
+<div class="paragraph">
+<p>The following example uses <code>url</code>:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        method 'GET'
+
+        // Specifying `url` and `urlPath` in one contract is illegal.
+        url('http://localhost:8888/users')
+    }
+
+    response {
+        //...
+        status 200
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">request:
+  method: PUT
+  urlPath: /foo</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">org.springframework.cloud.contract.spec.Contract.make(c -&gt; {
+    c.request(r -&gt; {
+        r.method("GET");
+
+        // Specifying `url` and `urlPath` in one contract is illegal.
+        r.url("http://localhost:8888/users");
+    });
+
+    c.response(r -&gt; {
+        // ...
+        r.status(200);
+    });
+});</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    request {
+        method = GET
+
+        // Specifying `url` and `urlPath` in one contract is illegal.
+        url("http://localhost:8888/users")
+    }
+    response {
+        // ...
+        status = OK
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p><code>request</code> may contain query parameters, as the following example (which uses <code>urlPath</code>) shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        //...
+        method GET()
+
+        urlPath('/users') {
+
+            // Each parameter is specified in form
+            // `'paramName' : paramValue` where parameter value
+            // may be a simple literal or one of matcher functions,
+            // all of which are used in this example.
+            queryParameters {
+
+                // If a simple literal is used as value
+                // default matcher function is used (equalTo)
+                parameter 'limit': 100
+
+                // `equalTo` function simply compares passed value
+                // using identity operator (==).
+                parameter 'filter': equalTo("email")
+
+                // `containing` function matches strings
+                // that contains passed substring.
+                parameter 'gender': value(consumer(containing("[mf]")), producer('mf'))
+
+                // `matching` function tests parameter
+                // against passed regular expression.
+                parameter 'offset': value(consumer(matching("[0-9]+")), producer(123))
+
+                // `notMatching` functions tests if parameter
+                // does not match passed regular expression.
+                parameter 'loginStartsWith': value(consumer(notMatching(".{0,2}")), producer(3))
+            }
+        }
+
+        //...
+    }
+
+    response {
+        //...
+        status 200
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
+...
+queryParameters:
+  a: b
+  b: c</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">org.springframework.cloud.contract.spec.Contract.make(c -&gt; {
+    c.request(r -&gt; {
+        // ...
+        r.method(r.GET());
+
+        r.urlPath("/users", u -&gt; {
+
+            // Each parameter is specified in form
+            // `'paramName' : paramValue` where parameter value
+            // may be a simple literal or one of matcher functions,
+            // all of which are used in this example.
+            u.queryParameters(q -&gt; {
+
+                // If a simple literal is used as value
+                // default matcher function is used (equalTo)
+                q.parameter("limit", 100);
+
+                // `equalTo` function simply compares passed value
+                // using identity operator (==).
+                q.parameter("filter", r.equalTo("email"));
+
+                // `containing` function matches strings
+                // that contains passed substring.
+                q.parameter("gender",
+                        r.value(r.consumer(r.containing("[mf]")),
+                                r.producer("mf")));
+
+                // `matching` function tests parameter
+                // against passed regular expression.
+                q.parameter("offset",
+                        r.value(r.consumer(r.matching("[0-9]+")),
+                                r.producer(123)));
+
+                // `notMatching` functions tests if parameter
+                // does not match passed regular expression.
+                q.parameter("loginStartsWith",
+                        r.value(r.consumer(r.notMatching(".{0,2}")),
+                                r.producer(3)));
+            });
+        });
+
+        // ...
+    });
+
+    c.response(r -&gt; {
+        // ...
+        r.status(200);
+    });
+});</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    request {
+        // ...
+        method = GET
+
+        // Each parameter is specified in form
+        // `'paramName' : paramValue` where parameter value
+        // may be a simple literal or one of matcher functions,
+        // all of which are used in this example.
+        urlPath = path("/users") withQueryParameters {
+            // If a simple literal is used as value
+            // default matcher function is used (equalTo)
+            parameter("limit", 100)
+
+            // `equalTo` function simply compares passed value
+            // using identity operator (==).
+            parameter("filter", equalTo("email"))
+
+            // `containing` function matches strings
+            // that contains passed substring.
+            parameter("gender", value(consumer(containing("[mf]")), producer("mf")))
+
+            // `matching` function tests parameter
+            // against passed regular expression.
+            parameter("offset", value(consumer(matching("[0-9]+")), producer(123)))
+
+            // `notMatching` functions tests if parameter
+            // does not match passed regular expression.
+            parameter("loginStartsWith", value(consumer(notMatching(".{0,2}")), producer(3)))
+        }
+
+        // ...
+    }
+    response {
+        // ...
+        status = code(200)
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p><code>request</code> can contain additional request headers, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        //...
+        method GET()
+        url "/foo"
+
+        // Each header is added in form `'Header-Name' : 'Header-Value'`.
+        // there are also some helper methods
+        headers {
+            header 'key': 'value'
+            contentType(applicationJson())
+        }
+
+        //...
+    }
+
+    response {
+        //...
+        status 200
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
+...
+headers:
+  foo: bar
+  fooReq: baz</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">org.springframework.cloud.contract.spec.Contract.make(c -&gt; {
+    c.request(r -&gt; {
+        // ...
+        r.method(r.GET());
+        r.url("/foo");
+
+        // Each header is added in form `'Header-Name' : 'Header-Value'`.
+        // there are also some helper methods
+        r.headers(h -&gt; {
+            h.header("key", "value");
+            h.contentType(h.applicationJson());
+        });
+
+        // ...
+    });
+
+    c.response(r -&gt; {
+        // ...
+        r.status(200);
+    });
+});</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    request {
+        // ...
+        method = GET
+        url = url("/foo")
+
+        // Each header is added in form `'Header-Name' : 'Header-Value'`.
+        // there are also some helper variables
+        headers {
+            header("key", "value")
+            contentType = APPLICATION_JSON
+        }
+
+        // ...
+    }
+    response {
+        // ...
+        status = OK
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p><code>request</code> may contain additional request cookies, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        //...
+        method GET()
+        url "/foo"
+
+        // Each Cookies is added in form `'Cookie-Key' : 'Cookie-Value'`.
+        // there are also some helper methods
+        cookies {
+            cookie 'key': 'value'
+            cookie('another_key', 'another_value')
+        }
+
+        //...
+    }
+
+    response {
+        //...
+        status 200
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
+...
+cookies:
+  foo: bar
+  fooReq: baz</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">org.springframework.cloud.contract.spec.Contract.make(c -&gt; {
+    c.request(r -&gt; {
+        // ...
+        r.method(r.GET());
+        r.url("/foo");
+
+        // Each Cookies is added in form `'Cookie-Key' : 'Cookie-Value'`.
+        // there are also some helper methods
+        r.cookies(ck -&gt; {
+            ck.cookie("key", "value");
+            ck.cookie("another_key", "another_value");
+        });
+
+        // ...
+    });
+
+    c.response(r -&gt; {
+        // ...
+        r.status(200);
+    });
+});</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    request {
+        // ...
+        method = GET
+        url = url("/foo")
+
+        // Each Cookies is added in form `'Cookie-Key' : 'Cookie-Value'`.
+        // there are also some helper methods
+        cookies {
+            cookie("key", "value")
+            cookie("another_key", "another_value")
+        }
+
+        // ...
+    }
+
+    response {
+        // ...
+        status = code(200)
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p><code>request</code> may contain a request body, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        //...
+        method GET()
+        url "/foo"
+
+        // Currently only JSON format of request body is supported.
+        // Format will be determined from a header or body's content.
+        body '''{ "login" : "john", "name": "John The Contract" }'''
+    }
+
+    response {
+        //...
+        status 200
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">request:
+...
+body:
+  foo: bar</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">org.springframework.cloud.contract.spec.Contract.make(c -&gt; {
+    c.request(r -&gt; {
+        // ...
+        r.method(r.GET());
+        r.url("/foo");
+
+        // Currently only JSON format of request body is supported.
+        // Format will be determined from a header or body's content.
+        r.body("{ \"login\" : \"john\", \"name\": \"John The Contract\" }");
+    });
+
+    c.response(r -&gt; {
+        // ...
+        r.status(200);
+    });
+});</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    request {
+        // ...
+        method = GET
+        url = url("/foo")
+
+        // Currently only JSON format of request body is supported.
+        // Format will be determined from a header or body's content.
+        body = body("{ \"login\" : \"john\", \"name\": \"John The Contract\" }")
+    }
+    response {
+        // ...
+        status = OK
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p><code>request</code> can contain multipart elements. To include multipart elements, use the
+<code>multipart</code> method/section, as the following examples show:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract contractDsl = org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        method 'PUT'
+        url '/multipart'
+        headers {
+            contentType('multipart/form-data;boundary=AaB03x')
+        }
+        multipart(
+                // key (parameter name), value (parameter value) pair
+                formParameter: $(c(regex('".+"')), p('"formParameterValue"')),
+                someBooleanParameter: $(c(regex(anyBoolean())), p('true')),
+                // a named parameter (e.g. with `file` name) that represents file with
+                // `name` and `content`. You can also call `named("fileName", "fileContent")`
+                file: named(
+                        // name of the file
+                        name: $(c(regex(nonEmpty())), p('filename.csv')),
+                        // content of the file
+                        content: $(c(regex(nonEmpty())), p('file content')),
+                        // content type for the part
+                        contentType: $(c(regex(nonEmpty())), p('application/json')))
+        )
+    }
+    response {
+        status OK()
+    }
+}
+org.springframework.cloud.contract.spec.Contract contractDsl = org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        method "PUT"
+        url "/multipart"
+        headers {
+            contentType('multipart/form-data;boundary=AaB03x')
+        }
+        multipart(
+                file: named(
+                        name: value(stub(regex('.+')), test('file')),
+                        content: value(stub(regex('.+')), test([100, 117, 100, 97] as byte[]))
+                )
+        )
+    }
+    response {
+        status 200
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">request:
+  method: PUT
+  url: /multipart
+  headers:
+    Content-Type: multipart/form-data;boundary=AaB03x
+  multipart:
+    params:
+      # key (parameter name), value (parameter value) pair
+      formParameter: '"formParameterValue"'
+      someBooleanParameter: true
+    named:
+      - paramName: file
+        fileName: filename.csv
+        fileContent: file content
+  matchers:
+    multipart:
+      params:
+        - key: formParameter
+          regex: ".+"
+        - key: someBooleanParameter
+          predefined: any_boolean
+      named:
+        - paramName: file
+          fileName:
+            predefined: non_empty
+          fileContent:
+            predefined: non_empty
+response:
+  status: 200</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import java.util.Collection;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.Map;
+import java.util.function.Supplier;
+
+import org.springframework.cloud.contract.spec.Contract;
+import org.springframework.cloud.contract.spec.internal.DslProperty;
+import org.springframework.cloud.contract.spec.internal.Request;
+import org.springframework.cloud.contract.verifier.util.ContractVerifierUtil;
+
+class contract_multipart implements Supplier&lt;Collection&lt;Contract&gt;&gt; {
+
+    private static Map&lt;String, DslProperty&gt; namedProps(Request r) {
+        Map&lt;String, DslProperty&gt; map = new HashMap&lt;&gt;();
+        // name of the file
+        map.put("name", r.$(r.c(r.regex(r.nonEmpty())), r.p("filename.csv")));
+        // content of the file
+        map.put("content", r.$(r.c(r.regex(r.nonEmpty())), r.p("file content")));
+        // content type for the part
+        map.put("contentType", r.$(r.c(r.regex(r.nonEmpty())), r.p("application/json")));
+        return map;
+    }
+
+    @Override
+    public Collection&lt;Contract&gt; get() {
+        return Collections.singletonList(Contract.make(c -&gt; {
+            c.request(r -&gt; {
+                r.method("PUT");
+                r.url("/multipart");
+                r.headers(h -&gt; {
+                    h.contentType("multipart/form-data;boundary=AaB03x");
+                });
+                r.multipart(ContractVerifierUtil.map()
+                        // key (parameter name), value (parameter value) pair
+                        .entry("formParameter",
+                                r.$(r.c(r.regex("\".+\"")),
+                                        r.p("\"formParameterValue\"")))
+                        .entry("someBooleanParameter",
+                                r.$(r.c(r.regex(r.anyBoolean())), r.p("true")))
+                        // a named parameter (e.g. with `file` name) that represents file
+                        // with
+                        // `name` and `content`. You can also call `named("fileName",
+                        // "fileContent")`
+                        .entry("file", r.named(namedProps(r))));
+            });
+            c.response(r -&gt; {
+                r.status(r.OK());
+            });
+        }));
+    }
+
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">import org.springframework.cloud.contract.spec.ContractDsl.Companion.contract
+
+contract {
+    request {
+        method = PUT
+        url = url("/multipart")
+        multipart {
+            field("formParameter", value(consumer(regex("\".+\"")), producer("\"formParameterValue\"")))
+            field("someBooleanParameter", value(consumer(anyBoolean), producer("true")))
+            field("file",
+                named(
+                    // name of the file
+                    value(consumer(regex(nonEmpty)), producer("filename.csv")),
+                    // content of the file
+                    value(consumer(regex(nonEmpty)), producer("file content")),
+                    // content type for the part
+                    value(consumer(regex(nonEmpty)), producer("application/json"))
+                )
+            )
+        }
+        headers {
+            contentType = "multipart/form-data;boundary=AaB03x"
+        }
+    }
+    response {
+        status = OK
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>In the preceding example, we define parameters in either of two ways:</p>
+</div>
+<div class="ulist">
+<div class="title">Coded DSL</div>
+<ul>
+<li>
+<p>Directly, by using the map notation, where the value can be a dynamic property (such as
+<code>formParameter: $(consumer(&#8230;&#8203;), producer(&#8230;&#8203;))</code>).</p>
+</li>
+<li>
+<p>By using the <code>named(&#8230;&#8203;)</code> method that lets you set a named parameter. A named parameter
+can set a <code>name</code> and <code>content</code>. You can call it either by using a method with two arguments,
+such as <code>named("fileName", "fileContent")</code>, or by using a map notation, such as
+<code>named(name: "fileName", content: "fileContent")</code>.</p>
+</li>
+</ul>
+</div>
+<div class="ulist">
+<div class="title">YAML</div>
+<ul>
+<li>
+<p>The multipart parameters are set in the <code>multipart.params</code> section.</p>
+</li>
+<li>
+<p>The named parameters (the <code>fileName</code> and <code>fileContent</code> for a given parameter name)
+can be set in the <code>multipart.named</code> section. That section contains
+the <code>paramName</code> (the name of the parameter), <code>fileName</code> (the name of the file),
+<code>fileContent</code> (the content of the file) fields.</p>
+</li>
+<li>
+<p>The dynamic bits can be set via the <code>matchers.multipart</code> section.</p>
+<div class="ulist">
+<ul>
+<li>
+<p>For parameters, use the <code>params</code> section, which can accept
+<code>regex</code> or a <code>predefined</code> regular expression.</p>
+</li>
+<li>
+<p>for named params, use the <code>named</code> section where first you
+define the parameter name with <code>paramName</code>. Then you can pass the
+parametrization of either <code>fileName</code> or <code>fileContent</code> in a
+<code>regex</code> or in a <code>predefined</code> regular expression.</p>
+</li>
+</ul>
+</div>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>From the contract in the preceding example, the generated test and stubs look as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Test</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">// given:
+  MockMvcRequestSpecification request = given()
+    .header("Content-Type", "multipart/form-data;boundary=AaB03x")
+    .param("formParameter", "\"formParameterValue\"")
+    .param("someBooleanParameter", "true")
+    .multiPart("file", "filename.csv", "file content".getBytes());
+
+ // when:
+  ResponseOptions response = given().spec(request)
+    .put("/multipart");
+
+ // then:
+  assertThat(response.statusCode()).isEqualTo(200);</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Stub</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">            '''
+{
+  "request" : {
+    "url" : "/multipart",
+    "method" : "PUT",
+    "headers" : {
+      "Content-Type" : {
+        "matches" : "multipart/form-data;boundary=AaB03x.*"
+      }
+    },
+    "bodyPatterns" : [ {
+        "matches" : ".*--(.*)\\r\\nContent-Disposition: form-data; name=\\"formParameter\\"\\r\\n(Content-Type: .*\\r\\n)?(Content-Transfer-Encoding: .*\\r\\n)?(Content-Length: \\\\d+\\r\\n)?\\r\\n\\".+\\"\\r\\n--\\\\1.*"
+    }, {
+        "matches" : ".*--(.*)\\r\\nContent-Disposition: form-data; name=\\"someBooleanParameter\\"\\r\\n(Content-Type: .*\\r\\n)?(Content-Transfer-Encoding: .*\\r\\n)?(Content-Length: \\\\d+\\r\\n)?\\r\\n(true|false)\\r\\n--\\\\1.*"
+    }, {
+      "matches" : ".*--(.*)\\r\\nContent-Disposition: form-data; name=\\"file\\"; filename=\\"[\\\\S\\\\s]+\\"\\r\\n(Content-Type: .*\\r\\n)?(Content-Transfer-Encoding: .*\\r\\n)?(Content-Length: \\\\d+\\r\\n)?\\r\\n[\\\\S\\\\s]+\\r\\n--\\\\1.*"
+    } ]
+  },
+  "response" : {
+    "status" : 200,
+    "transformers" : [ "response-template", "foo-transformer" ]
+  }
+}
+    '''</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="contract-dsl-response"><a class="anchor" href="#contract-dsl-response"></a><a class="link" href="#contract-dsl-response">3.2.3. HTTP Response</a></h4>
+<div class="paragraph">
+<p>The response must contain an HTTP status code and may contain other information. The
+following code shows an example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        //...
+        method GET()
+        url "/foo"
+    }
+    response {
+        // Status code sent by the server
+        // in response to request specified above.
+        status OK()
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">response:
+...
+status: 200</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">org.springframework.cloud.contract.spec.Contract.make(c -&gt; {
+    c.request(r -&gt; {
+        // ...
+        r.method(r.GET());
+        r.url("/foo");
+    });
+    c.response(r -&gt; {
+        // Status code sent by the server
+        // in response to request specified above.
+        r.status(r.OK());
+    });
+});</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    request {
+        // ...
+        method = GET
+        url =url("/foo")
+    }
+    response {
+        // Status code sent by the server
+        // in response to request specified above.
+        status = OK
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Besides status, the response may contain headers, cookies, and a body, which are
+specified the same way as in the request (see <a href="#contract-dsl-request">HTTP Request</a>).</p>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+In the Groovy DSL, you can reference the <code>org.springframework.cloud.contract.spec.internal.HttpStatus</code>
+methods to provide a meaningful status instead of a digit. For example, you can call
+<code>OK()</code> for a status <code>200</code> or <code>BAD_REQUEST()</code> for <code>400</code>.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="contract-dsl-dynamic-properties"><a class="anchor" href="#contract-dsl-dynamic-properties"></a><a class="link" href="#contract-dsl-dynamic-properties">3.2.4. Dynamic properties</a></h4>
+<div class="paragraph">
+<p>The contract can contain some dynamic properties: timestamps, IDs, and so on. You do not
+want to force the consumers to stub their clocks to always return the same value of time
+so that it gets matched by the stub.</p>
+</div>
+<div class="paragraph">
+<p>For the Groovy DSL, you can provide the dynamic parts in your contracts
+in two ways: pass them directly in the body or set them in a separate section called
+<code>bodyMatchers</code>.</p>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+Before 2.0.0, these were set by using <code>testMatchers</code> and <code>stubMatchers</code>.
+See the <a href="https://github.com/spring-cloud/spring-cloud-contract/wiki/Spring-Cloud-Contract-2.0-Migration-Guide">migration guide</a> for more information.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>For YAML, you can use only the <code>matchers</code> section.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+Entries inside the <code>matchers</code> must reference existing elements of the payload. For more information check this <a href="https://github.com/spring-cloud/spring-cloud-contract/issues/722">issue</a>.
+</td>
+</tr>
+</table>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-dynamic-properties-in-body"><a class="anchor" href="#contract-dsl-dynamic-properties-in-body"></a><a class="link" href="#contract-dsl-dynamic-properties-in-body">Dynamic Properties inside the Body</a></h5>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+This section is valid only for the Coded DSL (Groovy, Java etc.). Check out the
+<a href="#contract-dsl-matchers">Dynamic Properties in the Matchers Sections</a> section for YAML examples of a similar feature.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>You can set the properties inside the body either with the <code>value</code> method or, if you use
+the Groovy map notation, with <code>$()</code>. The following example shows how to set dynamic
+properties with the value method:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">value</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">value(consumer(...), producer(...))
+value(c(...), p(...))
+value(stub(...), test(...))
+value(client(...), server(...))</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">$</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">$(consumer(...), producer(...))
+$(c(...), p(...))
+$(stub(...), test(...))
+$(client(...), server(...))</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Both approaches work equally well. The <code>stub</code> and <code>client</code> methods are aliases over the <code>consumer</code>
+method. Subsequent sections take a closer look at what you can do with those values.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-regex"><a class="anchor" href="#contract-dsl-regex"></a><a class="link" href="#contract-dsl-regex">Regular Expressions</a></h5>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+This section is valid only for Groovy DSL. Check out the
+<a href="#contract-dsl-matchers">Dynamic Properties in the Matchers Sections</a> section for YAML examples of a similar feature.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>You can use regular expressions to write your requests in the contract DSL. Doing so is
+particularly useful when you want to indicate that a given response should be provided
+for requests that follow a given pattern. Also, you can use regular expressions when you
+need to use patterns and not exact values both for your tests and your server-side tests.</p>
+</div>
+<div class="paragraph">
+<p>Make sure that regex matches a whole region of a sequence, as, internally, a call to
+<a href="https://docs.oracle.com/javase/8/docs/api/java/util/regex/Matcher.html#matches"><code>Pattern.matches()</code></a>
+is called. For instance, <code>abc</code> does not match <code>aabc</code>, but <code>.abc</code> does.
+There are several additional <a href="#contract-dsl-regex-limitations">known limitations</a> as well.</p>
+</div>
+<div class="paragraph">
+<p>The following example shows how to use regular expressions to write a request:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        method('GET')
+        url $(consumer(~/\/[0-9]{2}/), producer('/12'))
+    }
+    response {
+        status OK()
+        body(
+                id: $(anyNumber()),
+                surname: $(
+                        consumer('Kowalsky'),
+                        producer(regex('[a-zA-Z]+'))
+                ),
+                name: 'Jan',
+                created: $(consumer('2014-02-02 12:23:43'), producer(execute('currentDate(it)'))),
+                correlationId: value(consumer('5d1f9fef-e0dc-4f3d-a7e4-72d2220dd827'),
+                        producer(regex('[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}'))
+                )
+        )
+        headers {
+            header 'Content-Type': 'text/plain'
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">org.springframework.cloud.contract.spec.Contract.make(c -&gt; {
+    c.request(r -&gt; {
+        r.method("GET");
+        r.url(r.$(r.consumer(r.regex("\\/[0-9]{2}")), r.producer("/12")));
+    });
+    c.response(r -&gt; {
+        r.status(r.OK());
+        r.body(ContractVerifierUtil.map().entry("id", r.$(r.anyNumber()))
+                .entry("surname", r.$(r.consumer("Kowalsky"),
+                        r.producer(r.regex("[a-zA-Z]+")))));
+        r.headers(h -&gt; {
+            h.header("Content-Type", "text/plain");
+        });
+    });
+});</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    request {
+        method = method("GET")
+        url = url(v(consumer(regex("\\/[0-9]{2}")), producer("/12")))
+    }
+    response {
+        status = OK
+        body(mapOf(
+                "id" to v(anyNumber),
+                "surname" to v(consumer("Kowalsky"), producer(regex("[a-zA-Z]+")))
+        ))
+        headers {
+            header("Content-Type", "text/plain")
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You can also provide only one side of the communication with a regular expression. If you
+do so, then the contract engine automatically provides the generated string that matches
+the provided regular expression. The following code shows an example for Groovy:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        method 'PUT'
+        url value(consumer(regex('/foo/[0-9]{5}')))
+        body([
+                requestElement: $(consumer(regex('[0-9]{5}')))
+        ])
+        headers {
+            header('header', $(consumer(regex('application\\/vnd\\.fraud\\.v1\\+json;.*'))))
+        }
+    }
+    response {
+        status OK()
+        body([
+                responseElement: $(producer(regex('[0-9]{7}')))
+        ])
+        headers {
+            contentType("application/vnd.fraud.v1+json")
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>In the preceding example, the opposite side of the communication has the respective data
+generated for request and response.</p>
+</div>
+<div class="paragraph">
+<p>Spring Cloud Contract comes with a series of predefined regular expressions that you can
+use in your contracts, as the following example shows:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public static RegexProperty onlyAlphaUnicode() {
+    return new RegexProperty(ONLY_ALPHA_UNICODE).asString();
+}
+
+public static RegexProperty alphaNumeric() {
+    return new RegexProperty(ALPHA_NUMERIC).asString();
+}
+
+public static RegexProperty number() {
+    return new RegexProperty(NUMBER).asDouble();
+}
+
+public static RegexProperty positiveInt() {
+    return new RegexProperty(POSITIVE_INT).asInteger();
+}
+
+public static RegexProperty anyBoolean() {
+    return new RegexProperty(TRUE_OR_FALSE).asBooleanType();
+}
+
+public static RegexProperty anInteger() {
+    return new RegexProperty(INTEGER).asInteger();
+}
+
+public static RegexProperty aDouble() {
+    return new RegexProperty(DOUBLE).asDouble();
+}
+
+public static RegexProperty ipAddress() {
+    return new RegexProperty(IP_ADDRESS).asString();
+}
+
+public static RegexProperty hostname() {
+    return new RegexProperty(HOSTNAME_PATTERN).asString();
+}
+
+public static RegexProperty email() {
+    return new RegexProperty(EMAIL).asString();
+}
+
+public static RegexProperty url() {
+    return new RegexProperty(URL).asString();
+}
+
+public static RegexProperty httpsUrl() {
+    return new RegexProperty(HTTPS_URL).asString();
+}
+
+public static RegexProperty uuid() {
+    return new RegexProperty(UUID).asString();
+}
+
+public static RegexProperty isoDate() {
+    return new RegexProperty(ANY_DATE).asString();
+}
+
+public static RegexProperty isoDateTime() {
+    return new RegexProperty(ANY_DATE_TIME).asString();
+}
+
+public static RegexProperty isoTime() {
+    return new RegexProperty(ANY_TIME).asString();
+}
+
+public static RegexProperty iso8601WithOffset() {
+    return new RegexProperty(ISO8601_WITH_OFFSET).asString();
+}
+
+public static RegexProperty nonEmpty() {
+    return new RegexProperty(NON_EMPTY).asString();
+}
+
+public static RegexProperty nonBlank() {
+    return new RegexProperty(NON_BLANK).asString();
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>In your contract, you can use it as follows (example for the Groovy DSL):</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract dslWithOptionalsInString = Contract.make {
+    priority 1
+    request {
+        method POST()
+        url '/users/password'
+        headers {
+            contentType(applicationJson())
+        }
+        body(
+                email: $(consumer(optional(regex(email()))), producer('abc@abc.com')),
+                callback_url: $(consumer(regex(hostname())), producer('http://partners.com'))
+        )
+    }
+    response {
+        status 404
+        headers {
+            contentType(applicationJson())
+        }
+        body(
+                code: value(consumer("123123"), producer(optional("123123"))),
+                message: "User not found by email = [${value(producer(regex(email())), consumer('not.existing@user.com'))}]"
+        )
+    }
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>To make matters even simpler, you can use a set of predefined objects that automatically
+assume that you want a regular expression to be passed.
+All of those methods start with the <code>any</code> prefix, as follows:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">T anyAlphaUnicode();
+
+T anyAlphaNumeric();
+
+T anyNumber();
+
+T anyInteger();
+
+T anyPositiveInt();
+
+T anyDouble();
+
+T anyHex();
+
+T aBoolean();
+
+T anyIpAddress();
+
+T anyHostname();
+
+T anyEmail();
+
+T anyUrl();
+
+T anyHttpsUrl();
+
+T anyUuid();
+
+T anyDate();
+
+T anyDateTime();
+
+T anyTime();
+
+T anyIso8601WithOffset();
+
+T anyNonBlankString();
+
+T anyNonEmptyString();
+
+T anyOf(String... values);</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The following example shows how you can reference those methods:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract contractDsl = Contract.make {
+    name "foo"
+    label 'trigger_event'
+    input {
+        triggeredBy('toString()')
+    }
+    outputMessage {
+        sentTo 'topic.rateablequote'
+        body([
+                alpha            : $(anyAlphaUnicode()),
+                number           : $(anyNumber()),
+                anInteger        : $(anyInteger()),
+                positiveInt      : $(anyPositiveInt()),
+                aDouble          : $(anyDouble()),
+                aBoolean         : $(aBoolean()),
+                ip               : $(anyIpAddress()),
+                hostname         : $(anyHostname()),
+                email            : $(anyEmail()),
+                url              : $(anyUrl()),
+                httpsUrl         : $(anyHttpsUrl()),
+                uuid             : $(anyUuid()),
+                date             : $(anyDate()),
+                dateTime         : $(anyDateTime()),
+                time             : $(anyTime()),
+                iso8601WithOffset: $(anyIso8601WithOffset()),
+                nonBlankString   : $(anyNonBlankString()),
+                nonEmptyString   : $(anyNonEmptyString()),
+                anyOf            : $(anyOf('foo', 'bar'))
+        ])
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract {
+    name = "foo"
+    label = "trigger_event"
+    input {
+        triggeredBy = "toString()"
+    }
+    outputMessage {
+        sentTo = sentTo("topic.rateablequote")
+        body(mapOf(
+                "alpha" to v(anyAlphaUnicode),
+                "number" to v(anyNumber),
+                "anInteger" to v(anyInteger),
+                "positiveInt" to v(anyPositiveInt),
+                "aDouble" to v(anyDouble),
+                "aBoolean" to v(aBoolean),
+                "ip" to v(anyIpAddress),
+                "hostname" to v(anyAlphaUnicode),
+                "email" to v(anyEmail),
+                "url" to v(anyUrl),
+                "httpsUrl" to v(anyHttpsUrl),
+                "uuid" to v(anyUuid),
+                "date" to v(anyDate),
+                "dateTime" to v(anyDateTime),
+                "time" to v(anyTime),
+                "iso8601WithOffset" to v(anyIso8601WithOffset),
+                "nonBlankString" to v(anyNonBlankString),
+                "nonEmptyString" to v(anyNonEmptyString),
+                "anyOf" to v(anyOf('foo', 'bar'))
+        ))
+        headers {
+            header("Content-Type", "text/plain")
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="contract-dsl-regex-limitations"><a class="anchor" href="#contract-dsl-regex-limitations"></a><a class="link" href="#contract-dsl-regex-limitations">Limitations</a></h6>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-warning" title="Warning"></i>
+</td>
+<td class="content">
+Due to certain limitations of the <code>Xeger</code> library that generates a string out of
+a regex, do not use the <code>$</code> and <code>^</code> signs in your regex if you rely on automatic
+generation. See <a href="https://github.com/spring-cloud/spring-cloud-contract/issues/899">Issue 899</a>.
+</td>
+</tr>
+</table>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-warning" title="Warning"></i>
+</td>
+<td class="content">
+Do not use a <code>LocalDate</code> instance as a value for <code>$</code> (for example, <code>$(consumer(LocalDate.now()))</code>).
+It causes a <code>java.lang.StackOverflowError</code>. Use <code>$(consumer(LocalDate.now().toString()))</code> instead.
+See <a href="https://github.com/spring-cloud/spring-cloud-contract/issues/900">Issue 900</a>.
+</td>
+</tr>
+</table>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-optional-params"><a class="anchor" href="#contract-dsl-optional-params"></a><a class="link" href="#contract-dsl-optional-params">Passing Optional Parameters</a></h5>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+This section is valid only for Groovy DSL. Check out the
+<a href="#contract-dsl-matchers">Dynamic Properties in the Matchers Sections</a> section for YAML examples of a similar feature.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>You can provide optional parameters in your contract. However, you can provide
+optional parameters only for the following:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>The STUB side of the Request</p>
+</li>
+<li>
+<p>The TEST side of the Response</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The following example shows how to provide optional parameters:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    priority 1
+    name "optionals"
+    request {
+        method 'POST'
+        url '/users/password'
+        headers {
+            contentType(applicationJson())
+        }
+        body(
+                email: $(consumer(optional(regex(email()))), producer('abc@abc.com')),
+                callback_url: $(consumer(regex(hostname())), producer('https://partners.com'))
+        )
+    }
+    response {
+        status 404
+        headers {
+            header 'Content-Type': 'application/json'
+        }
+        body(
+                code: value(consumer("123123"), producer(optional("123123")))
+        )
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">org.springframework.cloud.contract.spec.Contract.make(c -&gt; {
+    c.priority(1);
+    c.name("optionals");
+    c.request(r -&gt; {
+        r.method("POST");
+        r.url("/users/password");
+        r.headers(h -&gt; {
+            h.contentType(h.applicationJson());
+        });
+        r.body(ContractVerifierUtil.map()
+                .entry("email",
+                        r.$(r.consumer(r.optional(r.regex(r.email()))),
+                                r.producer("abc@abc.com")))
+                .entry("callback_url", r.$(r.consumer(r.regex(r.hostname())),
+                        r.producer("https://partners.com"))));
+    });
+    c.response(r -&gt; {
+        r.status(404);
+        r.headers(h -&gt; {
+            h.header("Content-Type", "application/json");
+        });
+        r.body(ContractVerifierUtil.map().entry("code", r.value(
+                r.consumer("123123"), r.producer(r.optional("123123")))));
+    });
+});</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">contract { c -&gt;
+    priority = 1
+    name = "optionals"
+    request {
+        method = POST
+        url = url("/users/password")
+        headers {
+            contentType = APPLICATION_JSON
+        }
+        body = body(mapOf(
+                "email" to v(consumer(optional(regex(email))), producer("abc@abc.com")),
+                "callback_url" to v(consumer(regex(hostname)), producer("https://partners.com"))
+        ))
+    }
+    response {
+        status = NOT_FOUND
+        headers {
+            header("Content-Type", "application/json")
+        }
+        body(mapOf(
+                "code" to value(consumer("123123"), producer(optional("123123")))
+        ))
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>By wrapping a part of the body with the <code>optional()</code> method, you create a regular
+expression that must be present 0 or more times.</p>
+</div>
+<div class="paragraph">
+<p>If you use Spock, the following test would be generated from the previous example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">                    """\
+package com.example
+
+import com.jayway.jsonpath.DocumentContext
+import com.jayway.jsonpath.JsonPath
+import spock.lang.Specification
+import io.restassured.module.mockmvc.specification.MockMvcRequestSpecification
+import io.restassured.response.ResponseOptions
+
+import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*
+import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson
+import static io.restassured.module.mockmvc.RestAssuredMockMvc.*
+
+@SuppressWarnings("rawtypes")
+class FooSpec extends Specification {
+
+\tdef validate_optionals() throws Exception {
+\t\tgiven:
+\t\t\tMockMvcRequestSpecification request = given()
+\t\t\t\t\t.header("Content-Type", "application/json")
+\t\t\t\t\t.body('''{"email":"abc@abc.com","callback_url":"https://partners.com"}''')
+
+\t\twhen:
+\t\t\tResponseOptions response = given().spec(request)
+\t\t\t\t\t.post("/users/password")
+
+\t\tthen:
+\t\t\tresponse.statusCode() == 404
+\t\t\tresponse.header("Content-Type") == 'application/json'
+
+\t\tand:
+\t\t\tDocumentContext parsedJson = JsonPath.parse(response.body.asString())
+\t\t\tassertThatJson(parsedJson).field("['code']").matches("(123123)?")
+\t}
+
+}
+"""</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following stub would also be generated:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">                    '''
+{
+  "request" : {
+    "url" : "/users/password",
+    "method" : "POST",
+    "bodyPatterns" : [ {
+      "matchesJsonPath" : "$[?(@.['email'] =~ /([a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\\\.[a-zA-Z]{2,6})?/)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.['callback_url'] =~ /((http[s]?|ftp):\\\\/)\\\\/?([^:\\\\/\\\\s]+)(:[0-9]{1,5})?/)]"
+    } ],
+    "headers" : {
+      "Content-Type" : {
+        "equalTo" : "application/json"
+      }
+    }
+  },
+  "response" : {
+    "status" : 404,
+    "body" : "{\\"code\\":\\"123123\\",\\"message\\":\\"User not found by email == [not.existing@user.com]\\"}",
+    "headers" : {
+      "Content-Type" : "application/json"
+    }
+  },
+  "priority" : 1
+}
+'''</code></pre>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-custom-methods"><a class="anchor" href="#contract-dsl-custom-methods"></a><a class="link" href="#contract-dsl-custom-methods">Executing Custom Methods on the Server Side</a></h5>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+This section is valid only for Groovy DSL. Check out the
+<a href="#contract-dsl-matchers">Dynamic Properties in the Matchers Sections</a> section for YAML examples of a similar feature.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>You can define a method call that runs on the server side during the test. Such a
+method can be added to the class defined as <code>baseClassForTests</code> in the configuration. The
+following code shows an example of the contract portion of the test case:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">method GET()</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">r.method(r.GET());</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">method = GET</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following code shows the base class portion of the test case:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">abstract class BaseMockMvcSpec extends Specification {
+
+    def setup() {
+        RestAssuredMockMvc.standaloneSetup(new PairIdController())
+    }
+
+    void isProperCorrelationId(Integer correlationId) {
+        assert correlationId == 123456
+    }
+
+    void isEmpty(String value) {
+        assert value == null
+    }
+
+}</code></pre>
+</div>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+You cannot use both a <code>String</code> and <code>execute</code> to perform concatenation. For
+example, calling <code>header('Authorization', 'Bearer ' + execute('authToken()'))</code> leads to
+improper results. Instead, call <code>header('Authorization', execute('authToken()'))</code> and
+ensure that the <code>authToken()</code> method returns everything you need.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The type of the object read from the JSON can be one of the following, depending on the
+JSON path:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>String</code>: If you point to a <code>String</code> value in the JSON.</p>
+</li>
+<li>
+<p><code>JSONArray</code>: If you point to a <code>List</code> in the JSON.</p>
+</li>
+<li>
+<p><code>Map</code>: If you point to a <code>Map</code> in the JSON.</p>
+</li>
+<li>
+<p><code>Number</code>: If you point to <code>Integer</code>, <code>Double</code>, and other numeric type in the JSON.</p>
+</li>
+<li>
+<p><code>Boolean</code>: If you point to a <code>Boolean</code> in the JSON.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>In the request part of the contract, you can specify that the <code>body</code> should be taken from
+a method.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+You must provide both the consumer and the producer side. The <code>execute</code> part
+is applied for the whole body, not for parts of it.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The following example shows how to read an object from JSON:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract contractDsl = Contract.make {
+    request {
+        method 'GET'
+        url '/something'
+        body(
+                $(c('foo'), p(execute('hashCode()')))
+        )
+    }
+    response {
+        status OK()
+    }
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The preceding example results in calling the <code>hashCode()</code> method in the request body.
+It should resemble the following code:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">// given:
+ MockMvcRequestSpecification request = given()
+   .body(hashCode());
+
+// when:
+ ResponseOptions response = given().spec(request)
+   .get("/something");
+
+// then:
+ assertThat(response.statusCode()).isEqualTo(200);</code></pre>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-referencing-request-from-response"><a class="anchor" href="#contract-dsl-referencing-request-from-response"></a><a class="link" href="#contract-dsl-referencing-request-from-response">Referencing the Request from the Response</a></h5>
+<div class="paragraph">
+<p>The best situation is to provide fixed values, but sometimes you need to reference a
+request in your response.</p>
+</div>
+<div class="paragraph">
+<p>If you write contracts in the Groovy DSL, you can use the <code>fromRequest()</code> method, which lets
+you reference a bunch of elements from the HTTP request. You can use the following
+options:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>fromRequest().url()</code>: Returns the request URL and query parameters.</p>
+</li>
+<li>
+<p><code>fromRequest().query(String key)</code>: Returns the first query parameter with a given name.</p>
+</li>
+<li>
+<p><code>fromRequest().query(String key, int index)</code>: Returns the nth query parameter with a
+given name.</p>
+</li>
+<li>
+<p><code>fromRequest().path()</code>: Returns the full path.</p>
+</li>
+<li>
+<p><code>fromRequest().path(int index)</code>: Returns the nth path element.</p>
+</li>
+<li>
+<p><code>fromRequest().header(String key)</code>: Returns the first header with a given name.</p>
+</li>
+<li>
+<p><code>fromRequest().header(String key, int index)</code>: Returns the nth header with a given name.</p>
+</li>
+<li>
+<p><code>fromRequest().body()</code>: Returns the full request body.</p>
+</li>
+<li>
+<p><code>fromRequest().body(String jsonPath)</code>: Returns the element from the request that
+matches the JSON Path.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>If you use the YAML contract definition or the Java one, you have to use the
+<a href="https://handlebarsjs.com/">Handlebars</a> <code>{{{ }}}</code> notation with custom Spring Cloud Contract
+functions to achieve this. In that case, you can use the following options:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>{{{ request.url }}}</code>: Returns the request URL and query parameters.</p>
+</li>
+<li>
+<p><code>{{{ request.query.key.[index] }}}</code>: Returns the nth query parameter with a given name.
+For example, for a key of <code>thing</code>, the first entry is <code>{{{ request.query.thing.[0] }}}</code></p>
+</li>
+<li>
+<p><code>{{{ request.path }}}</code>: Returns the full path.</p>
+</li>
+<li>
+<p><code>{{{ request.path.[index] }}}</code>: Returns the nth path element. For example,
+the first entry is <code>`</code>{{{ request.path.[0] }}}</p>
+</li>
+<li>
+<p><code>{{{ request.headers.key }}}</code>: Returns the first header with a given name.</p>
+</li>
+<li>
+<p><code>{{{ request.headers.key.[index] }}}</code>: Returns the nth header with a given name.</p>
+</li>
+<li>
+<p><code>{{{ request.body }}}</code>: Returns the full request body.</p>
+</li>
+<li>
+<p><code>{{{ jsonpath this 'your.json.path' }}}</code>: Returns the element from the request that
+matches the JSON Path. For example, for a JSON path of <code>$.here</code>, use <code>{{{ jsonpath this '$.here' }}}</code></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Consider the following contract:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract contractDsl = Contract.make {
+    request {
+        method 'GET'
+        url('/api/v1/xxxx') {
+            queryParameters {
+                parameter('foo', 'bar')
+                parameter('foo', 'bar2')
+            }
+        }
+        headers {
+            header(authorization(), 'secret')
+            header(authorization(), 'secret2')
+        }
+        body(foo: 'bar', baz: 5)
+    }
+    response {
+        status OK()
+        headers {
+            header(authorization(), "foo ${fromRequest().header(authorization())} bar")
+        }
+        body(
+                url: fromRequest().url(),
+                path: fromRequest().path(),
+                pathIndex: fromRequest().path(1),
+                param: fromRequest().query('foo'),
+                paramIndex: fromRequest().query('foo', 1),
+                authorization: fromRequest().header('Authorization'),
+                authorization2: fromRequest().header('Authorization', 1),
+                fullBody: fromRequest().body(),
+                responseFoo: fromRequest().body('$.foo'),
+                responseBaz: fromRequest().body('$.baz'),
+                responseBaz2: "Bla bla ${fromRequest().body('$.foo')} bla bla",
+                rawUrl: fromRequest().rawUrl(),
+                rawPath: fromRequest().rawPath(),
+                rawPathIndex: fromRequest().rawPath(1),
+                rawParam: fromRequest().rawQuery('foo'),
+                rawParamIndex: fromRequest().rawQuery('foo', 1),
+                rawAuthorization: fromRequest().rawHeader('Authorization'),
+                rawAuthorization2: fromRequest().rawHeader('Authorization', 1),
+                rawResponseFoo: fromRequest().rawBody('$.foo'),
+                rawResponseBaz: fromRequest().rawBody('$.baz'),
+                rawResponseBaz2: "Bla bla ${fromRequest().rawBody('$.foo')} bla bla"
+        )
+    }
+}
+Contract contractDsl = Contract.make {
+    request {
+        method 'GET'
+        url('/api/v1/xxxx') {
+            queryParameters {
+                parameter('foo', 'bar')
+                parameter('foo', 'bar2')
+            }
+        }
+        headers {
+            header(authorization(), 'secret')
+            header(authorization(), 'secret2')
+        }
+        body(foo: "bar", baz: 5)
+    }
+    response {
+        status OK()
+        headers {
+            contentType(applicationJson())
+        }
+        body('''
+                {
+                    "responseFoo": "{{{ jsonPath request.body '$.foo' }}}",
+                    "responseBaz": {{{ jsonPath request.body '$.baz' }}},
+                    "responseBaz2": "Bla bla {{{ jsonPath request.body '$.foo' }}} bla bla"
+                }
+        '''.toString())
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">request:
+  method: GET
+  url: /api/v1/xxxx
+  queryParameters:
+    foo:
+      - bar
+      - bar2
+  headers:
+    Authorization:
+      - secret
+      - secret2
+  body:
+    foo: bar
+    baz: 5
+response:
+  status: 200
+  headers:
+    Authorization: "foo {{{ request.headers.Authorization.0 }}} bar"
+  body:
+    url: "{{{ request.url }}}"
+    path: "{{{ request.path }}}"
+    pathIndex: "{{{ request.path.1 }}}"
+    param: "{{{ request.query.foo }}}"
+    paramIndex: "{{{ request.query.foo.1 }}}"
+    authorization: "{{{ request.headers.Authorization.0 }}}"
+    authorization2: "{{{ request.headers.Authorization.1 }}"
+    fullBody: "{{{ request.body }}}"
+    responseFoo: "{{{ jsonpath this '$.foo' }}}"
+    responseBaz: "{{{ jsonpath this '$.baz' }}}"
+    responseBaz2: "Bla bla {{{ jsonpath this '$.foo' }}} bla bla"</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package contracts.beer.rest;
+
+import java.util.function.Supplier;
+
+import org.springframework.cloud.contract.spec.Contract;
+
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.map;
+
+class shouldReturnStatsForAUser implements Supplier&lt;Contract&gt; {
+
+    @Override
+    public Contract get() {
+        return Contract.make(c -&gt; {
+            c.request(r -&gt; {
+                r.method("POST");
+                r.url("/stats");
+                r.body(map().entry("name", r.anyAlphaUnicode()));
+                r.headers(h -&gt; {
+                    h.contentType(h.applicationJson());
+                });
+            });
+            c.response(r -&gt; {
+                r.status(r.OK());
+                r.body(map()
+                        .entry("text",
+                                "Dear {{{jsonPath request.body '$.name'}}} thanks for your interested in drinking beer")
+                        .entry("quantity", r.$(r.c(5), r.p(r.anyNumber()))));
+                r.headers(h -&gt; {
+                    h.contentType(h.applicationJson());
+                });
+            });
+        });
+    }
+
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">package contracts.beer.rest
+
+import org.springframework.cloud.contract.spec.ContractDsl.Companion.contract
+
+contract {
+    request {
+        method = method("POST")
+        url = url("/stats")
+        body(mapOf(
+            "name" to anyAlphaUnicode
+        ))
+        headers {
+            contentType = APPLICATION_JSON
+        }
+    }
+    response {
+        status = OK
+        body(mapOf(
+            "text" to "Don't worry ${fromRequest().body("$.name")} thanks for your interested in drinking beer",
+            "quantity" to v(c(5), p(anyNumber))
+        ))
+        headers {
+            contentType = fromRequest().header(CONTENT_TYPE)
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Running a JUnit test generation leads to a test that resembles the following example:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">// given:
+ MockMvcRequestSpecification request = given()
+   .header("Authorization", "secret")
+   .header("Authorization", "secret2")
+   .body("{\"foo\":\"bar\",\"baz\":5}");
+
+// when:
+ ResponseOptions response = given().spec(request)
+   .queryParam("foo","bar")
+   .queryParam("foo","bar2")
+   .get("/api/v1/xxxx");
+
+// then:
+ assertThat(response.statusCode()).isEqualTo(200);
+ assertThat(response.header("Authorization")).isEqualTo("foo secret bar");
+// and:
+ DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
+ assertThatJson(parsedJson).field("['fullBody']").isEqualTo("{\"foo\":\"bar\",\"baz\":5}");
+ assertThatJson(parsedJson).field("['authorization']").isEqualTo("secret");
+ assertThatJson(parsedJson).field("['authorization2']").isEqualTo("secret2");
+ assertThatJson(parsedJson).field("['path']").isEqualTo("/api/v1/xxxx");
+ assertThatJson(parsedJson).field("['param']").isEqualTo("bar");
+ assertThatJson(parsedJson).field("['paramIndex']").isEqualTo("bar2");
+ assertThatJson(parsedJson).field("['pathIndex']").isEqualTo("v1");
+ assertThatJson(parsedJson).field("['responseBaz']").isEqualTo(5);
+ assertThatJson(parsedJson).field("['responseFoo']").isEqualTo("bar");
+ assertThatJson(parsedJson).field("['url']").isEqualTo("/api/v1/xxxx?foo=bar&amp;foo=bar2");
+ assertThatJson(parsedJson).field("['responseBaz2']").isEqualTo("Bla bla bar bla bla");</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>As you can see, elements from the request have been properly referenced in the response.</p>
+</div>
+<div class="paragraph">
+<p>The generated WireMock stub should resemble the following example:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
+  "request" : {
+    "urlPath" : "/api/v1/xxxx",
+    "method" : "POST",
+    "headers" : {
+      "Authorization" : {
+        "equalTo" : "secret2"
+      }
+    },
+    "queryParameters" : {
+      "foo" : {
+        "equalTo" : "bar2"
+      }
+    },
+    "bodyPatterns" : [ {
+      "matchesJsonPath" : "$[?(@.['baz'] == 5)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.['foo'] == 'bar')]"
+    } ]
+  },
+  "response" : {
+    "status" : 200,
+    "body" : "{\"authorization\":\"{{{request.headers.Authorization.[0]}}}\",\"path\":\"{{{request.path}}}\",\"responseBaz\":{{{jsonpath this '$.baz'}}} ,\"param\":\"{{{request.query.foo.[0]}}}\",\"pathIndex\":\"{{{request.path.[1]}}}\",\"responseBaz2\":\"Bla bla {{{jsonpath this '$.foo'}}} bla bla\",\"responseFoo\":\"{{{jsonpath this '$.foo'}}}\",\"authorization2\":\"{{{request.headers.Authorization.[1]}}}\",\"fullBody\":\"{{{escapejsonbody}}}\",\"url\":\"{{{request.url}}}\",\"paramIndex\":\"{{{request.query.foo.[1]}}}\"}",
+    "headers" : {
+      "Authorization" : "{{{request.headers.Authorization.[0]}}};foo"
+    },
+    "transformers" : [ "response-template" ]
+  }
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Sending a request such as the one presented in the <code>request</code> part of the contract results
+in sending the following response body:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
+  "url" : "/api/v1/xxxx?foo=bar&amp;foo=bar2",
+  "path" : "/api/v1/xxxx",
+  "pathIndex" : "v1",
+  "param" : "bar",
+  "paramIndex" : "bar2",
+  "authorization" : "secret",
+  "authorization2" : "secret2",
+  "fullBody" : "{\"foo\":\"bar\",\"baz\":5}",
+  "responseFoo" : "bar",
+  "responseBaz" : 5,
+  "responseBaz2" : "Bla bla bar bla bla"
+}</code></pre>
+</div>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+This feature works only with WireMock versions greater than or equal
+to 2.5.1. The Spring Cloud Contract Verifier uses WireMock&#8217;s
+<code>response-template</code> response transformer. It uses Handlebars to convert the Mustache <code>{{{ }}}</code> templates into
+proper values. Additionally, it registers two helper functions:
+</td>
+</tr>
+</table>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>escapejsonbody</code>: Escapes the request body in a format that can be embedded in a JSON.</p>
+</li>
+<li>
+<p><code>jsonpath</code>: For a given parameter, find an object in the request body.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-matchers"><a class="anchor" href="#contract-dsl-matchers"></a><a class="link" href="#contract-dsl-matchers">Dynamic Properties in the Matchers Sections</a></h5>
+<div class="paragraph">
+<p>If you work with <a href="https://docs.pact.io/">Pact</a>, the following discussion may seem familiar.
+Quite a few users are used to having a separation between the body and setting the
+dynamic parts of a contract.</p>
+</div>
+<div class="paragraph">
+<p>You can use the <code>bodyMatchers</code> section for two reasons:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Define the dynamic values that should end up in a stub.
+You can set it in the <code>request</code> or <code>inputMessage</code> part of your contract.</p>
+</li>
+<li>
+<p>Verify the result of your test.
+This section is present in the <code>response</code> or <code>outputMessage</code> side of the
+contract.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Currently, Spring Cloud Contract Verifier supports only JSON path-based matchers with the
+following matching possibilities:</p>
+</div>
+<div class="sect5">
+<h6 id="coded-dsl"><a class="anchor" href="#coded-dsl"></a><a class="link" href="#coded-dsl">Coded DSL</a></h6>
+<div class="ulist">
+<ul>
+<li>
+<p>For the stubs (in tests on the consumer&#8217;s side):</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>byEquality()</code>: The value taken from the consumer&#8217;s request in the provided JSON path must be
+equal to the value provided in the contract.</p>
+</li>
+<li>
+<p><code>byRegex(&#8230;&#8203;)</code>: The value taken from the consumer&#8217;s request in the provided JSON path must
+match the regex. You can also pass the type of the expected matched value (for example, <code>asString()</code>, <code>asLong()</code>, and so on).</p>
+</li>
+<li>
+<p><code>byDate()</code>: The value taken from the consumer&#8217;s request in the provided JSON path must
+match the regex for an ISO Date value.</p>
+</li>
+<li>
+<p><code>byTimestamp()</code>: The value taken from the consumer&#8217;s request in the provided JSON path must
+match the regex for an ISO DateTime value.</p>
+</li>
+<li>
+<p><code>byTime()</code>: The value taken from the consumer&#8217;s request in the provided JSON path must
+match the regex for an ISO Time value.</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>For the verification (in generated tests on the Producer&#8217;s side):</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>byEquality()</code>: The value taken from the producer&#8217;s response in the provided JSON path must be
+equal to the provided value in the contract.</p>
+</li>
+<li>
+<p><code>byRegex(&#8230;&#8203;)</code>: The value taken from the producer&#8217;s response in the provided JSON path must
+match the regex.</p>
+</li>
+<li>
+<p><code>byDate()</code>: The value taken from the producer&#8217;s response in the provided JSON path must match
+the regex for an ISO Date value.</p>
+</li>
+<li>
+<p><code>byTimestamp()</code>: The value taken from the producer&#8217;s response in the provided JSON path must
+match the regex for an ISO DateTime value.</p>
+</li>
+<li>
+<p><code>byTime()</code>: The value taken from the producer&#8217;s response in the provided JSON path must match
+the regex for an ISO Time value.</p>
+</li>
+<li>
+<p><code>byType()</code>: The value taken from the producer&#8217;s response in the provided JSON path needs to be
+of the same type as the type defined in the body of the response in the contract.
+<code>byType</code> can take a closure, in which you can set <code>minOccurrence</code> and <code>maxOccurrence</code>. For the
+request side, you should use the closure to assert size of the collection.
+That way, you can assert the size of the flattened collection. To check the size of an
+unflattened collection, use a custom method with the <code>byCommand(&#8230;&#8203;)</code> <code>testMatcher</code>.</p>
+</li>
+<li>
+<p><code>byCommand(&#8230;&#8203;)</code>: The value taken from the producer&#8217;s response in the provided JSON path is
+passed as an input to the custom method that you provide. For example,
+<code>byCommand('thing($it)')</code> results in calling a <code>thing</code> method to which the value matching the
+JSON Path gets passed. The type of the object read from the JSON can be one of the
+following, depending on the JSON path:</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>String</code>: If you point to a <code>String</code> value.</p>
+</li>
+<li>
+<p><code>JSONArray</code>: If you point to a <code>List</code>.</p>
+</li>
+<li>
+<p><code>Map</code>: If you point to a <code>Map</code>.</p>
+</li>
+<li>
+<p><code>Number</code>: If you point to <code>Integer</code>, <code>Double</code>, or another kind of number.</p>
+</li>
+<li>
+<p><code>Boolean</code>: If you point to a <code>Boolean</code>.</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p><code>byNull()</code>: The value taken from the response in the provided JSON path must be null.</p>
+</li>
+</ul>
+</div>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect5">
+<h6 id="yaml"><a class="anchor" href="#yaml"></a><a class="link" href="#yaml">YAML</a></h6>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+See the Groovy section for detailed explanation of
+what the types mean.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>For YAML, the structure of a matcher resembles the following example:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">- path: $.thing1
+  type: by_regex
+  value: thing2
+  regexType: as_string</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Alternatively, if you want to use one of the predefined regular expressions
+<code>[only_alpha_unicode, number, any_boolean, ip_address, hostname,
+email, url, uuid, iso_date, iso_date_time, iso_time, iso_8601_with_offset, non_empty,
+non_blank]</code>, you can use something similar to the following example:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">- path: $.thing1
+  type: by_regex
+  predefined: only_alpha_unicode</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The following list shows the allowed list of <code>type</code> values:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>For <code>stubMatchers</code>:</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>by_equality</code></p>
+</li>
+<li>
+<p><code>by_regex</code></p>
+</li>
+<li>
+<p><code>by_date</code></p>
+</li>
+<li>
+<p><code>by_timestamp</code></p>
+</li>
+<li>
+<p><code>by_time</code></p>
+</li>
+<li>
+<p><code>by_type</code></p>
+<div class="ulist">
+<ul>
+<li>
+<p>Two additional fields (<code>minOccurrence</code> and <code>maxOccurrence</code>) are accepted.</p>
+</li>
+</ul>
+</div>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>For <code>testMatchers</code>:</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>by_equality</code></p>
+</li>
+<li>
+<p><code>by_regex</code></p>
+</li>
+<li>
+<p><code>by_date</code></p>
+</li>
+<li>
+<p><code>by_timestamp</code></p>
+</li>
+<li>
+<p><code>by_time</code></p>
+</li>
+<li>
+<p><code>by_type</code></p>
+<div class="ulist">
+<ul>
+<li>
+<p>Two additional fields (<code>minOccurrence</code> and <code>maxOccurrence</code>) are accepted.</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p><code>by_command</code></p>
+</li>
+<li>
+<p><code>by_null</code></p>
+</li>
+</ul>
+</div>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>You can also define which type the regular expression corresponds to in the <code>regexType</code>
+field. The following list shows the allowed regular expression types:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>as_integer</code></p>
+</li>
+<li>
+<p><code>as_double</code></p>
+</li>
+<li>
+<p><code>as_float</code></p>
+</li>
+<li>
+<p><code>as_long</code></p>
+</li>
+<li>
+<p><code>as_short</code></p>
+</li>
+<li>
+<p><code>as_boolean</code></p>
+</li>
+<li>
+<p><code>as_string</code></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Consider the following example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract contractDsl = Contract.make {
+    request {
+        method 'GET'
+        urlPath '/get'
+        body([
+                duck                : 123,
+                alpha               : 'abc',
+                number              : 123,
+                aBoolean            : true,
+                date                : '2017-01-01',
+                dateTime            : '2017-01-01T01:23:45',
+                time                : '01:02:34',
+                valueWithoutAMatcher: 'foo',
+                valueWithTypeMatch  : 'string',
+                key                 : [
+                        'complex.key': 'foo'
+                ]
+        ])
+        bodyMatchers {
+            jsonPath('$.duck', byRegex("[0-9]{3}").asInteger())
+            jsonPath('$.duck', byEquality())
+            jsonPath('$.alpha', byRegex(onlyAlphaUnicode()).asString())
+            jsonPath('$.alpha', byEquality())
+            jsonPath('$.number', byRegex(number()).asInteger())
+            jsonPath('$.aBoolean', byRegex(anyBoolean()).asBooleanType())
+            jsonPath('$.date', byDate())
+            jsonPath('$.dateTime', byTimestamp())
+            jsonPath('$.time', byTime())
+            jsonPath("\$.['key'].['complex.key']", byEquality())
+        }
+        headers {
+            contentType(applicationJson())
+        }
+    }
+    response {
+        status OK()
+        body([
+                duck                 : 123,
+                alpha                : 'abc',
+                number               : 123,
+                positiveInteger      : 1234567890,
+                negativeInteger      : -1234567890,
+                positiveDecimalNumber: 123.4567890,
+                negativeDecimalNumber: -123.4567890,
+                aBoolean             : true,
+                date                 : '2017-01-01',
+                dateTime             : '2017-01-01T01:23:45',
+                time                 : "01:02:34",
+                valueWithoutAMatcher : 'foo',
+                valueWithTypeMatch   : 'string',
+                valueWithMin         : [
+                        1, 2, 3
+                ],
+                valueWithMax         : [
+                        1, 2, 3
+                ],
+                valueWithMinMax      : [
+                        1, 2, 3
+                ],
+                valueWithMinEmpty    : [],
+                valueWithMaxEmpty    : [],
+                key                  : [
+                        'complex.key': 'foo'
+                ],
+                nullValue            : null
+        ])
+        bodyMatchers {
+            // asserts the jsonpath value against manual regex
+            jsonPath('$.duck', byRegex("[0-9]{3}").asInteger())
+            // asserts the jsonpath value against the provided value
+            jsonPath('$.duck', byEquality())
+            // asserts the jsonpath value against some default regex
+            jsonPath('$.alpha', byRegex(onlyAlphaUnicode()).asString())
+            jsonPath('$.alpha', byEquality())
+            jsonPath('$.number', byRegex(number()).asInteger())
+            jsonPath('$.positiveInteger', byRegex(anInteger()).asInteger())
+            jsonPath('$.negativeInteger', byRegex(anInteger()).asInteger())
+            jsonPath('$.positiveDecimalNumber', byRegex(aDouble()).asDouble())
+            jsonPath('$.negativeDecimalNumber', byRegex(aDouble()).asDouble())
+            jsonPath('$.aBoolean', byRegex(anyBoolean()).asBooleanType())
+            // asserts vs inbuilt time related regex
+            jsonPath('$.date', byDate())
+            jsonPath('$.dateTime', byTimestamp())
+            jsonPath('$.time', byTime())
+            // asserts that the resulting type is the same as in response body
+            jsonPath('$.valueWithTypeMatch', byType())
+            jsonPath('$.valueWithMin', byType {
+                // results in verification of size of array (min 1)
+                minOccurrence(1)
+            })
+            jsonPath('$.valueWithMax', byType {
+                // results in verification of size of array (max 3)
+                maxOccurrence(3)
+            })
+            jsonPath('$.valueWithMinMax', byType {
+                // results in verification of size of array (min 1 &amp; max 3)
+                minOccurrence(1)
+                maxOccurrence(3)
+            })
+            jsonPath('$.valueWithMinEmpty', byType {
+                // results in verification of size of array (min 0)
+                minOccurrence(0)
+            })
+            jsonPath('$.valueWithMaxEmpty', byType {
+                // results in verification of size of array (max 0)
+                maxOccurrence(0)
+            })
+            // will execute a method `assertThatValueIsANumber`
+            jsonPath('$.duck', byCommand('assertThatValueIsANumber($it)'))
+            jsonPath("\$.['key'].['complex.key']", byEquality())
+            jsonPath('$.nullValue', byNull())
+        }
+        headers {
+            contentType(applicationJson())
+            header('Some-Header', $(c('someValue'), p(regex('[a-zA-Z]{9}'))))
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">request:
+  method: GET
+  urlPath: /get/1
+  headers:
+    Content-Type: application/json
+  cookies:
+    foo: 2
+    bar: 3
+  queryParameters:
+    limit: 10
+    offset: 20
+    filter: 'email'
+    sort: name
+    search: 55
+    age: 99
+    name: John.Doe
+    email: 'bob@email.com'
+  body:
+    duck: 123
+    alpha: "abc"
+    number: 123
+    aBoolean: true
+    date: "2017-01-01"
+    dateTime: "2017-01-01T01:23:45"
+    time: "01:02:34"
+    valueWithoutAMatcher: "foo"
+    valueWithTypeMatch: "string"
+    key:
+      "complex.key": 'foo'
+    nullValue: null
+    valueWithMin:
+      - 1
+      - 2
+      - 3
+    valueWithMax:
+      - 1
+      - 2
+      - 3
+    valueWithMinMax:
+      - 1
+      - 2
+      - 3
+    valueWithMinEmpty: []
+    valueWithMaxEmpty: []
+  matchers:
+    url:
+      regex: /get/[0-9]
+      # predefined:
+      # execute a method
+      #command: 'equals($it)'
+    queryParameters:
+      - key: limit
+        type: equal_to
+        value: 20
+      - key: offset
+        type: containing
+        value: 20
+      - key: sort
+        type: equal_to
+        value: name
+      - key: search
+        type: not_matching
+        value: '^[0-9]{2}$'
+      - key: age
+        type: not_matching
+        value: '^\\w*$'
+      - key: name
+        type: matching
+        value: 'John.*'
+      - key: hello
+        type: absent
+    cookies:
+      - key: foo
+        regex: '[0-9]'
+      - key: bar
+        command: 'equals($it)'
+    headers:
+      - key: Content-Type
+        regex: "application/json.*"
+    body:
+      - path: $.duck
+        type: by_regex
+        value: "[0-9]{3}"
+      - path: $.duck
+        type: by_equality
+      - path: $.alpha
+        type: by_regex
+        predefined: only_alpha_unicode
+      - path: $.alpha
+        type: by_equality
+      - path: $.number
+        type: by_regex
+        predefined: number
+      - path: $.aBoolean
+        type: by_regex
+        predefined: any_boolean
+      - path: $.date
+        type: by_date
+      - path: $.dateTime
+        type: by_timestamp
+      - path: $.time
+        type: by_time
+      - path: "$.['key'].['complex.key']"
+        type: by_equality
+      - path: $.nullvalue
+        type: by_null
+      - path: $.valueWithMin
+        type: by_type
+        minOccurrence: 1
+      - path: $.valueWithMax
+        type: by_type
+        maxOccurrence: 3
+      - path: $.valueWithMinMax
+        type: by_type
+        minOccurrence: 1
+        maxOccurrence: 3
+response:
+  status: 200
+  cookies:
+    foo: 1
+    bar: 2
+  body:
+    duck: 123
+    alpha: "abc"
+    number: 123
+    aBoolean: true
+    date: "2017-01-01"
+    dateTime: "2017-01-01T01:23:45"
+    time: "01:02:34"
+    valueWithoutAMatcher: "foo"
+    valueWithTypeMatch: "string"
+    valueWithMin:
+      - 1
+      - 2
+      - 3
+    valueWithMax:
+      - 1
+      - 2
+      - 3
+    valueWithMinMax:
+      - 1
+      - 2
+      - 3
+    valueWithMinEmpty: []
+    valueWithMaxEmpty: []
+    key:
+      'complex.key': 'foo'
+    nulValue: null
+  matchers:
+    headers:
+      - key: Content-Type
+        regex: "application/json.*"
+    cookies:
+      - key: foo
+        regex: '[0-9]'
+      - key: bar
+        command: 'equals($it)'
+    body:
+      - path: $.duck
+        type: by_regex
+        value: "[0-9]{3}"
+      - path: $.duck
+        type: by_equality
+      - path: $.alpha
+        type: by_regex
+        predefined: only_alpha_unicode
+      - path: $.alpha
+        type: by_equality
+      - path: $.number
+        type: by_regex
+        predefined: number
+      - path: $.aBoolean
+        type: by_regex
+        predefined: any_boolean
+      - path: $.date
+        type: by_date
+      - path: $.dateTime
+        type: by_timestamp
+      - path: $.time
+        type: by_time
+      - path: $.valueWithTypeMatch
+        type: by_type
+      - path: $.valueWithMin
+        type: by_type
+        minOccurrence: 1
+      - path: $.valueWithMax
+        type: by_type
+        maxOccurrence: 3
+      - path: $.valueWithMinMax
+        type: by_type
+        minOccurrence: 1
+        maxOccurrence: 3
+      - path: $.valueWithMinEmpty
+        type: by_type
+        minOccurrence: 0
+      - path: $.valueWithMaxEmpty
+        type: by_type
+        maxOccurrence: 0
+      - path: $.duck
+        type: by_command
+        value: assertThatValueIsANumber($it)
+      - path: $.nullValue
+        type: by_null
+        value: null
+  headers:
+    Content-Type: application/json</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>In the preceding example, you can see the dynamic portions of the contract in the
+<code>matchers</code> sections. For the request part, you can see that, for all fields but
+<code>valueWithoutAMatcher</code>, the values of the regular expressions that the stub should
+contain are explicitly set. For the <code>valueWithoutAMatcher</code>, the verification takes place
+in the same way as without the use of matchers. In that case, the test performs an
+equality check.</p>
+</div>
+<div class="paragraph">
+<p>For the response side in the <code>bodyMatchers</code> section, we define the dynamic parts in a
+similar manner. The only difference is that the <code>byType</code> matchers are also present. The
+verifier engine checks four fields to verify whether the response from the test
+has a value for which the JSON path matches the given field, is of the same type as the one
+defined in the response body, and passes the following check (based on the method being called):</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>For <code>$.valueWithTypeMatch</code>, the engine checks whether the type is the same.</p>
+</li>
+<li>
+<p>For <code>$.valueWithMin</code>, the engine checks the type and asserts whether the size is greater
+than or equal to the minimum occurrence.</p>
+</li>
+<li>
+<p>For <code>$.valueWithMax</code>, the engine checks the type and asserts whether the size is
+smaller than or equal to the maximum occurrence.</p>
+</li>
+<li>
+<p>For <code>$.valueWithMinMax</code>, the engine checks the type and asserts whether the size is
+between the minimum and maximum occurrence.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The resulting test resembles the following example (note that an <code>and</code> section
+separates the autogenerated assertions and the assertion from matchers):</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">// given:
+ MockMvcRequestSpecification request = given()
+   .header("Content-Type", "application/json")
+   .body("{\"duck\":123,\"alpha\":\"abc\",\"number\":123,\"aBoolean\":true,\"date\":\"2017-01-01\",\"dateTime\":\"2017-01-01T01:23:45\",\"time\":\"01:02:34\",\"valueWithoutAMatcher\":\"foo\",\"valueWithTypeMatch\":\"string\",\"key\":{\"complex.key\":\"foo\"}}");
+
+// when:
+ ResponseOptions response = given().spec(request)
+   .get("/get");
+
+// then:
+ assertThat(response.statusCode()).isEqualTo(200);
+ assertThat(response.header("Content-Type")).matches("application/json.*");
+// and:
+ DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
+ assertThatJson(parsedJson).field("['valueWithoutAMatcher']").isEqualTo("foo");
+// and:
+ assertThat(parsedJson.read("$.duck", String.class)).matches("[0-9]{3}");
+ assertThat(parsedJson.read("$.duck", Integer.class)).isEqualTo(123);
+ assertThat(parsedJson.read("$.alpha", String.class)).matches("[\\p{L}]*");
+ assertThat(parsedJson.read("$.alpha", String.class)).isEqualTo("abc");
+ assertThat(parsedJson.read("$.number", String.class)).matches("-?(\\d*\\.\\d+|\\d+)");
+ assertThat(parsedJson.read("$.aBoolean", String.class)).matches("(true|false)");
+ assertThat(parsedJson.read("$.date", String.class)).matches("(\\d\\d\\d\\d)-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])");
+ assertThat(parsedJson.read("$.dateTime", String.class)).matches("([0-9]{4})-(1[0-2]|0[1-9])-(3[01]|0[1-9]|[12][0-9])T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])");
+ assertThat(parsedJson.read("$.time", String.class)).matches("(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9])");
+ assertThat((Object) parsedJson.read("$.valueWithTypeMatch")).isInstanceOf(java.lang.String.class);
+ assertThat((Object) parsedJson.read("$.valueWithMin")).isInstanceOf(java.util.List.class);
+ assertThat((java.lang.Iterable) parsedJson.read("$.valueWithMin", java.util.Collection.class)).as("$.valueWithMin").hasSizeGreaterThanOrEqualTo(1);
+ assertThat((Object) parsedJson.read("$.valueWithMax")).isInstanceOf(java.util.List.class);
+ assertThat((java.lang.Iterable) parsedJson.read("$.valueWithMax", java.util.Collection.class)).as("$.valueWithMax").hasSizeLessThanOrEqualTo(3);
+ assertThat((Object) parsedJson.read("$.valueWithMinMax")).isInstanceOf(java.util.List.class);
+ assertThat((java.lang.Iterable) parsedJson.read("$.valueWithMinMax", java.util.Collection.class)).as("$.valueWithMinMax").hasSizeBetween(1, 3);
+ assertThat((Object) parsedJson.read("$.valueWithMinEmpty")).isInstanceOf(java.util.List.class);
+ assertThat((java.lang.Iterable) parsedJson.read("$.valueWithMinEmpty", java.util.Collection.class)).as("$.valueWithMinEmpty").hasSizeGreaterThanOrEqualTo(0);
+ assertThat((Object) parsedJson.read("$.valueWithMaxEmpty")).isInstanceOf(java.util.List.class);
+ assertThat((java.lang.Iterable) parsedJson.read("$.valueWithMaxEmpty", java.util.Collection.class)).as("$.valueWithMaxEmpty").hasSizeLessThanOrEqualTo(0);
+ assertThatValueIsANumber(parsedJson.read("$.duck"));
+ assertThat(parsedJson.read("$.['key'].['complex.key']", String.class)).isEqualTo("foo");</code></pre>
+</div>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+Notice that, for the <code>byCommand</code> method, the example calls the
+<code>assertThatValueIsANumber</code>. This method must be defined in the test base class or be
+statically imported to your tests. Notice that the <code>byCommand</code> call was converted to
+<code>assertThatValueIsANumber(parsedJson.read("$.duck"));</code>. That means that the engine took
+the method name and passed the proper JSON path as a parameter to it.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The resulting WireMock stub is in the following example:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">                    '''
+{
+  "request" : {
+    "urlPath" : "/get",
+    "method" : "POST",
+    "headers" : {
+      "Content-Type" : {
+        "matches" : "application/json.*"
+      }
+    },
+    "bodyPatterns" : [ {
+      "matchesJsonPath" : "$.['list'].['some'].['nested'][?(@.['anothervalue'] == 4)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.['valueWithoutAMatcher'] == 'foo')]"
+    }, {
+      "matchesJsonPath" : "$[?(@.['valueWithTypeMatch'] == 'string')]"
+    }, {
+      "matchesJsonPath" : "$.['list'].['someother'].['nested'][?(@.['json'] == 'with value')]"
+    }, {
+      "matchesJsonPath" : "$.['list'].['someother'].['nested'][?(@.['anothervalue'] == 4)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.duck =~ /([0-9]{3})/)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.duck == 123)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.alpha =~ /([\\\\p{L}]*)/)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.alpha == 'abc')]"
+    }, {
+      "matchesJsonPath" : "$[?(@.number =~ /(-?(\\\\d*\\\\.\\\\d+|\\\\d+))/)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.aBoolean =~ /((true|false))/)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.date =~ /((\\\\d\\\\d\\\\d\\\\d)-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01]))/)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.dateTime =~ /(([0-9]{4})-(1[0-2]|0[1-9])-(3[01]|0[1-9]|[12][0-9])T(2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9]))/)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.time =~ /((2[0-3]|[01][0-9]):([0-5][0-9]):([0-5][0-9]))/)]"
+    }, {
+      "matchesJsonPath" : "$.list.some.nested[?(@.json =~ /(.*)/)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.valueWithMin.size() &gt;= 1)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.valueWithMax.size() &lt;= 3)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.valueWithMinMax.size() &gt;= 1 &amp;&amp; @.valueWithMinMax.size() &lt;= 3)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.valueWithOccurrence.size() &gt;= 4 &amp;&amp; @.valueWithOccurrence.size() &lt;= 4)]"
+    } ]
+  },
+  "response" : {
+    "status" : 200,
+    "body" : "{\\"duck\\":123,\\"alpha\\":\\"abc\\",\\"number\\":123,\\"aBoolean\\":true,\\"date\\":\\"2017-01-01\\",\\"dateTime\\":\\"2017-01-01T01:23:45\\",\\"time\\":\\"01:02:34\\",\\"valueWithoutAMatcher\\":\\"foo\\",\\"valueWithTypeMatch\\":\\"string\\",\\"valueWithMin\\":[1,2,3],\\"valueWithMax\\":[1,2,3],\\"valueWithMinMax\\":[1,2,3],\\"valueWithOccurrence\\":[1,2,3,4]}",
+    "headers" : {
+      "Content-Type" : "application/json"
+    },
+    "transformers" : [ "response-template" ]
+  }
+}
+'''</code></pre>
+</div>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+If you use a <code>matcher</code>, the part of the request and response that the
+<code>matcher</code> addresses with the JSON Path gets removed from the assertion. In the case of
+verifying a collection, you must create matchers for <strong>all</strong> the elements of the
+collection.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>Consider the following example:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
+    request {
+        method 'GET'
+        url("/foo")
+    }
+    response {
+        status OK()
+        body(events: [[
+                                 operation          : 'EXPORT',
+                                 eventId            : '16f1ed75-0bcc-4f0d-a04d-3121798faf99',
+                                 status             : 'OK'
+                         ], [
+                                 operation          : 'INPUT_PROCESSING',
+                                 eventId            : '3bb4ac82-6652-462f-b6d1-75e424a0024a',
+                                 status             : 'OK'
+                         ]
+                ]
+        )
+        bodyMatchers {
+            jsonPath('$.events[0].operation', byRegex('.+'))
+            jsonPath('$.events[0].eventId', byRegex('^([a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12})$'))
+            jsonPath('$.events[0].status', byRegex('.+'))
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The preceding code leads to creating the following test (the code block shows only the assertion section):</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">and:
+    DocumentContext parsedJson = JsonPath.parse(response.body.asString())
+    assertThatJson(parsedJson).array("['events']").contains("['eventId']").isEqualTo("16f1ed75-0bcc-4f0d-a04d-3121798faf99")
+    assertThatJson(parsedJson).array("['events']").contains("['operation']").isEqualTo("EXPORT")
+    assertThatJson(parsedJson).array("['events']").contains("['operation']").isEqualTo("INPUT_PROCESSING")
+    assertThatJson(parsedJson).array("['events']").contains("['eventId']").isEqualTo("3bb4ac82-6652-462f-b6d1-75e424a0024a")
+    assertThatJson(parsedJson).array("['events']").contains("['status']").isEqualTo("OK")
+and:
+    assertThat(parsedJson.read("\$.events[0].operation", String.class)).matches(".+")
+    assertThat(parsedJson.read("\$.events[0].eventId", String.class)).matches("^([a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12})\$")
+    assertThat(parsedJson.read("\$.events[0].status", String.class)).matches(".+")</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>As you can see, the assertion is malformed. Only the first element of the array got
+asserted. In order to fix this, you should apply the assertion to the whole <code>$.events</code>
+collection and assert it with the <code>byCommand(&#8230;&#8203;)</code> method.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="contract-dsl-async"><a class="anchor" href="#contract-dsl-async"></a><a class="link" href="#contract-dsl-async">3.2.5. Asynchronous Support</a></h4>
+<div class="paragraph">
+<p>If you use asynchronous communication on the server side (your controllers are
+returning <code>Callable</code>, <code>DeferredResult</code>, and so on), then, inside your contract, you must
+provide an <code>async()</code> method in the <code>response</code> section. The following code shows an example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        method GET()
+        url '/get'
+    }
+    response {
+        status OK()
+        body 'Passed'
+        async()
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">response:
+    async: true</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class contract implements Supplier&lt;Collection&lt;Contract&gt;&gt; {
+
+    @Override
+    public Collection&lt;Contract&gt; get() {
+        return Collections.singletonList(Contract.make(c -&gt; {
+            c.request(r -&gt; {
+                // ...
+            });
+            c.response(r -&gt; {
+                r.async();
+                // ...
+            });
+        }));
+    }
+
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">import org.springframework.cloud.contract.spec.ContractDsl.Companion.contract
+
+contract {
+    request {
+        // ...
+    }
+    response {
+        async = true
+        // ...
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You can also use the <code>fixedDelayMilliseconds</code> method or property to add delay to your stubs.
+The following example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        method GET()
+        url '/get'
+    }
+    response {
+        status 200
+        body 'Passed'
+        fixedDelayMilliseconds 1000
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">response:
+    fixedDelayMilliseconds: 1000</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class contract implements Supplier&lt;Collection&lt;Contract&gt;&gt; {
+
+    @Override
+    public Collection&lt;Contract&gt; get() {
+        return Collections.singletonList(Contract.make(c -&gt; {
+            c.request(r -&gt; {
+                // ...
+            });
+            c.response(r -&gt; {
+                r.fixedDelayMilliseconds(1000);
+                // ...
+            });
+        }));
+    }
+
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">import org.springframework.cloud.contract.spec.ContractDsl.Companion.contract
+
+contract {
+    request {
+        // ...
+    }
+    response {
+        delay = fixedMilliseconds(1000)
+        // ...
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="contract-dsl-xml"><a class="anchor" href="#contract-dsl-xml"></a><a class="link" href="#contract-dsl-xml">3.2.6. XML Support for HTTP</a></h4>
+<div class="paragraph">
+<p>For HTTP contracts, we also support using XML in the request and response body.
+The XML body has to be passed within the <code>body</code> element
+as a <code>String</code> or <code>GString</code>. Also, body matchers can be provided for
+both the request and the response. In place of the <code>jsonPath(&#8230;&#8203;)</code> method, the <code>org.springframework.cloud.contract.spec.internal.BodyMatchers.xPath</code>
+method should be used, with the desired <code>xPath</code> provided as the first argument
+and the appropriate <code>MatchingType</code> as second. All the body matchers apart from <code>byType()</code> are supported.</p>
+</div>
+<div class="paragraph">
+<p>The following example shows a Groovy DSL contract with XML in the response body:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">                    Contract.make {
+                        request {
+                            method GET()
+                            urlPath '/get'
+                            headers {
+                                contentType(applicationXml())
+                            }
+                        }
+                        response {
+                            status(OK())
+                            headers {
+                                contentType(applicationXml())
+                            }
+                            body """
+&lt;test&gt;
+&lt;duck type='xtype'&gt;123&lt;/duck&gt;
+&lt;alpha&gt;abc&lt;/alpha&gt;
+&lt;list&gt;
+&lt;elem&gt;abc&lt;/elem&gt;
+&lt;elem&gt;def&lt;/elem&gt;
+&lt;elem&gt;ghi&lt;/elem&gt;
+&lt;/list&gt;
+&lt;number&gt;123&lt;/number&gt;
+&lt;aBoolean&gt;true&lt;/aBoolean&gt;
+&lt;date&gt;2017-01-01&lt;/date&gt;
+&lt;dateTime&gt;2017-01-01T01:23:45&lt;/dateTime&gt;
+&lt;time&gt;01:02:34&lt;/time&gt;
+&lt;valueWithoutAMatcher&gt;foo&lt;/valueWithoutAMatcher&gt;
+&lt;key&gt;&lt;complex&gt;foo&lt;/complex&gt;&lt;/key&gt;
+&lt;/test&gt;"""
+                            bodyMatchers {
+                                xPath('/test/duck/text()', byRegex("[0-9]{3}"))
+                                xPath('/test/duck/text()', byCommand('equals($it)'))
+                                xPath('/test/duck/xxx', byNull())
+                                xPath('/test/duck/text()', byEquality())
+                                xPath('/test/alpha/text()', byRegex(onlyAlphaUnicode()))
+                                xPath('/test/alpha/text()', byEquality())
+                                xPath('/test/number/text()', byRegex(number()))
+                                xPath('/test/date/text()', byDate())
+                                xPath('/test/dateTime/text()', byTimestamp())
+                                xPath('/test/time/text()', byTime())
+                                xPath('/test/*/complex/text()', byEquality())
+                                xPath('/test/duck/@type', byEquality())
+                            }
+                        }
+                    }</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">include::/opt/jenkins/data/workspace/spring-cloud-contract-master-ci/spring-cloud-contract-verifier/src/test/resources/yml/contract_rest_xml.yml</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import java.util.function.Supplier;
+
+import org.springframework.cloud.contract.spec.Contract;
+
+class contract_xml implements Supplier&lt;Contract&gt; {
+
+    @Override
+    public Contract get() {
+        return Contract.make(c -&gt; {
+            c.request(r -&gt; {
+                r.method(r.GET());
+                r.urlPath("/get");
+                r.headers(h -&gt; {
+                    h.contentType(h.applicationXml());
+                });
+            });
+            c.response(r -&gt; {
+                r.status(r.OK());
+                r.headers(h -&gt; {
+                    h.contentType(h.applicationXml());
+                });
+                r.body("&lt;test&gt;\n" + "&lt;duck type='xtype'&gt;123&lt;/duck&gt;\n"
+                        + "&lt;alpha&gt;abc&lt;/alpha&gt;\n" + "&lt;list&gt;\n" + "&lt;elem&gt;abc&lt;/elem&gt;\n"
+                        + "&lt;elem&gt;def&lt;/elem&gt;\n" + "&lt;elem&gt;ghi&lt;/elem&gt;\n" + "&lt;/list&gt;\n"
+                        + "&lt;number&gt;123&lt;/number&gt;\n" + "&lt;aBoolean&gt;true&lt;/aBoolean&gt;\n"
+                        + "&lt;date&gt;2017-01-01&lt;/date&gt;\n"
+                        + "&lt;dateTime&gt;2017-01-01T01:23:45&lt;/dateTime&gt;\n"
+                        + "&lt;time&gt;01:02:34&lt;/time&gt;\n"
+                        + "&lt;valueWithoutAMatcher&gt;foo&lt;/valueWithoutAMatcher&gt;\n"
+                        + "&lt;key&gt;&lt;complex&gt;foo&lt;/complex&gt;&lt;/key&gt;\n" + "&lt;/test&gt;");
+                r.bodyMatchers(m -&gt; {
+                    m.xPath("/test/duck/text()", m.byRegex("[0-9]{3}"));
+                    m.xPath("/test/duck/text()", m.byCommand("equals($it)"));
+                    m.xPath("/test/duck/xxx", m.byNull());
+                    m.xPath("/test/duck/text()", m.byEquality());
+                    m.xPath("/test/alpha/text()", m.byRegex(r.onlyAlphaUnicode()));
+                    m.xPath("/test/alpha/text()", m.byEquality());
+                    m.xPath("/test/number/text()", m.byRegex(r.number()));
+                    m.xPath("/test/date/text()", m.byDate());
+                    m.xPath("/test/dateTime/text()", m.byTimestamp());
+                    m.xPath("/test/time/text()", m.byTime());
+                    m.xPath("/test/*/complex/text()", m.byEquality());
+                    m.xPath("/test/duck/@type", m.byEquality());
+                });
+            });
+        });
+    };
+
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">import org.springframework.cloud.contract.spec.ContractDsl.Companion.contract
+
+contract {
+    request {
+        method = GET
+        urlPath = path("/get")
+        headers {
+            contentType = APPLICATION_XML
+        }
+    }
+    response {
+        status = OK
+        headers {
+            contentType =APPLICATION_XML
+        }
+        body = body("&lt;test&gt;\n" + "&lt;duck type='xtype'&gt;123&lt;/duck&gt;\n"
+                + "&lt;alpha&gt;abc&lt;/alpha&gt;\n" + "&lt;list&gt;\n" + "&lt;elem&gt;abc&lt;/elem&gt;\n"
+                + "&lt;elem&gt;def&lt;/elem&gt;\n" + "&lt;elem&gt;ghi&lt;/elem&gt;\n" + "&lt;/list&gt;\n"
+                + "&lt;number&gt;123&lt;/number&gt;\n" + "&lt;aBoolean&gt;true&lt;/aBoolean&gt;\n"
+                + "&lt;date&gt;2017-01-01&lt;/date&gt;\n"
+                + "&lt;dateTime&gt;2017-01-01T01:23:45&lt;/dateTime&gt;\n"
+                + "&lt;time&gt;01:02:34&lt;/time&gt;\n"
+                + "&lt;valueWithoutAMatcher&gt;foo&lt;/valueWithoutAMatcher&gt;\n"
+                + "&lt;key&gt;&lt;complex&gt;foo&lt;/complex&gt;&lt;/key&gt;\n" + "&lt;/test&gt;")
+        bodyMatchers {
+            xPath("/test/duck/text()", byRegex("[0-9]{3}"))
+            xPath("/test/duck/text()", byCommand("equals(\$it)"))
+            xPath("/test/duck/xxx", byNull)
+            xPath("/test/duck/text()", byEquality)
+            xPath("/test/alpha/text()", byRegex(onlyAlphaUnicode))
+            xPath("/test/alpha/text()", byEquality)
+            xPath("/test/number/text()", byRegex(number))
+            xPath("/test/date/text()", byDate)
+            xPath("/test/dateTime/text()", byTimestamp)
+            xPath("/test/time/text()", byTime)
+            xPath("/test/*/complex/text()", byEquality)
+            xPath("/test/duck/@type", byEquality)
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following example shows an automatically generated test for XML in the response body:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Test
+public void validate_xmlMatches() throws Exception {
+    // given:
+    MockMvcRequestSpecification request = given()
+                .header("Content-Type", "application/xml");
+
+    // when:
+    ResponseOptions response = given().spec(request).get("/get");
+
+    // then:
+    assertThat(response.statusCode()).isEqualTo(200);
+    // and:
+    DocumentBuilder documentBuilder = DocumentBuilderFactory.newInstance()
+                    .newDocumentBuilder();
+    Document parsedXml = documentBuilder.parse(new InputSource(
+                new StringReader(response.getBody().asString())));
+    // and:
+    assertThat(valueFromXPath(parsedXml, "/test/list/elem/text()")).isEqualTo("abc");
+    assertThat(valueFromXPath(parsedXml,"/test/list/elem[2]/text()")).isEqualTo("def");
+    assertThat(valueFromXPath(parsedXml, "/test/duck/text()")).matches("[0-9]{3}");
+    assertThat(nodeFromXPath(parsedXml, "/test/duck/xxx")).isNull();
+    assertThat(valueFromXPath(parsedXml, "/test/alpha/text()")).matches("[\\p{L}]*");
+    assertThat(valueFromXPath(parsedXml, "/test/*/complex/text()")).isEqualTo("foo");
+    assertThat(valueFromXPath(parsedXml, "/test/duck/@type")).isEqualTo("xtype");
+    }</code></pre>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="contract-dsl-multiple"><a class="anchor" href="#contract-dsl-multiple"></a><a class="link" href="#contract-dsl-multiple">3.2.7. Multiple Contracts in One File</a></h4>
+<div class="paragraph">
+<p>You can define multiple contracts in one file. Such a contract might resemble the
+following example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">import org.springframework.cloud.contract.spec.Contract
+
+[
+    Contract.make {
+        name("should post a user")
+        request {
+            method 'POST'
+            url('/users/1')
+        }
+        response {
+            status OK()
+        }
+    },
+    Contract.make {
+        request {
+            method 'POST'
+            url('/users/2')
+        }
+        response {
+            status OK()
+        }
+    }
+]</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">---
+name: should post a user
+request:
+  method: POST
+  url: /users/1
+response:
+  status: 200
+---
+request:
+  method: POST
+  url: /users/2
+response:
+  status: 200
+---
+request:
+  method: POST
+  url: /users/3
+response:
+  status: 200</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">java</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class contract implements Supplier&lt;Collection&lt;Contract&gt;&gt; {
+
+    @Override
+    public Collection&lt;Contract&gt; get() {
+        return Arrays.asList(
+            Contract.make(c -&gt; {
+                c.name("should post a user");
+                // ...
+            }), Contract.make(c -&gt; {
+                // ...
+            }), Contract.make(c -&gt; {
+                // ...
+            })
+        );
+    }
+
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">kotlin</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-kotlin hljs" data-lang="kotlin">import org.springframework.cloud.contract.spec.ContractDsl.Companion.contract
+
+arrayOf(
+    contract {
+        name("should post a user")
+        // ...
+    },
+    contract {
+        // ...
+    },
+    contract {
+        // ...
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>In the preceding example, one contract has the <code>name</code> field and the other does not. This
+leads to generation of two tests that look more or less like the following:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package org.springframework.cloud.contract.verifier.tests.com.hello;
+
+import com.example.TestBase;
+import com.jayway.jsonpath.DocumentContext;
+import com.jayway.jsonpath.JsonPath;
+import com.jayway.restassured.module.mockmvc.specification.MockMvcRequestSpecification;
+import com.jayway.restassured.response.ResponseOptions;
+import org.junit.Test;
+
+import static com.jayway.restassured.module.mockmvc.RestAssuredMockMvc.*;
+import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson;
+import static org.assertj.core.api.Assertions.assertThat;
+
+public class V1Test extends TestBase {
+
+    @Test
+    public void validate_should_post_a_user() throws Exception {
+        // given:
+            MockMvcRequestSpecification request = given();
+
+        // when:
+            ResponseOptions response = given().spec(request)
+                    .post("/users/1");
+
+        // then:
+            assertThat(response.statusCode()).isEqualTo(200);
+    }
+
+    @Test
+    public void validate_withList_1() throws Exception {
+        // given:
+            MockMvcRequestSpecification request = given();
+
+        // when:
+            ResponseOptions response = given().spec(request)
+                    .post("/users/2");
+
+        // then:
+            assertThat(response.statusCode()).isEqualTo(200);
+    }
+
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Notice that, for the contract that has the <code>name</code> field, the generated test method is named
+<code>validate_should_post_a_user</code>. The one that does not have the <code>name</code> field is called
+<code>validate_withList_1</code>. It corresponds to the name of the file <code>WithList.groovy</code> and the
+index of the contract in the list.</p>
+</div>
+<div class="paragraph">
+<p>The generated stubs are shown in the following example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code>should post a user.json
+1_WithList.json</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The first file got the <code>name</code> parameter from the contract. The second
+got the name of the contract file (<code>WithList.groovy</code>) prefixed with the index (in this
+case, the contract had an index of <code>1</code> in the list of contracts in the file).</p>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+It is much better to name your contracts, because doing so makes
+your tests far more meaningful.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="contract-stateful-contracts"><a class="anchor" href="#contract-stateful-contracts"></a><a class="link" href="#contract-stateful-contracts">3.2.8. Stateful Contracts</a></h4>
+<div class="paragraph">
+<p>Stateful contracts (known also as scenarios) are contract definitions that should be read
+in order. This might be useful in the following situations:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>You want to execute the contract in a precisely defined order, since you use Spring
+Cloud Contract to test your stateful application</p>
+</li>
+</ul>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+We really discourage you from doing that, since contract tests should be stateless.
+</td>
+</tr>
+</table>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>You want the same endpoint to return different results for the same request.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>To create stateful contracts (or scenarios), you need to
+use the proper naming convention while creating your contracts. The convention
+requires including an order number followed by an underscore. This works regardless
+of whether you work with YAML or Groovy. The following listing shows an example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code>my_contracts_dir\
+  scenario1\
+    1_login.groovy
+    2_showCart.groovy
+    3_logout.groovy</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Such a tree causes Spring Cloud Contract Verifier to generate WireMock&#8217;s scenario with a
+name of <code>scenario1</code> and the three following steps:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>login, marked as <code>Started</code> pointing to&#8230;&#8203;</p>
+</li>
+<li>
+<p>showCart, marked as <code>Step1</code> pointing to&#8230;&#8203;</p>
+</li>
+<li>
+<p>logout, marked as <code>Step2</code> (which closes the scenario).</p>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>You can find more details about WireMock scenarios at
+<a href="https://wiremock.org/docs/stateful-behaviour/">https://wiremock.org/docs/stateful-behaviour/</a>.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="feature-integrations"><a class="anchor" href="#feature-integrations"></a><a class="link" href="#feature-integrations">3.3. Integrations</a></h3>
+<div class="sect3">
+<h4 id="features-jax-rs"><a class="anchor" href="#features-jax-rs"></a><a class="link" href="#features-jax-rs">3.3.1. JAX-RS</a></h4>
+<div class="paragraph">
+<p>The Spring Cloud Contract supports the JAX-RS 2 Client API. The base class needs
+to define <code>protected WebTarget webTarget</code> and server initialization. The only option for
+testing JAX-RS API is to start a web server. Also, a request with a body needs to have a
+content type be set. Otherwise, the default of <code>application/octet-stream</code> gets used.</p>
+</div>
+<div class="paragraph">
+<p>In order to use JAX-RS mode, use the following settings:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">testMode = 'JAXRSCLIENT'</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The following example shows a generated test API:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">                    """\
+package com.example;
+
+import com.jayway.jsonpath.DocumentContext;
+import com.jayway.jsonpath.JsonPath;
+import org.junit.Test;
+import org.junit.Rule;
+import javax.ws.rs.client.Entity;
+import javax.ws.rs.core.Response;
+
+import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat;
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*;
+import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson;
+import static javax.ws.rs.client.Entity.*;
+
+@SuppressWarnings("rawtypes")
+public class FooTest {
+\tWebTarget webTarget;
+
+\t@Test
+\tpublic void validate_() throws Exception {
+
+\t\t// when:
+\t\t\tResponse response = webTarget
+\t\t\t\t\t\t\t.path("/users")
+\t\t\t\t\t\t\t.queryParam("limit", "10")
+\t\t\t\t\t\t\t.queryParam("offset", "20")
+\t\t\t\t\t\t\t.queryParam("filter", "email")
+\t\t\t\t\t\t\t.queryParam("sort", "name")
+\t\t\t\t\t\t\t.queryParam("search", "55")
+\t\t\t\t\t\t\t.queryParam("age", "99")
+\t\t\t\t\t\t\t.queryParam("name", "Denis.Stepanov")
+\t\t\t\t\t\t\t.queryParam("email", "bob@email.com")
+\t\t\t\t\t\t\t.request()
+\t\t\t\t\t\t\t.build("GET")
+\t\t\t\t\t\t\t.invoke();
+\t\t\tString responseAsString = response.readEntity(String.class);
+
+\t\t// then:
+\t\t\tassertThat(response.getStatus()).isEqualTo(200);
+
+\t\t// and:
+\t\t\tDocumentContext parsedJson = JsonPath.parse(responseAsString);
+\t\t\tassertThatJson(parsedJson).field("['property1']").isEqualTo("a");
+\t}
+
+}
+
+"""</code></pre>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="feature-webflux"><a class="anchor" href="#feature-webflux"></a><a class="link" href="#feature-webflux">3.3.2. WebFlux with WebTestClient</a></h4>
+<div class="paragraph">
+<p>You can work with WebFlux by using WebTestClient. The following listing shows how to
+configure WebTestClient as the test mode:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;testMode&gt;WEBTESTCLIENT&lt;/testMode&gt;
+    &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
+        testMode = 'WEBTESTCLIENT'
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following example shows how to set up a WebTestClient base class and RestAssured
+for WebFlux:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">import io.restassured.module.webtestclient.RestAssuredWebTestClient;
+import org.junit.Before;
+
+public abstract class BeerRestBase {
+
+    @Before
+    public void setup() {
+        RestAssuredWebTestClient.standaloneSetup(
+        new ProducerController(personToCheck -&gt; personToCheck.age &gt;= 20));
+    }
+}
+}</code></pre>
+</div>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+The <code>WebTestClient</code> mode is faster than the <code>EXPLICIT</code> mode.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="feature-webflux-explicit"><a class="anchor" href="#feature-webflux-explicit"></a><a class="link" href="#feature-webflux-explicit">3.3.3. WebFlux with Explicit Mode</a></h4>
+<div class="paragraph">
+<p>You can also use WebFlux with the explicit mode in your generated tests
+to work with WebFlux. The following example shows how to configure using explicit mode:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;testMode&gt;EXPLICIT&lt;/testMode&gt;
+    &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
+        testMode = 'EXPLICIT'
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following example shows how to set up a base class and RestAssured for Web Flux:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@RunWith(SpringRunner.class)
+@SpringBootTest(classes = BeerRestBase.Config.class,
+        webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT,
+        properties = "server.port=0")
+public abstract class BeerRestBase {
+
+    // your tests go here
+
+    // in this config class you define all controllers and mocked services
+@Configuration
+@EnableAutoConfiguration
+static class Config {
+
+    @Bean
+    PersonCheckingService personCheckingService()  {
+        return personToCheck -&gt; personToCheck.age &gt;= 20;
+    }
+
+    @Bean
+    ProducerController producerController() {
+        return new ProducerController(personCheckingService());
+    }
+}
+
+}</code></pre>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-context-paths"><a class="anchor" href="#features-context-paths"></a><a class="link" href="#features-context-paths">3.3.4. Working with Context Paths</a></h4>
+<div class="paragraph">
+<p>Spring Cloud Contract supports context paths.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+<div class="paragraph">
+<p>The only change needed to fully support context paths is the switch on the
+producer side. Also, the autogenerated tests must use explicit mode. The  consumer
+side remains untouched. In order for the generated test to pass, you must use explicit
+mode. The following example shows how to set the test mode to <code>EXPLICIT</code>:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;testMode&gt;EXPLICIT&lt;/testMode&gt;
+    &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
+        testMode = 'EXPLICIT'
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>That way, you generate a test that does not use MockMvc. It means that you generate
+real requests and you need to set up your generated test&#8217;s base class to work on a real
+socket.</p>
+</div>
+<div class="paragraph">
+<p>Consider the following contract:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.spec.Contract.make {
+    request {
+        method 'GET'
+        url '/my-context-path/url'
+    }
+    response {
+        status OK()
+    }
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The following example shows how to set up a base class and RestAssured:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">import io.restassured.RestAssured;
+import org.junit.Before;
+import org.springframework.boot.web.server.LocalServerPort;
+import org.springframework.boot.test.context.SpringBootTest;
+
+@SpringBootTest(classes = ContextPathTestingBaseClass.class, webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
+class ContextPathTestingBaseClass {
+
+    @LocalServerPort int port;
+
+    @Before
+    public void setup() {
+        RestAssured.baseURI = "http://localhost";
+        RestAssured.port = this.port;
+    }
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>If you do it this way:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>All of your requests in the autogenerated tests are sent to the real endpoint with your
+context path included (for example, <code>/my-context-path/url</code>).</p>
+</li>
+<li>
+<p>Your contracts reflect that you have a context path. Your generated stubs also have
+that information (for example, in the stubs, you have to call <code>/my-context-path/url</code>).</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-rest-docs"><a class="anchor" href="#features-rest-docs"></a><a class="link" href="#features-rest-docs">3.3.5. Working with REST Docs</a></h4>
+<div class="paragraph">
+<p>You can use <a href="https://projects.spring.io/spring-restdocs">Spring REST Docs</a> to generate
+documentation (for example, in Asciidoc format) for an HTTP API with Spring MockMvc,
+<code>WebTestClient</code>, or RestAssured. At the same time that you generate documentation for your API, you can also
+generate WireMock stubs by using Spring Cloud Contract WireMock. To do so, write your
+normal REST Docs test cases and use <code>@AutoConfigureRestDocs</code> to have stubs be
+automatically generated in the REST Docs output directory.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/rest-docs.png" alt="rest docs" width="1237" height="835">
+</div>
+</div>
+<div class="paragraph">
+<p>The following example uses <code>MockMvc</code>:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
+@SpringBootTest
+@AutoConfigureRestDocs(outputDir = "target/snippets")
+@AutoConfigureMockMvc
+public class ApplicationTests {
+
+    @Autowired
+    private MockMvc mockMvc;
+
+    @Test
+    public void contextLoads() throws Exception {
+        mockMvc.perform(get("/resource"))
+                .andExpect(content().string("Hello World"))
+                .andDo(document("resource"));
+    }
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>This test generates a WireMock stub at <code>target/snippets/stubs/resource.json</code>. It matches
+all <code>GET</code> requests to the <code>/resource</code> path. The same example with <code>WebTestClient</code> (used
+for testing Spring WebFlux applications) would be as follows:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
+@SpringBootTest
+@AutoConfigureRestDocs(outputDir = "target/snippets")
+@AutoConfigureWebTestClient
+public class ApplicationTests {
+
+    @Autowired
+    private WebTestClient client;
+
+    @Test
+    public void contextLoads() throws Exception {
+        client.get().uri("/resource").exchange()
+                .expectBody(String.class).isEqualTo("Hello World")
+                .consumeWith(document("resource"));
+    }
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Without any additional configuration, these tests create a stub with a request matcher
+for the HTTP method and all headers except <code>host</code> and <code>content-length</code>. To match the
+request more precisely (for example, to match the body of a POST or PUT), we need to
+explicitly create a request matcher. Doing so has two effects:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Creating a stub that matches only in the way you specify.</p>
+</li>
+<li>
+<p>Asserting that the request in the test case also matches the same conditions.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The main entry point for this feature is <code>WireMockRestDocs.verify()</code>, which can be used
+as a substitute for the <code>document()</code> convenience method, as the following
+example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import static org.springframework.cloud.contract.wiremock.restdocs.WireMockRestDocs.verify;
+
+@RunWith(SpringRunner.class)
+@SpringBootTest
+@AutoConfigureRestDocs(outputDir = "target/snippets")
+@AutoConfigureMockMvc
+public class ApplicationTests {
+
+    @Autowired
+    private MockMvc mockMvc;
+
+    @Test
+    public void contextLoads() throws Exception {
+        mockMvc.perform(post("/resource")
+                .content("{\"id\":\"123456\",\"message\":\"Hello World\"}"))
+                .andExpect(status().isOk())
+                .andDo(verify().jsonPath("$.id")
+                .andDo(document("resource"));
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The preceding contract specifies that any valid POST with an <code>id</code> field receives the response
+defined in this test. You can chain together calls to <code>.jsonPath()</code> to add additional
+matchers. If JSON Path is unfamiliar, the <a href="https://github.com/jayway/JsonPath">JayWay
+documentation</a> can help you get up to speed. The <code>WebTestClient</code> version of this test
+has a similar <code>verify()</code> static helper that you insert in the same place.</p>
+</div>
+<div class="paragraph">
+<p>Instead of the <code>jsonPath</code> and <code>contentType</code> convenience methods, you can also use the
+WireMock APIs to verify that the request matches the created stub, as the
+following example shows:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Test
+public void contextLoads() throws Exception {
+    mockMvc.perform(post("/resource")
+            .content("{\"id\":\"123456\",\"message\":\"Hello World\"}"))
+            .andExpect(status().isOk())
+            .andDo(verify()
+                    .wiremock(WireMock.post(
+                        urlPathEquals("/resource"))
+                        .withRequestBody(matchingJsonPath("$.id"))
+                        .andDo(document("post-resource"));
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The WireMock API is rich. You can match headers, query parameters, and the request body by
+regex as well as by JSON path. You can use these features to create stubs with a wider
+range of parameters. The preceding example generates a stub resembling the following example:</p>
+</div>
+<div class="listingblock">
+<div class="title">post-resource.json</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
+  "request" : {
+    "url" : "/resource",
+    "method" : "POST",
+    "bodyPatterns" : [ {
+      "matchesJsonPath" : "$.id"
+    }]
+  },
+  "response" : {
+    "status" : 200,
+    "body" : "Hello World",
+    "headers" : {
+      "X-Application-Context" : "application:-1",
+      "Content-Type" : "text/plain"
+    }
+  }
+}</code></pre>
+</div>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+You can use either the <code>wiremock()</code> method or the <code>jsonPath()</code> and <code>contentType()</code>
+methods to create request matchers, but you cannot use both approaches.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>On the consumer side, you can make the <code>resource.json</code> generated earlier in this section
+available on the classpath (by
+<a href="#features-stub-runner-publishing-stubs-as-jars">Publishing Stubs as JARs</a>, for example). After that, you can create a stub that uses WireMock in a
+number of different ways, including by using
+<code>@AutoConfigureWireMock(stubs="classpath:resource.json")</code>, as described earlier in this
+document.</p>
+</div>
+<div class="sect4">
+<h5 id="features-rest-docs-contracts"><a class="anchor" href="#features-rest-docs-contracts"></a><a class="link" href="#features-rest-docs-contracts">Generating Contracts with REST Docs</a></h5>
+<div class="paragraph">
+<p>You can also generate Spring Cloud Contract DSL files and documentation with Spring REST
+Docs. If you do so in combination with Spring Cloud WireMock, you get both the contracts
+and the stubs.</p>
+</div>
+<div class="paragraph">
+<p>Why would you want to use this feature? Some people in the community asked questions
+about a situation in which they would like to move to DSL-based contract definition,
+but they already have a lot of Spring MVC tests. Using this feature lets you generate
+the contract files that you can later modify and move to folders (defined in your
+configuration) so that the plugin finds them.</p>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+You might wonder why this functionality is in the WireMock module. The functionality
+is there because it makes sense to generate both the contracts and the stubs.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>Consider the following test:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">        this.mockMvc
+                .perform(post("/foo").accept(MediaType.APPLICATION_PDF)
+                        .accept(MediaType.APPLICATION_JSON)
+                        .contentType(MediaType.APPLICATION_JSON)
+                        .content("{\"foo\": 23, \"bar\" : \"baz\" }"))
+                .andExpect(status().isOk()).andExpect(content().string("bar"))
+                // first WireMock
+                .andDo(WireMockRestDocs.verify().jsonPath("$[?(@.foo &gt;= 20)]")
+                        .jsonPath("$[?(@.bar in ['baz','bazz','bazzz'])]")
+                        .contentType(MediaType.valueOf("application/json")))
+                // then Contract DSL documentation
+                .andDo(document("index", SpringCloudContractRestDocs.dslContract()));</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The preceding test creates the stub presented in the previous section, generating both
+the contract and a documentation file.</p>
+</div>
+<div class="paragraph">
+<p>The contract is called <code>index.groovy</code> and might resemble the following example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">import org.springframework.cloud.contract.spec.Contract
+
+Contract.make {
+    request {
+        method 'POST'
+        url '/foo'
+        body('''
+            {"foo": 23 }
+        ''')
+        headers {
+            header('''Accept''', '''application/json''')
+            header('''Content-Type''', '''application/json''')
+        }
+    }
+    response {
+        status OK()
+        body('''
+        bar
+        ''')
+        headers {
+            header('''Content-Type''', '''application/json;charset=UTF-8''')
+            header('''Content-Length''', '''3''')
+        }
+        bodyMatchers {
+            jsonPath('$[?(@.foo &gt;= 20)]', byType())
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The generated document (formatted in Asciidoc in this case) contains a formatted
+contract. The location of this file would be <code>index/dsl-contract.adoc</code>.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="features-messaging"><a class="anchor" href="#features-messaging"></a><a class="link" href="#features-messaging">3.4. Messaging</a></h3>
+<div class="paragraph">
+<p>Spring Cloud Contract lets you verify applications that use messaging as a
+means of communication. All of the integrations shown in this document work with Spring,
+but you can also create one of your own and use that.</p>
+</div>
+<div class="sect3">
+<h4 id="contract-dsl-messaging-top-level"><a class="anchor" href="#contract-dsl-messaging-top-level"></a><a class="link" href="#contract-dsl-messaging-top-level">3.4.1. Messaging DSL Top-Level Elements</a></h4>
+<div class="paragraph">
+<p>The DSL for messaging looks a little bit different than the one that focuses on HTTP. The
+following sections explain the differences:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="#contract-dsl-output-triggered-method">Output Triggered by a Method</a></p>
+</li>
+<li>
+<p><a href="#contract-dsl-output-triggered-message">Output Triggered by a Message</a></p>
+</li>
+<li>
+<p><a href="#contract-dsl-consumer-producer">Consumer/Producer</a></p>
+</li>
+<li>
+<p><a href="#contract-dsl-messaging-common">Common</a></p>
+</li>
+</ul>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-output-triggered-method"><a class="anchor" href="#contract-dsl-output-triggered-method"></a><a class="link" href="#contract-dsl-output-triggered-method">Output Triggered by a Method</a></h5>
+<div class="paragraph">
+<p>The output message can be triggered by calling a method (such as a <code>Scheduler</code> when a contract was
+started and a message was sent), as shown in the following example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">def dsl = Contract.make {
+    // Human readable description
+    description 'Some description'
+    // Label by means of which the output message can be triggered
+    label 'some_label'
+    // input to the contract
+    input {
+        // the contract will be triggered by a method
+        triggeredBy('bookReturnedTriggered()')
+    }
+    // output message of the contract
+    outputMessage {
+        // destination to which the output message will be sent
+        sentTo('output')
+        // the body of the output message
+        body('''{ "bookName" : "foo" }''')
+        // the headers of the output message
+        headers {
+            header('BOOK-NAME', 'foo')
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy"># Human readable description
+description: Some description
+# Label by means of which the output message can be triggered
+label: some_label
+input:
+  # the contract will be triggered by a method
+  triggeredBy: bookReturnedTriggered()
+# output message of the contract
+outputMessage:
+  # destination to which the output message will be sent
+  sentTo: output
+  # the body of the output message
+  body:
+    bookName: foo
+  # the headers of the output message
+  headers:
+    BOOK-NAME: foo</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>In the previous example case, the output message is sent to <code>output</code> if a method called
+<code>bookReturnedTriggered</code> is executed. On the message publisher&#8217;s side, we generate a
+test that calls that method to trigger the message. On the consumer side, you can use
+the <code>some_label</code> to trigger the message.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-output-triggered-message"><a class="anchor" href="#contract-dsl-output-triggered-message"></a><a class="link" href="#contract-dsl-output-triggered-message">Output Triggered by a Message</a></h5>
+<div class="paragraph">
+<p>The output message can be triggered by receiving a message, as shown in the following
+example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">def dsl = Contract.make {
+    description 'Some Description'
+    label 'some_label'
+    // input is a message
+    input {
+        // the message was received from this destination
+        messageFrom('input')
+        // has the following body
+        messageBody([
+                bookName: 'foo'
+        ])
+        // and the following headers
+        messageHeaders {
+            header('sample', 'header')
+        }
+    }
+    outputMessage {
+        sentTo('output')
+        body([
+                bookName: 'foo'
+        ])
+        headers {
+            header('BOOK-NAME', 'foo')
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy"># Human readable description
+description: Some description
+# Label by means of which the output message can be triggered
+label: some_label
+# input is a message
+input:
+  messageFrom: input
+  # has the following body
+  messageBody:
+    bookName: 'foo'
+  # and the following headers
+  messageHeaders:
+    sample: 'header'
+# output message of the contract
+outputMessage:
+  # destination to which the output message will be sent
+  sentTo: output
+  # the body of the output message
+  body:
+    bookName: foo
+  # the headers of the output message
+  headers:
+    BOOK-NAME: foo</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>In the preceding example, the output message is sent to <code>output</code> if a proper message is
+received on the <code>input</code> destination. On the message publisher&#8217;s side, the engine
+generates a test that sends the input message to the defined destination. On the
+consumer side, you can either send a message to the input destination or use a label
+(<code>some_label</code> in the example) to trigger the message.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-consumer-producer"><a class="anchor" href="#contract-dsl-consumer-producer"></a><a class="link" href="#contract-dsl-consumer-producer">Consumer/Producer</a></h5>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+This section is valid only for Groovy DSL.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>In HTTP, you have a notion of <code>client</code>/<code>stub and `server</code>/<code>test</code> notation. You can also
+use those paradigms in messaging. In addition, Spring Cloud Contract Verifier also
+provides the <code>consumer</code> and <code>producer</code> methods, as presented in the following example
+(note that you can use either <code>$</code> or <code>value</code> methods to provide <code>consumer</code> and <code>producer</code>
+parts):</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">                    Contract.make {
+                name "foo"
+                        label 'some_label'
+                        input {
+                            messageFrom value(consumer('jms:output'), producer('jms:input'))
+                            messageBody([
+                                    bookName: 'foo'
+                            ])
+                            messageHeaders {
+                                header('sample', 'header')
+                            }
+                        }
+                        outputMessage {
+                            sentTo $(consumer('jms:input'), producer('jms:output'))
+                            body([
+                                    bookName: 'foo'
+                            ])
+                        }
+                    }</code></pre>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="contract-dsl-messaging-common"><a class="anchor" href="#contract-dsl-messaging-common"></a><a class="link" href="#contract-dsl-messaging-common">Common</a></h5>
+<div class="paragraph">
+<p>In the <code>input</code> or <code>outputMessage</code> section, you can call <code>assertThat</code> with the name
+of a <code>method</code> (for example, <code>assertThatMessageIsOnTheQueue()</code>) that you have defined in the
+base class or in a static import. Spring Cloud Contract runs that method
+in the generated test.</p>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-messaging-integrations"><a class="anchor" href="#features-messaging-integrations"></a><a class="link" href="#features-messaging-integrations">3.4.2. Integrations</a></h4>
+<div class="paragraph">
+<p>You can use one of the following four integration configurations:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Apache Camel</p>
+</li>
+<li>
+<p>Spring Integration</p>
+</li>
+<li>
+<p>Spring Cloud Stream</p>
+</li>
+<li>
+<p>Spring AMQP</p>
+</li>
+<li>
+<p>Spring JMS (requires embedded broker)</p>
+</li>
+<li>
+<p>Spring Kafka (requires embedded broker)</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Since we use Spring Boot, if you have added one of these libraries to the classpath, all
+the messaging configuration is automatically set up.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+Remember to put <code>@AutoConfigureMessageVerifier</code> on the base class of your
+generated tests. Otherwise, the messaging part of Spring Cloud Contract does not
+work.
+</td>
+</tr>
+</table>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+<div class="paragraph">
+<p>If you want to use Spring Cloud Stream, remember to add a test dependency on
+<code>org.springframework.cloud:spring-cloud-stream</code>, as  follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-stream&lt;/artifactId&gt;
+    &lt;type&gt;test-jar&lt;/type&gt;
+    &lt;scope&gt;test&lt;/scope&gt;
+    &lt;classifier&gt;test-binder&lt;/classifier&gt;
+&lt;/dependency&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">testImplementation(group: 'org.springframework.cloud', name: 'spring-cloud-stream', classifier: 'test-binder')</code></pre>
+</div>
+</div>
+</div>
+</div>
+</td>
+</tr>
+</table>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-manual"><a class="anchor" href="#features-messaging-manual"></a><a class="link" href="#features-messaging-manual">Manual Integration Testing</a></h5>
+<div class="paragraph">
+<p>The main interface used by the tests is
+<code>org.springframework.cloud.contract.verifier.messaging.MessageVerifier</code>.
+It defines how to send and receive messages. You can create your own implementation to
+achieve the same goal.</p>
+</div>
+<div class="paragraph">
+<p>In a test, you can inject a <code>ContractVerifierMessageExchange</code> to send and receive
+messages that follow the contract. Then add <code>@AutoConfigureMessageVerifier</code> to your test.
+The following example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringTestRunner.class)
+@SpringBootTest
+@AutoConfigureMessageVerifier
+public static class MessagingContractTests {
+
+  @Autowired
+  private MessageVerifier verifier;
+  ...
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+If your tests require stubs as well, then <code>@AutoConfigureStubRunner</code> includes the
+messaging configuration, so you only need the one annotation.
+</td>
+</tr>
+</table>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-messaging-test-generation"><a class="anchor" href="#features-messaging-test-generation"></a><a class="link" href="#features-messaging-test-generation">3.4.3. Producer Side  Messaging Test Generation</a></h4>
+<div class="paragraph">
+<p>Having the <code>input</code> or <code>outputMessage</code> sections in your DSL results in creation of tests
+on the publisher&#8217;s side. By default, JUnit 4 tests are created. However, there is also a
+possibility to create JUnit 5, TestNG, or Spock tests.</p>
+</div>
+<div class="paragraph">
+<p>There are three main scenarios that we should take into consideration:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Scenario 1: There is no input message that produces an output message. The output
+message  is triggered by a component inside the application (for example, a scheduler).</p>
+</li>
+<li>
+<p>Scenario 2: The input message triggers an output message.</p>
+</li>
+<li>
+<p>Scenario 3: The input message is consumed, and there is no output message.</p>
+</li>
+</ul>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+The destination passed to <code>messageFrom</code> or <code>sentTo</code> can have different
+meanings for different messaging implementations. For Stream and Integration, it is
+first resolved as a <code>destination</code> of a channel. Then, if there is no such <code>destination</code>
+it is resolved as a channel name. For Camel, that&#8217;s a certain component (for example,
+<code>jms</code>).
+</td>
+</tr>
+</table>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-scenario1"><a class="anchor" href="#features-messaging-scenario1"></a><a class="link" href="#features-messaging-scenario1">Scenario 1: No Input Message</a></h5>
+<div class="paragraph">
+<p>Consider the following contract:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">def contractDsl = Contract.make {
+    name "foo"
+    label 'some_label'
+    input {
+        triggeredBy('bookReturnedTriggered()')
+    }
+    outputMessage {
+        sentTo('activemq:output')
+        body('''{ "bookName" : "foo" }''')
+        headers {
+            header('BOOK-NAME', 'foo')
+            messagingContentType(applicationJson())
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">label: some_label
+input:
+  triggeredBy: bookReturnedTriggered
+outputMessage:
+  sentTo: activemq:output
+  body:
+    bookName: foo
+  headers:
+    BOOK-NAME: foo
+    contentType: application/json</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>For the preceding example, the following test would be created:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">JUnit</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">                    '''\
+package com.example;
+
+import com.jayway.jsonpath.DocumentContext;
+import com.jayway.jsonpath.JsonPath;
+import org.junit.Test;
+import org.junit.Rule;
+import javax.inject.Inject;
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierObjectMapper;
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessage;
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessaging;
+
+import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat;
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*;
+import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson;
+import static org.springframework.cloud.contract.verifier.messaging.util.ContractVerifierMessagingUtil.headers;
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.fileToBytes;
+
+@SuppressWarnings("rawtypes")
+public class FooTest {
+\t@Inject ContractVerifierMessaging contractVerifierMessaging;
+\t@Inject ContractVerifierObjectMapper contractVerifierObjectMapper;
+
+\t@Test
+\tpublic void validate_foo() throws Exception {
+\t\t// when:
+\t\t\tbookReturnedTriggered();
+
+\t\t// then:
+\t\t\tContractVerifierMessage response = contractVerifierMessaging.receive("activemq:output");
+\t\t\tassertThat(response).isNotNull();
+
+\t\t// and:
+\t\t\tassertThat(response.getHeader("BOOK-NAME")).isNotNull();
+\t\t\tassertThat(response.getHeader("BOOK-NAME").toString()).isEqualTo("foo");
+\t\t\tassertThat(response.getHeader("contentType")).isNotNull();
+\t\t\tassertThat(response.getHeader("contentType").toString()).isEqualTo("application/json");
+
+\t\t// and:
+\t\t\tDocumentContext parsedJson = JsonPath.parse(contractVerifierObjectMapper.writeValueAsString(response.getPayload()));
+\t\t\tassertThatJson(parsedJson).field("['bookName']").isEqualTo("foo");
+\t}
+
+}
+
+'''</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Spock</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">                    '''\
+package com.example
+
+import com.jayway.jsonpath.DocumentContext
+import com.jayway.jsonpath.JsonPath
+import spock.lang.Specification
+import javax.inject.Inject
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierObjectMapper
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessage
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessaging
+
+import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*
+import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson
+import static org.springframework.cloud.contract.verifier.messaging.util.ContractVerifierMessagingUtil.headers
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.fileToBytes
+
+@SuppressWarnings("rawtypes")
+class FooSpec extends Specification {
+\t@Inject ContractVerifierMessaging contractVerifierMessaging
+\t@Inject ContractVerifierObjectMapper contractVerifierObjectMapper
+
+\tdef validate_foo() throws Exception {
+\t\twhen:
+\t\t\tbookReturnedTriggered()
+
+\t\tthen:
+\t\t\tContractVerifierMessage response = contractVerifierMessaging.receive("activemq:output")
+\t\t\tresponse != null
+
+\t\tand:
+\t\t\tresponse.getHeader("BOOK-NAME") != null
+\t\t\tresponse.getHeader("BOOK-NAME").toString() == 'foo'
+\t\t\tresponse.getHeader("contentType") != null
+\t\t\tresponse.getHeader("contentType").toString() == 'application/json'
+
+\t\tand:
+\t\t\tDocumentContext parsedJson = JsonPath.parse(contractVerifierObjectMapper.writeValueAsString(response.getPayload()))
+\t\t\tassertThatJson(parsedJson).field("['bookName']").isEqualTo("foo")
+\t}
+
+}
+
+'''</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-scenario2"><a class="anchor" href="#features-messaging-scenario2"></a><a class="link" href="#features-messaging-scenario2">Scenario 2: Output Triggered by Input</a></h5>
+<div class="paragraph">
+<p>Consider the following contract:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">def contractDsl = Contract.make {
+    name "foo"
+    label 'some_label'
+    input {
+        messageFrom('jms:input')
+        messageBody([
+                bookName: 'foo'
+        ])
+        messageHeaders {
+            header('sample', 'header')
+        }
+    }
+    outputMessage {
+        sentTo('jms:output')
+        body([
+                bookName: 'foo'
+        ])
+        headers {
+            header('BOOK-NAME', 'foo')
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">label: some_label
+input:
+  messageFrom: jms:input
+  messageBody:
+    bookName: 'foo'
+  messageHeaders:
+    sample: header
+outputMessage:
+  sentTo: jms:output
+  body:
+    bookName: foo
+  headers:
+    BOOK-NAME: foo</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>For the preceding contract, the following test would be created:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">JUnit</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">                    '''\
+package com.example;
+
+import com.jayway.jsonpath.DocumentContext;
+import com.jayway.jsonpath.JsonPath;
+import org.junit.Test;
+import org.junit.Rule;
+import javax.inject.Inject;
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierObjectMapper;
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessage;
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessaging;
+
+import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat;
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*;
+import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson;
+import static org.springframework.cloud.contract.verifier.messaging.util.ContractVerifierMessagingUtil.headers;
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.fileToBytes;
+
+@SuppressWarnings("rawtypes")
+public class FooTest {
+\t@Inject ContractVerifierMessaging contractVerifierMessaging;
+\t@Inject ContractVerifierObjectMapper contractVerifierObjectMapper;
+
+\t@Test
+\tpublic void validate_foo() throws Exception {
+\t\t// given:
+\t\t\tContractVerifierMessage inputMessage = contractVerifierMessaging.create(
+\t\t\t\t\t"{\\"bookName\\":\\"foo\\"}"
+\t\t\t\t\t\t, headers()
+\t\t\t\t\t\t\t.header("sample", "header")
+\t\t\t);
+
+\t\t// when:
+\t\t\tcontractVerifierMessaging.send(inputMessage, "jms:input");
+
+\t\t// then:
+\t\t\tContractVerifierMessage response = contractVerifierMessaging.receive("jms:output");
+\t\t\tassertThat(response).isNotNull();
+
+\t\t// and:
+\t\t\tassertThat(response.getHeader("BOOK-NAME")).isNotNull();
+\t\t\tassertThat(response.getHeader("BOOK-NAME").toString()).isEqualTo("foo");
+
+\t\t// and:
+\t\t\tDocumentContext parsedJson = JsonPath.parse(contractVerifierObjectMapper.writeValueAsString(response.getPayload()));
+\t\t\tassertThatJson(parsedJson).field("['bookName']").isEqualTo("foo");
+\t}
+
+}
+
+'''</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Spock</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">                    """\
+package com.example
+
+import com.jayway.jsonpath.DocumentContext
+import com.jayway.jsonpath.JsonPath
+import spock.lang.Specification
+import javax.inject.Inject
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierObjectMapper
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessage
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessaging
+
+import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*
+import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson
+import static org.springframework.cloud.contract.verifier.messaging.util.ContractVerifierMessagingUtil.headers
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.fileToBytes
+
+@SuppressWarnings("rawtypes")
+class FooSpec extends Specification {
+\t@Inject ContractVerifierMessaging contractVerifierMessaging
+\t@Inject ContractVerifierObjectMapper contractVerifierObjectMapper
+
+\tdef validate_foo() throws Exception {
+\t\tgiven:
+\t\t\tContractVerifierMessage inputMessage = contractVerifierMessaging.create(
+\t\t\t\t\t'''{"bookName":"foo"}'''
+\t\t\t\t\t\t, headers()
+\t\t\t\t\t\t\t.header("sample", "header")
+\t\t\t)
+
+\t\twhen:
+\t\t\tcontractVerifierMessaging.send(inputMessage, "jms:input")
+
+\t\tthen:
+\t\t\tContractVerifierMessage response = contractVerifierMessaging.receive("jms:output")
+\t\t\tresponse != null
+
+\t\tand:
+\t\t\tresponse.getHeader("BOOK-NAME") != null
+\t\t\tresponse.getHeader("BOOK-NAME").toString() == 'foo'
+
+\t\tand:
+\t\t\tDocumentContext parsedJson = JsonPath.parse(contractVerifierObjectMapper.writeValueAsString(response.getPayload()))
+\t\t\tassertThatJson(parsedJson).field("['bookName']").isEqualTo("foo")
+\t}
+
+}
+
+"""</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-scenario3"><a class="anchor" href="#features-messaging-scenario3"></a><a class="link" href="#features-messaging-scenario3">Scenario 3: No Output Message</a></h5>
+<div class="paragraph">
+<p>Consider the following contract:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">groovy</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">def contractDsl = Contract.make {
+    name "foo"
+    label 'some_label'
+    input {
+        messageFrom('jms:delete')
+        messageBody([
+                bookName: 'foo'
+        ])
+        messageHeaders {
+            header('sample', 'header')
+        }
+        assertThat('bookWasDeleted()')
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">yml</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">label: some_label
+input:
+  messageFrom: jms:delete
+  messageBody:
+    bookName: 'foo'
+  messageHeaders:
+    sample: header
+  assertThat: bookWasDeleted()</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>For the preceding contract, the following test would be created:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">JUnit</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">                    """\
+package com.example;
+
+import com.jayway.jsonpath.DocumentContext;
+import com.jayway.jsonpath.JsonPath;
+import org.junit.Test;
+import org.junit.Rule;
+import javax.inject.Inject;
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierObjectMapper;
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessage;
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessaging;
+
+import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat;
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*;
+import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson;
+import static org.springframework.cloud.contract.verifier.messaging.util.ContractVerifierMessagingUtil.headers;
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.fileToBytes;
+
+@SuppressWarnings("rawtypes")
+public class FooTest {
+\t@Inject ContractVerifierMessaging contractVerifierMessaging;
+\t@Inject ContractVerifierObjectMapper contractVerifierObjectMapper;
+
+\t@Test
+\tpublic void validate_foo() throws Exception {
+\t\t// given:
+\t\t\tContractVerifierMessage inputMessage = contractVerifierMessaging.create(
+\t\t\t\t\t"{\\"bookName\\":\\"foo\\"}"
+\t\t\t\t\t\t, headers()
+\t\t\t\t\t\t\t.header("sample", "header")
+\t\t\t);
+
+\t\t// when:
+\t\t\tcontractVerifierMessaging.send(inputMessage, "jms:delete");
+\t\t\tbookWasDeleted();
+
+\t}
+
+}
+
+"""</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Spock</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">                    """\
+package com.example
+
+import com.jayway.jsonpath.DocumentContext
+import com.jayway.jsonpath.JsonPath
+import spock.lang.Specification
+import javax.inject.Inject
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierObjectMapper
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessage
+import org.springframework.cloud.contract.verifier.messaging.internal.ContractVerifierMessaging
+
+import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*
+import static com.toomuchcoding.jsonassert.JsonAssertion.assertThatJson
+import static org.springframework.cloud.contract.verifier.messaging.util.ContractVerifierMessagingUtil.headers
+import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.fileToBytes
+
+@SuppressWarnings("rawtypes")
+class FooSpec extends Specification {
+\t@Inject ContractVerifierMessaging contractVerifierMessaging
+\t@Inject ContractVerifierObjectMapper contractVerifierObjectMapper
+
+\tdef validate_foo() throws Exception {
+\t\tgiven:
+\t\t\tContractVerifierMessage inputMessage = contractVerifierMessaging.create(
+\t\t\t\t\t'''{"bookName":"foo"}'''
+\t\t\t\t\t\t, headers()
+\t\t\t\t\t\t\t.header("sample", "header")
+\t\t\t)
+
+\t\twhen:
+\t\t\tcontractVerifierMessaging.send(inputMessage, "jms:delete")
+\t\t\tbookWasDeleted()
+
+\t\tthen:
+\t\t\tnoExceptionThrown()
+\t}
+
+}
+"""</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-messaging-consumer"><a class="anchor" href="#features-messaging-consumer"></a><a class="link" href="#features-messaging-consumer">3.4.4. Consumer Stub Generation</a></h4>
+<div class="paragraph">
+<p>Unlike in the HTTP part, in messaging, we need to publish the contract definition inside the JAR with
+a stub. Then it is parsed on the consumer side, and proper stubbed routes are created.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+If you have multiple frameworks on the classpath, Stub Runner needs to
+define which one should be used. Assume that you have AMQP, Spring Cloud Stream, and Spring Integration
+on the classpath and that you want to use Spring AMQP. Then you need to set
+<code>stubrunner.stream.enabled=false</code> and <code>stubrunner.integration.enabled=false</code>.
+That way, the only remaining framework is Spring AMQP.
+</td>
+</tr>
+</table>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-triggering"><a class="anchor" href="#features-messaging-stub-triggering"></a><a class="link" href="#features-messaging-stub-triggering">Stub triggering</a></h5>
+<div class="paragraph">
+<p>To trigger a message, use the <code>StubTrigger</code> interface, as the following example shows:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package org.springframework.cloud.contract.stubrunner;
+
+import java.util.Collection;
+import java.util.Map;
+
+/**
+ * Contract for triggering stub messages.
+ *
+ * @author Marcin Grzejszczak
+ */
+public interface StubTrigger {
+
+    /**
+     * Triggers an event by a given label for a given {@code groupid:artifactid} notation.
+     * You can use only {@code artifactId} too.
+     *
+     * Feature related to messaging.
+     * @param ivyNotation ivy notation of a stub
+     * @param labelName name of the label to trigger
+     * @return true - if managed to run a trigger
+     */
+    boolean trigger(String ivyNotation, String labelName);
+
+    /**
+     * Triggers an event by a given label.
+     *
+     * Feature related to messaging.
+     * @param labelName name of the label to trigger
+     * @return true - if managed to run a trigger
+     */
+    boolean trigger(String labelName);
+
+    /**
+     * Triggers all possible events.
+     *
+     * Feature related to messaging.
+     * @return true - if managed to run a trigger
+     */
+    boolean trigger();
+
+    /**
+     * Feature related to messaging.
+     * @return a mapping of ivy notation of a dependency to all the labels it has.
+     */
+    Map&lt;String, Collection&lt;String&gt;&gt; labels();
+
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>For convenience, the <code>StubFinder</code> interface extends <code>StubTrigger</code>, so you only need one
+or the other in your tests.</p>
+</div>
+<div class="paragraph">
+<p><code>StubTrigger</code> gives you the following options to trigger a message:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="#features-messaging-trigger-label">Trigger by Label</a></p>
+</li>
+<li>
+<p><a href="#features-messaging-trigger-group-artifact-ids">Trigger by Group and Artifact Ids</a></p>
+</li>
+<li>
+<p><a href="#features-messaging-trigger-artifact-ids">Trigger by Artifact IDs</a></p>
+</li>
+<li>
+<p><a href="#features-messaging-trigger-all-messages">Trigger All Messages</a></p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-trigger-label"><a class="anchor" href="#features-messaging-trigger-label"></a><a class="link" href="#features-messaging-trigger-label">Trigger by Label</a></h5>
+<div class="paragraph">
+<p>The following example shows how to trigger a message with a label:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('return_book_1')</code></pre>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-trigger-group-artifact-ids"><a class="anchor" href="#features-messaging-trigger-group-artifact-ids"></a><a class="link" href="#features-messaging-trigger-group-artifact-ids">Trigger by Group and Artifact Ids</a></h5>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('org.springframework.cloud.contract.verifier.stubs:streamService', 'return_book_1')</code></pre>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-trigger-artifact-ids"><a class="anchor" href="#features-messaging-trigger-artifact-ids"></a><a class="link" href="#features-messaging-trigger-artifact-ids">Trigger by Artifact IDs</a></h5>
+<div class="paragraph">
+<p>The following example shows how to trigger a message from artifact IDs:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('streamService', 'return_book_1')</code></pre>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-trigger-all-messages"><a class="anchor" href="#features-messaging-trigger-all-messages"></a><a class="link" href="#features-messaging-trigger-all-messages">Trigger All Messages</a></h5>
+<div class="paragraph">
+<p>The following example shows how to trigger all messages:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger()</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-messaging-stub-runner-camel"><a class="anchor" href="#features-messaging-stub-runner-camel"></a><a class="link" href="#features-messaging-stub-runner-camel">3.4.5. Consumer Side Messaging With Apache Camel</a></h4>
+<div class="paragraph">
+<p>Spring Cloud Contract Stub Runner&#8217;s messaging module gives you an easy way to integrate with Apache Camel.
+For the provided artifacts, it automatically downloads the stubs and registers the required
+routes.</p>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-camel-adding"><a class="anchor" href="#features-messaging-stub-runner-camel-adding"></a><a class="link" href="#features-messaging-stub-runner-camel-adding">Adding Apache Camel to the Project</a></h5>
+<div class="paragraph">
+<p>You can have both Apache Camel and Spring Cloud Contract Stub Runner on the classpath.
+Remember to annotate your test class with <code>@AutoConfigureStubRunner</code>.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-camel-disabling"><a class="anchor" href="#features-messaging-stub-runner-camel-disabling"></a><a class="link" href="#features-messaging-stub-runner-camel-disabling">Disabling the Functionality</a></h5>
+<div class="paragraph">
+<p>If you need to disable this functionality, set the <code>stubrunner.camel.enabled=false</code> property.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-camel-example"><a class="anchor" href="#features-messaging-stub-runner-camel-example"></a><a class="link" href="#features-messaging-stub-runner-camel-example">Examples</a></h5>
+<div class="paragraph">
+<p>Assume that we have the following Maven repository with deployed stubs for the
+<code>camelService</code> application.</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── .m2
+    └── repository
+        └── io
+            └── codearte
+                └── accurest
+                    └── stubs
+                        └── camelService
+                            ├── 0.0.1-SNAPSHOT
+                            │   ├── camelService-0.0.1-SNAPSHOT.pom
+                            │   ├── camelService-0.0.1-SNAPSHOT-stubs.jar
+                            │   └── maven-metadata-local.xml
+                            └── maven-metadata-local.xml</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Further assume that the stubs contain the following structure:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── META-INF
+│   └── MANIFEST.MF
+└── repository
+    ├── accurest
+    │   ├── bookDeleted.groovy
+    │   ├── bookReturned1.groovy
+    │   └── bookReturned2.groovy
+    └── mappings</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Now consider the following contracts (we number them 1 and 2):</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
+    label 'return_book_1'
+    input {
+        triggeredBy('bookReturnedTriggered()')
+    }
+    outputMessage {
+        sentTo('jms:output')
+        body('''{ "bookName" : "foo" }''')
+        headers {
+            header('BOOK-NAME', 'foo')
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
+    label 'return_book_2'
+    input {
+        messageFrom('jms:input')
+        messageBody([
+                bookName: 'foo'
+        ])
+        messageHeaders {
+            header('sample', 'header')
+        }
+    }
+    outputMessage {
+        sentTo('jms:output')
+        body([
+                bookName: 'foo'
+        ])
+        headers {
+            header('BOOK-NAME', 'foo')
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-camel-scenario1"><a class="anchor" href="#features-messaging-stub-runner-camel-scenario1"></a><a class="link" href="#features-messaging-stub-runner-camel-scenario1">Scenario 1 (No Input Message)</a></h6>
+<div class="paragraph">
+<p>To trigger a message from the <code>return_book_1</code> label, we use the <code>StubTrigger</code> interface, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('return_book_1')</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Next, we want to listen to the output of the message sent to <code>jms:output</code>:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Exchange receivedMessage = consumerTemplate.receive('jms:output', 5000)</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The received message would then pass the following assertions:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
+assertThatBodyContainsBookNameFoo(receivedMessage.in.body)
+receivedMessage.in.headers.get('BOOK-NAME') == 'foo'</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-camel-scenario2"><a class="anchor" href="#features-messaging-stub-runner-camel-scenario2"></a><a class="link" href="#features-messaging-stub-runner-camel-scenario2">Scenario 2 (Output Triggered by Input)</a></h6>
+<div class="paragraph">
+<p>Since the route is set for you, you can send a message to the <code>jms:output</code> destination.</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">producerTemplate.
+        sendBodyAndHeaders('jms:input', new BookReturned('foo'), [sample: 'header'])</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Next, we want to listen to the output of the message sent to <code>jms:output</code>, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Exchange receivedMessage = consumerTemplate.receive('jms:output', 5000)</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The received message would pass the following assertions:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
+assertThatBodyContainsBookNameFoo(receivedMessage.in.body)
+receivedMessage.in.headers.get('BOOK-NAME') == 'foo'</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-camel-scenario3"><a class="anchor" href="#features-messaging-stub-runner-camel-scenario3"></a><a class="link" href="#features-messaging-stub-runner-camel-scenario3">Scenario 3 (Input with No Output)</a></h6>
+<div class="paragraph">
+<p>Since the route is set for you, you can send a message to the <code>jms:output</code> destination, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">producerTemplate.
+        sendBodyAndHeaders('jms:delete', new BookReturned('foo'), [sample: 'header'])</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-messaging-stub-runner-integration"><a class="anchor" href="#features-messaging-stub-runner-integration"></a><a class="link" href="#features-messaging-stub-runner-integration">3.4.6. Consumer Side Messaging with Spring Integration</a></h4>
+<div class="paragraph">
+<p>Spring Cloud Contract Stub Runner&#8217;s messaging module gives you an easy way to
+integrate with Spring Integration. For the provided artifacts, it automatically downloads
+the stubs and registers the required routes.</p>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-integration-adding"><a class="anchor" href="#features-messaging-stub-runner-integration-adding"></a><a class="link" href="#features-messaging-stub-runner-integration-adding">Adding the Runner to the Project</a></h5>
+<div class="paragraph">
+<p>You can have both Spring Integration and Spring Cloud Contract Stub Runner on the
+classpath. Remember to annotate your test class with <code>@AutoConfigureStubRunner</code>.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-integration-disabling"><a class="anchor" href="#features-messaging-stub-runner-integration-disabling"></a><a class="link" href="#features-messaging-stub-runner-integration-disabling">Disabling the Functionality</a></h5>
+<div class="paragraph">
+<p>If you need to disable this functionality, set the
+<code>stubrunner.integration.enabled=false</code> property.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-integration-example"><a class="anchor" href="#features-messaging-stub-runner-integration-example"></a><a class="link" href="#features-messaging-stub-runner-integration-example">Examples</a></h5>
+<div class="paragraph">
+<p>Assume that you have the following Maven repository with deployed stubs for the
+<code>integrationService</code> application:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── .m2
+    └── repository
+        └── io
+            └── codearte
+                └── accurest
+                    └── stubs
+                        └── integrationService
+                            ├── 0.0.1-SNAPSHOT
+                            │   ├── integrationService-0.0.1-SNAPSHOT.pom
+                            │   ├── integrationService-0.0.1-SNAPSHOT-stubs.jar
+                            │   └── maven-metadata-local.xml
+                            └── maven-metadata-local.xml</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Further assume the stubs contain the following structure:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── META-INF
+│   └── MANIFEST.MF
+└── repository
+    ├── accurest
+    │   ├── bookDeleted.groovy
+    │   ├── bookReturned1.groovy
+    │   └── bookReturned2.groovy
+    └── mappings</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Consider the following contracts (numbered 1 and 2):</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
+    label 'return_book_1'
+    input {
+        triggeredBy('bookReturnedTriggered()')
+    }
+    outputMessage {
+        sentTo('output')
+        body('''{ "bookName" : "foo" }''')
+        headers {
+            header('BOOK-NAME', 'foo')
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
+    label 'return_book_2'
+    input {
+        messageFrom('input')
+        messageBody([
+                bookName: 'foo'
+        ])
+        messageHeaders {
+            header('sample', 'header')
+        }
+    }
+    outputMessage {
+        sentTo('output')
+        body([
+                bookName: 'foo'
+        ])
+        headers {
+            header('BOOK-NAME', 'foo')
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Now consider the following Spring Integration Route:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;beans:beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+             xmlns:beans="http://www.springframework.org/schema/beans"
+             xmlns="http://www.springframework.org/schema/integration"
+             xsi:schemaLocation="http://www.springframework.org/schema/beans
+            https://www.springframework.org/schema/beans/spring-beans.xsd
+            http://www.springframework.org/schema/integration
+            http://www.springframework.org/schema/integration/spring-integration.xsd"&gt;
+
+
+    &lt;!-- REQUIRED FOR TESTING --&gt;
+    &lt;bridge input-channel="output"
+            output-channel="outputTest"/&gt;
+
+    &lt;channel id="outputTest"&gt;
+        &lt;queue/&gt;
+    &lt;/channel&gt;
+
+&lt;/beans:beans&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>These examples lend themselves to three scenarios:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p><a href="#features-messaging-stub-runner-integration-scenario1">Scenario 1 (No Input Message)</a></p>
+</li>
+<li>
+<p><a href="#features-messaging-stub-runner-integration-scenario2">Scenario 2 (Output Triggered by Input)</a></p>
+</li>
+<li>
+<p><a href="#features-messaging-stub-runner-integration-scenario3">Scenario 3 (Input with No Output)</a></p>
+</li>
+</ol>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-integration-scenario1"><a class="anchor" href="#features-messaging-stub-runner-integration-scenario1"></a><a class="link" href="#features-messaging-stub-runner-integration-scenario1">Scenario 1 (No Input Message)</a></h6>
+<div class="paragraph">
+<p>To trigger a message from the <code>return_book_1</code> label, use the <code>StubTrigger</code> interface, as
+follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('return_book_1')</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following listing shows how to listen to the output of the message sent to <code>jms:output</code>:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Message&lt;?&gt; receivedMessage = messaging.receive('outputTest')</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The received message would pass the following assertions:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
+assertJsons(receivedMessage.payload)
+receivedMessage.headers.get('BOOK-NAME') == 'foo'</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-integration-scenario2"><a class="anchor" href="#features-messaging-stub-runner-integration-scenario2"></a><a class="link" href="#features-messaging-stub-runner-integration-scenario2">Scenario 2 (Output Triggered by Input)</a></h6>
+<div class="paragraph">
+<p>Since the route is set for you, you can send a message to the <code>jms:output</code>
+destination, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">messaging.send(new BookReturned('foo'), [sample: 'header'], 'input')</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following listing shows how to listen to the output of the message sent to <code>jms:output</code>:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Message&lt;?&gt; receivedMessage = messaging.receive('outputTest')</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The received message passes the following assertions:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
+assertJsons(receivedMessage.payload)
+receivedMessage.headers.get('BOOK-NAME') == 'foo'</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-integration-scenario3"><a class="anchor" href="#features-messaging-stub-runner-integration-scenario3"></a><a class="link" href="#features-messaging-stub-runner-integration-scenario3">Scenario 3 (Input with No Output)</a></h6>
+<div class="paragraph">
+<p>Since the route is set for you, you can send a message to the <code>jms:input</code> destination, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">messaging.send(new BookReturned('foo'), [sample: 'header'], 'delete')</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-messaging-stub-runner-stream"><a class="anchor" href="#features-messaging-stub-runner-stream"></a><a class="link" href="#features-messaging-stub-runner-stream">3.4.7. Consumer Side Messaging With Spring Cloud Stream</a></h4>
+<div class="paragraph">
+<p>Spring Cloud Contract Stub Runner&#8217;s messaging module gives you an easy way to
+integrate with Spring Stream. For the provided artifacts, it automatically downloads the
+stubs and registers the required routes.</p>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-warning" title="Warning"></i>
+</td>
+<td class="content">
+If Stub Runner&#8217;s integration with the Stream <code>messageFrom</code> or <code>sentTo</code> strings
+are resolved first as the <code>destination</code> of a channel and no such <code>destination</code> exists, the
+destination is resolved as a channel name.
+</td>
+</tr>
+</table>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+<div class="paragraph">
+<p>If you want to use Spring Cloud Stream, remember to add a dependency on
+<code>org.springframework.cloud:spring-cloud-stream</code> test support, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-stream&lt;/artifactId&gt;
+    &lt;type&gt;test-jar&lt;/type&gt;
+    &lt;scope&gt;test&lt;/scope&gt;
+    &lt;classifier&gt;test-binder&lt;/classifier&gt;
+&lt;/dependency&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">testImplementation(group: 'org.springframework.cloud', name: 'spring-cloud-stream', classifier: 'test-binder')</code></pre>
+</div>
+</div>
+</div>
+</div>
+</td>
+</tr>
+</table>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-stream-adding"><a class="anchor" href="#features-messaging-stub-runner-stream-adding"></a><a class="link" href="#features-messaging-stub-runner-stream-adding">Adding the Runner to the Project</a></h5>
+<div class="paragraph">
+<p>You can have both Spring Cloud Stream and Spring Cloud Contract Stub Runner on the
+classpath. Remember to annotate your test class with <code>@AutoConfigureStubRunner</code>.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-stream-disabling"><a class="anchor" href="#features-messaging-stub-runner-stream-disabling"></a><a class="link" href="#features-messaging-stub-runner-stream-disabling">Disabling the Functionality</a></h5>
+<div class="paragraph">
+<p>If you need to disable this functionality, set the <code>stubrunner.stream.enabled=false</code>
+property.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-stream-example"><a class="anchor" href="#features-messaging-stub-runner-stream-example"></a><a class="link" href="#features-messaging-stub-runner-stream-example">Examples</a></h5>
+<div class="paragraph">
+<p>Assume that you have the following Maven repository with deployed stubs for the
+<code>streamService</code> application:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── .m2
+    └── repository
+        └── io
+            └── codearte
+                └── accurest
+                    └── stubs
+                        └── streamService
+                            ├── 0.0.1-SNAPSHOT
+                            │   ├── streamService-0.0.1-SNAPSHOT.pom
+                            │   ├── streamService-0.0.1-SNAPSHOT-stubs.jar
+                            │   └── maven-metadata-local.xml
+                            └── maven-metadata-local.xml</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Further assume the stubs contain the following structure:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── META-INF
+│   └── MANIFEST.MF
+└── repository
+    ├── accurest
+    │   ├── bookDeleted.groovy
+    │   ├── bookReturned1.groovy
+    │   └── bookReturned2.groovy
+    └── mappings</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Consider the following contracts (numbered 1 and 2):</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
+    label 'return_book_1'
+    input { triggeredBy('bookReturnedTriggered()') }
+    outputMessage {
+        sentTo('returnBook')
+        body('''{ "bookName" : "foo" }''')
+        headers { header('BOOK-NAME', 'foo') }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
+    label 'return_book_2'
+    input {
+        messageFrom('bookStorage')
+        messageBody([
+                bookName: 'foo'
+        ])
+        messageHeaders { header('sample', 'header') }
+    }
+    outputMessage {
+        sentTo('returnBook')
+        body([
+                bookName: 'foo'
+        ])
+        headers { header('BOOK-NAME', 'foo') }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Now consider the following Spring configuration:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">stubrunner.repositoryRoot: classpath:m2repo/repository/
+stubrunner.ids: org.springframework.cloud.contract.verifier.stubs:streamService:0.0.1-SNAPSHOT:stubs
+stubrunner.stubs-mode: remote
+spring:
+  cloud:
+    stream:
+      bindings:
+        output:
+          destination: returnBook
+        input:
+          destination: bookStorage
+
+server:
+  port: 0
+
+debug: true</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>These examples lend themselves to three scenarios:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="#features-messaging-stub-runner-stream-scenario1">Scenario 1 (No Input Message)</a></p>
+</li>
+<li>
+<p><a href="#features-messaging-stub-runner-stream-scenario2">Scenario 2 (Output Triggered by Input)</a></p>
+</li>
+<li>
+<p><a href="#features-messaging-stub-runner-stream-scenario3">Scenario 3 (Input with No Output)</a></p>
+</li>
+</ul>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-stream-scenario1"><a class="anchor" href="#features-messaging-stub-runner-stream-scenario1"></a><a class="link" href="#features-messaging-stub-runner-stream-scenario1">Scenario 1 (No Input Message)</a></h6>
+<div class="paragraph">
+<p>To trigger a message from the <code>return_book_1</code> label, use the <code>StubTrigger</code> interface as
+follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('return_book_1')</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following example shows how to listen to the output of the message sent to a channel whose <code>destination</code> is
+<code>returnBook</code>:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Message&lt;?&gt; receivedMessage = messaging.receive('returnBook')</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The received message passes the following assertions:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
+assertJsons(receivedMessage.payload)
+receivedMessage.headers.get('BOOK-NAME') == 'foo'</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-stream-scenario2"><a class="anchor" href="#features-messaging-stub-runner-stream-scenario2"></a><a class="link" href="#features-messaging-stub-runner-stream-scenario2">Scenario 2 (Output Triggered by Input)</a></h6>
+<div class="paragraph">
+<p>Since the route is set for you, you can send a message to the <code>bookStorage</code>
+<code>destination</code>, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">messaging.send(new BookReturned('foo'), [sample: 'header'], 'bookStorage')</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following example shows how to listen to the output of the message sent to <code>returnBook</code>:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Message&lt;?&gt; receivedMessage = messaging.receive('returnBook')</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The received message passes the following assertions:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
+assertJsons(receivedMessage.payload)
+receivedMessage.headers.get('BOOK-NAME') == 'foo'</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-stream-scenario3"><a class="anchor" href="#features-messaging-stub-runner-stream-scenario3"></a><a class="link" href="#features-messaging-stub-runner-stream-scenario3">Scenario 3 (Input with No Output)</a></h6>
+<div class="paragraph">
+<p>Since the route is set for you, you can send a message to the <code>jms:output</code>
+destination, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">messaging.send(new BookReturned('foo'), [sample: 'header'], 'delete')</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-messaging-stub-runner-amqp"><a class="anchor" href="#features-messaging-stub-runner-amqp"></a><a class="link" href="#features-messaging-stub-runner-amqp">3.4.8. Consumer Side Messaging With Spring AMQP</a></h4>
+<div class="paragraph">
+<p>Spring Cloud Contract Stub Runner&#8217;s messaging module provides an easy way to
+integrate with Spring AMQP&#8217;s Rabbit Template. For the provided artifacts, it
+automatically downloads the stubs and registers the required routes.</p>
+</div>
+<div class="paragraph">
+<p>The integration tries to work standalone (that is, without interaction with a running
+RabbitMQ message broker). It expects a <code>RabbitTemplate</code> on the application context and
+uses it as a spring boot test named <code>@SpyBean</code>. As a result, it can use the Mockito spy
+functionality to verify and inspect messages sent by the application.</p>
+</div>
+<div class="paragraph">
+<p>On the message consumer side, the stub runner considers all <code>@RabbitListener</code> annotated
+endpoints and all <code>SimpleMessageListenerContainer</code> objects on the application context.</p>
+</div>
+<div class="paragraph">
+<p>As messages are usually sent to exchanges in AMQP, the message contract contains the
+exchange name as the destination. Message listeners on the other side are bound to
+queues. Bindings connect an exchange to a queue. If message contracts are triggered, the
+Spring AMQP stub runner integration looks for bindings on the application context that
+matches this exchange. Then it collects the queues from the Spring exchanges and tries to
+find message listeners bound to these queues. The message is triggered for all matching
+message listeners.</p>
+</div>
+<div class="paragraph">
+<p>If you need to work with routing keys, you can pass them by using the <code>amqp_receivedRoutingKey</code>
+messaging header.</p>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-amqp-adding"><a class="anchor" href="#features-messaging-stub-runner-amqp-adding"></a><a class="link" href="#features-messaging-stub-runner-amqp-adding">Adding the Runner to the Project</a></h5>
+<div class="paragraph">
+<p>You can have both Spring AMQP and Spring Cloud Contract Stub Runner on the classpath and
+set the property <code>stubrunner.amqp.enabled=true</code>. Remember to annotate your test class
+with <code>@AutoConfigureStubRunner</code>.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+If you already have Stream and Integration on the classpath, you need
+to disable them explicitly by setting the  <code>stubrunner.stream.enabled=false</code> and
+<code>stubrunner.integration.enabled=false</code> properties.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-amqp-example"><a class="anchor" href="#features-messaging-stub-runner-amqp-example"></a><a class="link" href="#features-messaging-stub-runner-amqp-example">Examples</a></h5>
+<div class="paragraph">
+<p>Assume that you have the following Maven repository with a deployed stubs for the
+<code>spring-cloud-contract-amqp-test</code> application:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── .m2
+    └── repository
+        └── com
+            └── example
+                └── spring-cloud-contract-amqp-test
+                    ├── 0.4.0-SNAPSHOT
+                    │   ├── spring-cloud-contract-amqp-test-0.4.0-SNAPSHOT.pom
+                    │   ├── spring-cloud-contract-amqp-test-0.4.0-SNAPSHOT-stubs.jar
+                    │   └── maven-metadata-local.xml
+                    └── maven-metadata-local.xml</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Further assume that the stubs contain the following structure:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── META-INF
+│   └── MANIFEST.MF
+└── contracts
+    └── shouldProduceValidPersonData.groovy</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Then consider the following contract:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
+    // Human readable description
+    description 'Should produce valid person data'
+    // Label by means of which the output message can be triggered
+    label 'contract-test.person.created.event'
+    // input to the contract
+    input {
+        // the contract will be triggered by a method
+        triggeredBy('createPerson()')
+    }
+    // output message of the contract
+    outputMessage {
+        // destination to which the output message will be sent
+        sentTo 'contract-test.exchange'
+        headers {
+            header('contentType': 'application/json')
+            header('__TypeId__': 'org.springframework.cloud.contract.stubrunner.messaging.amqp.Person')
+        }
+        // the body of the output message
+        body([
+                id  : $(consumer(9), producer(regex("[0-9]+"))),
+                name: "me"
+        ])
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Now consider the following Spring configuration:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">stubrunner:
+  repositoryRoot: classpath:m2repo/repository/
+  ids: org.springframework.cloud.contract.verifier.stubs.amqp:spring-cloud-contract-amqp-test:0.4.0-SNAPSHOT:stubs
+  stubs-mode: remote
+  amqp:
+    enabled: true
+server:
+  port: 0</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-amqp-triggering"><a class="anchor" href="#features-messaging-stub-runner-amqp-triggering"></a><a class="link" href="#features-messaging-stub-runner-amqp-triggering">Triggering the Message</a></h6>
+<div class="paragraph">
+<p>To trigger a message using the contract in the preceding section, use the <code>StubTrigger</code> interface as
+follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubTrigger.trigger("contract-test.person.created.event")</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The message has a destination of <code>contract-test.exchange</code>, so the Spring AMQP stub runner
+integration looks for bindings related to this exchange, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Bean
+public Binding binding() {
+    return BindingBuilder.bind(new Queue("test.queue"))
+            .to(new DirectExchange("contract-test.exchange")).with("#");
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The binding definition binds the queue called <code>test.queue</code>. As a result, the following listener
+definition is matched and invoked with the contract message:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Bean
+public SimpleMessageListenerContainer simpleMessageListenerContainer(
+        ConnectionFactory connectionFactory,
+        MessageListenerAdapter listenerAdapter) {
+    SimpleMessageListenerContainer container = new SimpleMessageListenerContainer();
+    container.setConnectionFactory(connectionFactory);
+    container.setQueueNames("test.queue");
+    container.setMessageListener(listenerAdapter);
+
+    return container;
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Also, the following annotated listener matches and is invoked:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RabbitListener(bindings = @QueueBinding(value = @Queue("test.queue"),
+        exchange = @Exchange(value = "contract-test.exchange",
+                ignoreDeclarationExceptions = "true")))
+public void handlePerson(Person person) {
+    this.person = person;
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+The message is directly handed over to the <code>onMessage</code> method of the
+<code>MessageListener</code> associated with the matching <code>SimpleMessageListenerContainer</code>.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-amqp-configuration"><a class="anchor" href="#features-messaging-stub-runner-amqp-configuration"></a><a class="link" href="#features-messaging-stub-runner-amqp-configuration">Spring AMQP Test Configuration</a></h6>
+<div class="paragraph">
+<p>In order to avoid Spring AMQP trying to connect to a running broker during our tests, we
+configure a mock <code>ConnectionFactory</code>.</p>
+</div>
+<div class="paragraph">
+<p>To disable the mocked <code>ConnectionFactory</code>, set the following property:
+<code>stubrunner.amqp.mockConnection=false</code>, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">stubrunner:
+  amqp:
+    mockConnection: false</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-messaging-stub-runner-jms"><a class="anchor" href="#features-messaging-stub-runner-jms"></a><a class="link" href="#features-messaging-stub-runner-jms">3.4.9. Consumer Side Messaging With Spring JMS</a></h4>
+<div class="paragraph">
+<p>Spring Cloud Contract Stub Runner&#8217;s messaging module provides an easy way to
+integrate with Spring JMS.</p>
+</div>
+<div class="paragraph">
+<p>The integration assumes that you have a running instance of a JMS broker (e.g. <code>activemq</code> embedded broker).</p>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-jms-adding"><a class="anchor" href="#features-messaging-stub-runner-jms-adding"></a><a class="link" href="#features-messaging-stub-runner-jms-adding">Adding the Runner to the Project</a></h5>
+<div class="paragraph">
+<p>You need to have both Spring JMS and Spring Cloud Contract Stub Runner on the classpath. Remember to annotate your test class
+with <code>@AutoConfigureStubRunner</code>.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-jms-example"><a class="anchor" href="#features-messaging-stub-runner-jms-example"></a><a class="link" href="#features-messaging-stub-runner-jms-example">Examples</a></h5>
+<div class="paragraph">
+<p>Assume that the stub structure looks as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── stubs
+    ├── bookDeleted.groovy
+    ├── bookReturned1.groovy
+    └── bookReturned2.groovy</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Further assume the following test configuration:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">stubrunner:
+  repository-root: stubs:classpath:/stubs/
+  ids: my:stubs
+  stubs-mode: remote
+spring:
+  activemq:
+    send-timeout: 1000
+  jms:
+    template:
+      receive-timeout: 1000</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Now consider the following contracts (we number them 1 and 2):</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
+    label 'return_book_1'
+    input {
+        triggeredBy('bookReturnedTriggered()')
+    }
+    outputMessage {
+        sentTo('output')
+        body('''{ "bookName" : "foo" }''')
+        headers {
+            header('BOOK-NAME', 'foo')
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
+    label 'return_book_2'
+    input {
+        messageFrom('input')
+        messageBody([
+                bookName: 'foo'
+        ])
+        messageHeaders {
+            header('sample', 'header')
+        }
+    }
+    outputMessage {
+        sentTo('output')
+        body([
+                bookName: 'foo'
+        ])
+        headers {
+            header('BOOK-NAME', 'foo')
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-jms-scenario1"><a class="anchor" href="#features-messaging-stub-runner-jms-scenario1"></a><a class="link" href="#features-messaging-stub-runner-jms-scenario1">Scenario 1 (No Input Message)</a></h6>
+<div class="paragraph">
+<p>To trigger a message from the <code>return_book_1</code> label, we use the <code>StubTrigger</code> interface, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('return_book_1')</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Next, we want to listen to the output of the message sent to <code>output</code>:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">TextMessage receivedMessage = (TextMessage) jmsTemplate.receive('output')</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The received message would then pass the following assertions:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
+assertThatBodyContainsBookNameFoo(receivedMessage.getText())
+receivedMessage.getStringProperty('BOOK-NAME') == 'foo'</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-jms-scenario2"><a class="anchor" href="#features-messaging-stub-runner-jms-scenario2"></a><a class="link" href="#features-messaging-stub-runner-jms-scenario2">Scenario 2 (Output Triggered by Input)</a></h6>
+<div class="paragraph">
+<p>Since the route is set for you, you can send a message to the <code>output</code> destination.</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">jmsTemplate.
+        convertAndSend('input', new BookReturned('foo'), new MessagePostProcessor() {
+            @Override
+            Message postProcessMessage(Message message) throws JMSException {
+                message.setStringProperty("sample", "header")
+                return message
+            }
+        })</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Next, we want to listen to the output of the message sent to <code>output</code>, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">TextMessage receivedMessage = (TextMessage) jmsTemplate.receive('output')</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The received message would pass the following assertions:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">receivedMessage != null
+assertThatBodyContainsBookNameFoo(receivedMessage.getText())
+receivedMessage.getStringProperty('BOOK-NAME') == 'foo'</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-jms-scenario3"><a class="anchor" href="#features-messaging-stub-runner-jms-scenario3"></a><a class="link" href="#features-messaging-stub-runner-jms-scenario3">Scenario 3 (Input with No Output)</a></h6>
+<div class="paragraph">
+<p>Since the route is set for you, you can send a message to the <code>output</code> destination, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">jmsTemplate.
+        convertAndSend('delete', new BookReturned('foo'), new MessagePostProcessor() {
+            @Override
+            Message postProcessMessage(Message message) throws JMSException {
+                message.setStringProperty("sample", "header")
+                return message
+            }
+        })</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-messaging-stub-runner-kafka"><a class="anchor" href="#features-messaging-stub-runner-kafka"></a><a class="link" href="#features-messaging-stub-runner-kafka">3.4.10. Consumer Side Messaging With Spring Kafka</a></h4>
+<div class="paragraph">
+<p>Spring Cloud Contract Stub Runner&#8217;s messaging module provides an easy way to
+integrate with Spring Kafka.</p>
+</div>
+<div class="paragraph">
+<p>The integration assumes that you have a running instance of a embedded Kafka broker (via the <code>spring-kafka-test</code> dependency).</p>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-kafka-adding"><a class="anchor" href="#features-messaging-stub-runner-kafka-adding"></a><a class="link" href="#features-messaging-stub-runner-kafka-adding">Adding the Runner to the Project</a></h5>
+<div class="paragraph">
+<p>You need to have both Spring Kafka, Spring Kafka Test (to run the <code>@EmbeddedBroker</code>) and Spring Cloud Contract Stub Runner on the classpath. Remember to annotate your test class
+with <code>@AutoConfigureStubRunner</code>.</p>
+</div>
+<div class="paragraph">
+<p>With Kafka integration, in order to poll for a single message we need to register a consumer upon Spring context startup. That may lead to a situation that, when you&#8217;re on the consumer side, Stub Runner can register an additional consumer for the same group id and topic. That could lead to a situation that only one of the components would actually poll for the message. Since on the consumer side you have both the Spring Cloud Contract Stub Runner and Spring Cloud Contract Verifier classpath, we need to be able to switch off such behaviour. That&#8217;s done automatically via the <code>stubrunner.kafka.initializer.enabled</code> flag, that will disable the Contact Verifier consumer registration. If your application is both the consumer and the producer of a kafka message, you might need to manually toggle that property to <code>false</code> in the base class of your generated tests.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-messaging-stub-runner-kafka-example"><a class="anchor" href="#features-messaging-stub-runner-kafka-example"></a><a class="link" href="#features-messaging-stub-runner-kafka-example">Examples</a></h5>
+<div class="paragraph">
+<p>Assume that the stub structure looks as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── stubs
+    ├── bookDeleted.groovy
+    ├── bookReturned1.groovy
+    └── bookReturned2.groovy</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Further assume the following test configuration (notice the <code>spring.kafka.bootstrap-servers</code> pointing to the embedded broker&#8217;s IP via <code>${spring.embedded.kafka.brokers}</code>):</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">stubrunner:
+  repository-root: stubs:classpath:/stubs/
+  ids: my:stubs
+  stubs-mode: remote
+spring:
+  kafka:
+    bootstrap-servers: ${spring.embedded.kafka.brokers}
+    producer:
+      properties:
+        "value.serializer": "org.springframework.kafka.support.serializer.JsonSerializer"
+        "spring.json.trusted.packages": "*"
+    consumer:
+      properties:
+        "value.deserializer": "org.springframework.kafka.support.serializer.JsonDeserializer"
+        "value.serializer": "org.springframework.kafka.support.serializer.JsonSerializer"
+        "spring.json.trusted.packages": "*"
+      group-id: groupId</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Now consider the following contracts (we number them 1 and 2):</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
+    label 'return_book_1'
+    input {
+        triggeredBy('bookReturnedTriggered()')
+    }
+    outputMessage {
+        sentTo('output')
+        body('''{ "bookName" : "foo" }''')
+        headers {
+            header('BOOK-NAME', 'foo')
+        }
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Contract.make {
+    label 'return_book_2'
+    input {
+        messageFrom('input')
+        messageBody([
+                bookName: 'foo'
+        ])
+        messageHeaders {
+            header('sample', 'header')
+        }
+    }
+    outputMessage {
+        sentTo('output')
+        body([
+                bookName: 'foo'
+        ])
+        headers {
+            header('BOOK-NAME', 'foo')
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-kafka-scenario1"><a class="anchor" href="#features-messaging-stub-runner-kafka-scenario1"></a><a class="link" href="#features-messaging-stub-runner-kafka-scenario1">Scenario 1 (No Input Message)</a></h6>
+<div class="paragraph">
+<p>To trigger a message from the <code>return_book_1</code> label, we use the <code>StubTrigger</code> interface, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">stubFinder.trigger('return_book_1')</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Next, we want to listen to the output of the message sent to <code>output</code>:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Message receivedMessage = receiveFromOutput()</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The received message would then pass the following assertions:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">assert receivedMessage != null
+assert assertThatBodyContainsBookNameFoo(receivedMessage.getPayload())
+assert receivedMessage.getHeaders().get('BOOK-NAME') == 'foo'</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-kafka-scenario2"><a class="anchor" href="#features-messaging-stub-runner-kafka-scenario2"></a><a class="link" href="#features-messaging-stub-runner-kafka-scenario2">Scenario 2 (Output Triggered by Input)</a></h6>
+<div class="paragraph">
+<p>Since the route is set for you, you can send a message to the <code>output</code> destination.</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Message message = MessageBuilder.createMessage(new BookReturned('foo'), new MessageHeaders([sample: "header",]))
+kafkaTemplate.setDefaultTopic('input')
+kafkaTemplate.send(message)</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Next, we want to listen to the output of the message sent to <code>output</code>, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Message receivedMessage = receiveFromOutput()</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The received message would pass the following assertions:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">assert receivedMessage != null
+assert assertThatBodyContainsBookNameFoo(receivedMessage.getPayload())
+assert receivedMessage.getHeaders().get('BOOK-NAME') == 'foo'</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-messaging-stub-runner-kafka-scenario3"><a class="anchor" href="#features-messaging-stub-runner-kafka-scenario3"></a><a class="link" href="#features-messaging-stub-runner-kafka-scenario3">Scenario 3 (Input with No Output)</a></h6>
+<div class="paragraph">
+<p>Since the route is set for you, you can send a message to the <code>output</code> destination, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">Message message = MessageBuilder.createMessage(new BookReturned('foo'), new MessageHeaders([sample: "header",]))
+kafkaTemplate.setDefaultTopic('delete')
+kafkaTemplate.send(message)</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="features-stub-runner"><a class="anchor" href="#features-stub-runner"></a><a class="link" href="#features-stub-runner">3.5. Spring Cloud Contract Stub Runner</a></h3>
+<div class="paragraph">
+<p>One of the issues that you might encounter while using Spring Cloud Contract Verifier is
+passing the generated WireMock JSON stubs from the server side to the client side (or to
+various clients). The same takes place in terms of client-side generation for messaging.</p>
+</div>
+<div class="paragraph">
+<p>Copying the JSON files and setting the client side for messaging manually is out of the
+question. That is why we introduced Spring Cloud Contract Stub Runner. It can
+automatically download and run the stubs for you.</p>
+</div>
+<div class="sect3">
+<h4 id="features-stub-runner-snapshot-versions"><a class="anchor" href="#features-stub-runner-snapshot-versions"></a><a class="link" href="#features-stub-runner-snapshot-versions">3.5.1. Snapshot Versions</a></h4>
+<div class="paragraph">
+<p>You can add the additional snapshot repository to your <code>build.gradle</code> file to use snapshot
+versions, which are automatically uploaded after every successful build, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;repositories&gt;
+    &lt;repository&gt;
+        &lt;id&gt;spring-snapshots&lt;/id&gt;
+        &lt;name&gt;Spring Snapshots&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;true&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/repository&gt;
+    &lt;repository&gt;
+        &lt;id&gt;spring-milestones&lt;/id&gt;
+        &lt;name&gt;Spring Milestones&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;false&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/repository&gt;
+    &lt;repository&gt;
+        &lt;id&gt;spring-releases&lt;/id&gt;
+        &lt;name&gt;Spring Releases&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;false&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/repository&gt;
+&lt;/repositories&gt;
+&lt;pluginRepositories&gt;
+    &lt;pluginRepository&gt;
+        &lt;id&gt;spring-snapshots&lt;/id&gt;
+        &lt;name&gt;Spring Snapshots&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;true&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/pluginRepository&gt;
+    &lt;pluginRepository&gt;
+        &lt;id&gt;spring-milestones&lt;/id&gt;
+        &lt;name&gt;Spring Milestones&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;false&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/pluginRepository&gt;
+    &lt;pluginRepository&gt;
+        &lt;id&gt;spring-releases&lt;/id&gt;
+        &lt;name&gt;Spring Releases&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;false&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/pluginRepository&gt;
+&lt;/pluginRepositories&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">/*
+ We need to use the [buildscript {}] section when we have to modify
+ the classpath for the plugins. If that's not the case this section
+ can be skipped.
+
+ If you don't need to modify the classpath (e.g. add a Pact dependency),
+ then you can just set the [pluginManagement {}] section in [settings.gradle] file.
+
+ // settings.gradle
+ pluginManagement {
+    repositories {
+        // for snapshots
+        maven {url "https://repo.spring.io/snapshot"}
+        // for milestones
+        maven {url "https://repo.spring.io/milestone"}
+        // for GA versions
+        gradlePluginPortal()
+    }
+ }
+
+ */
+buildscript {
+    repositories {
+        mavenCentral()
+        mavenLocal()
+        maven { url "https://repo.spring.io/snapshot" }
+        maven { url "https://repo.spring.io/milestone" }
+        maven { url "https://repo.spring.io/release" }
+    }</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-stub-runner-publishing-stubs-as-jars"><a class="anchor" href="#features-stub-runner-publishing-stubs-as-jars"></a><a class="link" href="#features-stub-runner-publishing-stubs-as-jars">3.5.2. Publishing Stubs as JARs</a></h4>
+<div class="paragraph">
+<p>The easiest approach to publishing stubs as jars is to centralize the way stubs are kept.
+For example, you can keep them as jars in a Maven repository.</p>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+For both Maven and Gradle, the setup comes ready to work. However, you can customize
+it if you want to.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The following example shows how to publish stubs as jars:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;!-- First disable the default jar setup in the properties section --&gt;
+&lt;!-- we don't want the verifier to do a jar for us --&gt;
+&lt;spring.cloud.contract.verifier.skip&gt;true&lt;/spring.cloud.contract.verifier.skip&gt;
+
+&lt;!-- Next add the assembly plugin to your build --&gt;
+&lt;!-- we want the assembly plugin to generate the JAR --&gt;
+&lt;plugin&gt;
+    &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
+    &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
+    &lt;executions&gt;
+        &lt;execution&gt;
+            &lt;id&gt;stub&lt;/id&gt;
+            &lt;phase&gt;prepare-package&lt;/phase&gt;
+            &lt;goals&gt;
+                &lt;goal&gt;single&lt;/goal&gt;
+            &lt;/goals&gt;
+            &lt;inherited&gt;false&lt;/inherited&gt;
+            &lt;configuration&gt;
+                &lt;attach&gt;true&lt;/attach&gt;
+                &lt;descriptors&gt;
+                    ${basedir}/src/assembly/stub.xml
+                &lt;/descriptors&gt;
+            &lt;/configuration&gt;
+        &lt;/execution&gt;
+    &lt;/executions&gt;
+&lt;/plugin&gt;
+
+&lt;!-- Finally setup your assembly. Below you can find the contents of src/main/assembly/stub.xml --&gt;
+&lt;assembly
+    xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3"
+    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3 https://maven.apache.org/xsd/assembly-1.1.3.xsd"&gt;
+    &lt;id&gt;stubs&lt;/id&gt;
+    &lt;formats&gt;
+        &lt;format&gt;jar&lt;/format&gt;
+    &lt;/formats&gt;
+    &lt;includeBaseDirectory&gt;false&lt;/includeBaseDirectory&gt;
+    &lt;fileSets&gt;
+        &lt;fileSet&gt;
+            &lt;directory&gt;src/main/java&lt;/directory&gt;
+            &lt;outputDirectory&gt;/&lt;/outputDirectory&gt;
+            &lt;includes&gt;
+                &lt;include&gt;**com/example/model/*.*&lt;/include&gt;
+            &lt;/includes&gt;
+        &lt;/fileSet&gt;
+        &lt;fileSet&gt;
+            &lt;directory&gt;${project.build.directory}/classes&lt;/directory&gt;
+            &lt;outputDirectory&gt;/&lt;/outputDirectory&gt;
+            &lt;includes&gt;
+                &lt;include&gt;**com/example/model/*.*&lt;/include&gt;
+            &lt;/includes&gt;
+        &lt;/fileSet&gt;
+        &lt;fileSet&gt;
+            &lt;directory&gt;${project.build.directory}/snippets/stubs&lt;/directory&gt;
+            &lt;outputDirectory&gt;META-INF/${project.groupId}/${project.artifactId}/${project.version}/mappings&lt;/outputDirectory&gt;
+            &lt;includes&gt;
+                &lt;include&gt;**/*&lt;/include&gt;
+            &lt;/includes&gt;
+        &lt;/fileSet&gt;
+        &lt;fileSet&gt;
+            &lt;directory&gt;${basedir}/src/test/resources/contracts&lt;/directory&gt;
+            &lt;outputDirectory&gt;META-INF/${project.groupId}/${project.artifactId}/${project.version}/contracts&lt;/outputDirectory&gt;
+            &lt;includes&gt;
+                &lt;include&gt;**/*.groovy&lt;/include&gt;
+            &lt;/includes&gt;
+        &lt;/fileSet&gt;
+    &lt;/fileSets&gt;
+&lt;/assembly&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">ext {
+    contractsDir = file("mappings")
+    stubsOutputDirRoot = file("${project.buildDir}/production/${project.name}-stubs/")
+}
+
+// Automatically added by plugin:
+// copyContracts - copies contracts to the output folder from which JAR will be created
+// verifierStubsJar - JAR with a provided stub suffix
+// the presented publication is also added by the plugin but you can modify it as you wish
+
+publishing {
+    publications {
+        stubs(MavenPublication) {
+            artifactId "${project.name}-stubs"
+            artifact verifierStubsJar
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-stub-runner-core"><a class="anchor" href="#features-stub-runner-core"></a><a class="link" href="#features-stub-runner-core">3.5.3. Stub Runner Core</a></h4>
+<div class="paragraph">
+<p>The stub runner core runs stubs for service collaborators. Treating stubs as contracts of
+services lets you use stub-runner as an implementation of
+<a href="https://martinfowler.com/articles/consumerDrivenContracts.html">Consumer-driven Contracts</a>.</p>
+</div>
+<div class="paragraph">
+<p>Stub Runner lets you automatically download the stubs of the provided dependencies (or
+pick those from the classpath), start WireMock servers for them, and feed them with proper
+stub definitions. For messaging, special stub routes are defined.</p>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-retrieving"><a class="anchor" href="#features-stub-runner-retrieving"></a><a class="link" href="#features-stub-runner-retrieving">Retrieving stubs</a></h5>
+<div class="paragraph">
+<p>You can pick from the following options of acquiring stubs:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Aether-based solution that downloads JARs with stubs from Artifactory or Nexus</p>
+</li>
+<li>
+<p>Classpath-scanning solution that searches the classpath with a pattern to retrieve stubs</p>
+</li>
+<li>
+<p>Writing your own implementation of the <code>org.springframework.cloud.contract.stubrunner.StubDownloaderBuilder</code> for full customization</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The latter example is described in the <a href="#customization-custom-stub-runner">Custom Stub Runner</a> section.</p>
+</div>
+<div class="sect5">
+<h6 id="features-stub-runner-downloading-stub"><a class="anchor" href="#features-stub-runner-downloading-stub"></a><a class="link" href="#features-stub-runner-downloading-stub">Downloading Stubs</a></h6>
+<div class="paragraph">
+<p>You can control the downloading of stubs with the <code>stubsMode</code> switch. It picks value from the
+<code>StubRunnerProperties.StubsMode</code> enumeration. You can use the following options:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>StubRunnerProperties.StubsMode.CLASSPATH</code> (default value): Picks stubs from the classpath</p>
+</li>
+<li>
+<p><code>StubRunnerProperties.StubsMode.LOCAL</code>: Picks stubs from a local storage (for example, <code>.m2</code>)</p>
+</li>
+<li>
+<p><code>StubRunnerProperties.StubsMode.REMOTE</code>: Picks stubs from a remote location</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The following example picks stubs from a local location:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(repositoryRoot="https://foo.bar", ids = "com.example:beer-api-producer:+:stubs:8095", stubsMode = StubRunnerProperties.StubsMode.LOCAL)</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-stub-runner-classpath-scanning"><a class="anchor" href="#features-stub-runner-classpath-scanning"></a><a class="link" href="#features-stub-runner-classpath-scanning">Classpath scanning</a></h6>
+<div class="paragraph">
+<p>If you set the <code>stubsMode</code> property to <code>StubRunnerProperties.StubsMode.CLASSPATH</code>
+(or set nothing since <code>CLASSPATH</code> is the default value), the classpath is scanned.
+Consider the following example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(ids = {
+    "com.example:beer-api-producer:+:stubs:8095",
+    "com.example.foo:bar:1.0.0:superstubs:8096"
+})</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You can add the dependencies to your classpath, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
+    &lt;groupId&gt;com.example&lt;/groupId&gt;
+    &lt;artifactId&gt;beer-api-producer-restdocs&lt;/artifactId&gt;
+    &lt;classifier&gt;stubs&lt;/classifier&gt;
+    &lt;version&gt;0.0.1-SNAPSHOT&lt;/version&gt;
+    &lt;scope&gt;test&lt;/scope&gt;
+    &lt;exclusions&gt;
+        &lt;exclusion&gt;
+            &lt;groupId&gt;*&lt;/groupId&gt;
+            &lt;artifactId&gt;*&lt;/artifactId&gt;
+        &lt;/exclusion&gt;
+    &lt;/exclusions&gt;
+&lt;/dependency&gt;
+&lt;dependency&gt;
+    &lt;groupId&gt;com.example.thing1&lt;/groupId&gt;
+    &lt;artifactId&gt;thing2&lt;/artifactId&gt;
+    &lt;classifier&gt;superstubs&lt;/classifier&gt;
+    &lt;version&gt;1.0.0&lt;/version&gt;
+    &lt;scope&gt;test&lt;/scope&gt;
+    &lt;exclusions&gt;
+        &lt;exclusion&gt;
+            &lt;groupId&gt;*&lt;/groupId&gt;
+            &lt;artifactId&gt;*&lt;/artifactId&gt;
+        &lt;/exclusion&gt;
+    &lt;/exclusions&gt;
+&lt;/dependency&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">testCompile("com.example:beer-api-producer-restdocs:0.0.1-SNAPSHOT:stubs") {
+    transitive = false
+}
+testCompile("com.example.thing1:thing2:1.0.0:superstubs") {
+    transitive = false
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Then the specified locations on your classpath get scanned. For <code>com.example:beer-api-producer-restdocs</code>,
+the following locations are scanned:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>/META-INF/com.example/beer-api-producer-restdocs/<strong>*/</strong>.*</p>
+</li>
+<li>
+<p>/contracts/com.example/beer-api-producer-restdocs/<strong>*/</strong>.*</p>
+</li>
+<li>
+<p>/mappings/com.example/beer-api-producer-restdocs/<strong>*/</strong>.*</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>For <code>com.example.thing1:thing2</code>, the following locations are scanned:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>/META-INF/com.example.thing1/thing2/<strong>*/</strong>.*</p>
+</li>
+<li>
+<p>/contracts/com.example.thing1/thing2/<strong>*/</strong>.*</p>
+</li>
+<li>
+<p>/mappings/com.example.thing1/thing2/<strong>*/</strong>.*</p>
+</li>
+</ul>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+You have to explicitly provide the group and artifact IDs when you package the
+producer stubs.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>To achieve proper stub packaging, the producer would set up the contracts as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── src
+    └── test
+        └── resources
+            └── contracts
+                └── com.example
+                    └── beer-api-producer-restdocs
+                        └── nested
+                            └── contract3.groovy</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>By using the <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/blob/2.2.x/producer_with_restdocs/pom.xml">Maven <code>assembly</code> plugin</a> or
+<a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/blob/2.2.x/producer_with_restdocs/build.gradle">Gradle Jar</a> task, you have to create the following
+structure in your stubs jar:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── META-INF
+    └── com.example
+        └── beer-api-producer-restdocs
+            └── 2.0.0
+                ├── contracts
+                │   └── nested
+                │       └── contract2.groovy
+                └── mappings
+                    └── mapping.json</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>By maintaining this structure, the classpath gets scanned and you can profit from the messaging or
+HTTP stubs without the need to download artifacts.</p>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-stub-runner-configuring-http-server-stubs"><a class="anchor" href="#features-stub-runner-configuring-http-server-stubs"></a><a class="link" href="#features-stub-runner-configuring-http-server-stubs">Configuring HTTP Server Stubs</a></h6>
+<div class="paragraph">
+<p>Stub Runner has a notion of a <code>HttpServerStub</code> that abstracts the underlying
+concrete implementation of the HTTP server (for example, WireMock is one of the implementations).
+Sometimes, you need to perform some additional tuning (which is concrete for the given implementation) of the stub servers.
+To do that, Stub Runner gives you
+the <code>httpServerStubConfigurer</code> property that is available in the annotation and the
+JUnit rule and is accessible through system properties, where you can provide
+your implementation of the <code>org.springframework.cloud.contract.stubrunner.HttpServerStubConfigurer</code>
+interface. The implementations can alter
+the configuration files for the given HTTP server stub.</p>
+</div>
+<div class="paragraph">
+<p>Spring Cloud Contract Stub Runner comes with an implementation that you
+can extend for WireMock:
+<code>org.springframework.cloud.contract.stubrunner.provider.wiremock.WireMockHttpServerStubConfigurer</code>.
+In the <code>configure</code> method,
+you can provide your own custom configuration for the given stub. The use
+case might be starting WireMock for the given artifact ID, on an HTTPS port. The following
+example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="title">Example 1. WireMockHttpServerStubConfigurer implementation</div>
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@CompileStatic
+static class HttpsForFraudDetection extends WireMockHttpServerStubConfigurer {
+
+    private static final Log log = LogFactory.getLog(HttpsForFraudDetection)
+
+    @Override
+    WireMockConfiguration configure(WireMockConfiguration httpStubConfiguration, HttpServerStubConfiguration httpServerStubConfiguration) {
+        if (httpServerStubConfiguration.stubConfiguration.artifactId == "fraudDetectionServer") {
+            int httpsPort = SocketUtils.findAvailableTcpPort()
+            log.info("Will set HTTPs port [" + httpsPort + "] for fraud detection server")
+            return httpStubConfiguration
+                    .httpsPort(httpsPort)
+        }
+        return httpStubConfiguration
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You can then reuse it with the <code>@AutoConfigureStubRunner</code> annotation, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@AutoConfigureStubRunner(mappingsOutputFolder = "target/outputmappings/",
+        httpServerStubConfigurer = HttpsForFraudDetection)</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Whenever an HTTPS port is found, it takes precedence over the HTTP port.</p>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-running-stubs"><a class="anchor" href="#features-stub-runner-running-stubs"></a><a class="link" href="#features-stub-runner-running-stubs">Running stubs</a></h5>
+<div class="paragraph">
+<p>This section describes how to run stubs. It contains the following topics:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="#features-stub-runner-http-stubs">HTTP Stubs</a></p>
+</li>
+<li>
+<p><a href="#features-stub-runner-viewing">Viewing Registered Mappings</a></p>
+</li>
+<li>
+<p><a href="#features-stub-runner-messaging">Messaging Stubs</a></p>
+</li>
+</ul>
+</div>
+<div class="sect5">
+<h6 id="features-stub-runner-http-stubs"><a class="anchor" href="#features-stub-runner-http-stubs"></a><a class="link" href="#features-stub-runner-http-stubs">HTTP Stubs</a></h6>
+<div class="paragraph">
+<p>Stubs are defined in JSON documents, whose syntax is defined in <a href="http://wiremock.org/stubbing.html">WireMock documentation</a></p>
+</div>
+<div class="paragraph">
+<p>The following example defines a stub in JSON:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-javascript hljs" data-lang="javascript">{
+    "request": {
+        "method": "GET",
+        "url": "/ping"
+    },
+    "response": {
+        "status": 200,
+        "body": "pong",
+        "headers": {
+            "Content-Type": "text/plain"
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-stub-runner-viewing"><a class="anchor" href="#features-stub-runner-viewing"></a><a class="link" href="#features-stub-runner-viewing">Viewing Registered Mappings</a></h6>
+<div class="paragraph">
+<p>Every stubbed collaborator exposes a list of defined mappings under the <code>__/admin/</code> endpoint.</p>
+</div>
+<div class="paragraph">
+<p>You can also use the <code>mappingsOutputFolder</code> property to dump the mappings to files.
+For the annotation-based approach, it would resembling the following example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(ids="a.b.c:loanIssuance,a.b.c:fraudDetectionServer",
+mappingsOutputFolder = "target/outputmappings/")</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>For the JUnit approach, it resembles the following example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ClassRule @Shared StubRunnerRule rule = new StubRunnerRule()
+            .repoRoot("https://some_url")
+            .downloadStub("a.b.c", "loanIssuance")
+            .downloadStub("a.b.c:fraudDetectionServer")
+            .withMappingsOutputFolder("target/outputmappings")</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Then, if you check out the <code>target/outputmappings</code> folder, you would see the following structure;</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">.
+├── fraudDetectionServer_13705
+└── loanIssuance_12255</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>That means that there were two stubs registered. <code>fraudDetectionServer</code> was registered at port <code>13705</code>
+and <code>loanIssuance</code> at port <code>12255</code>. If we take a look at one of the files, we would see (for WireMock)
+the mappings available for the given server:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">[{
+  "id" : "f9152eb9-bf77-4c38-8289-90be7d10d0d7",
+  "request" : {
+    "url" : "/name",
+    "method" : "GET"
+  },
+  "response" : {
+    "status" : 200,
+    "body" : "fraudDetectionServer"
+  },
+  "uuid" : "f9152eb9-bf77-4c38-8289-90be7d10d0d7"
+},
+...
+]</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-stub-runner-messaging"><a class="anchor" href="#features-stub-runner-messaging"></a><a class="link" href="#features-stub-runner-messaging">Messaging Stubs</a></h6>
+<div class="paragraph">
+<p>Depending on the provided Stub Runner dependency and the DSL, the messaging routes are automatically set up.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-stub-runner-junit"><a class="anchor" href="#features-stub-runner-junit"></a><a class="link" href="#features-stub-runner-junit">3.5.4. Stub Runner JUnit Rule and Stub Runner JUnit5 Extension</a></h4>
+<div class="paragraph">
+<p>Stub Runner comes with a JUnit rule that lets you can download and run stubs for a given
+group and artifact ID, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ClassRule
+public static StubRunnerRule rule = new StubRunnerRule().repoRoot(repoRoot())
+        .stubsMode(StubRunnerProperties.StubsMode.REMOTE)
+        .downloadStub("org.springframework.cloud.contract.verifier.stubs",
+                "loanIssuance")
+        .downloadStub(
+                "org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer");
+
+@BeforeClass
+@AfterClass
+public static void setupProps() {
+    System.clearProperty("stubrunner.repository.root");
+    System.clearProperty("stubrunner.classifier");
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>A <code>StubRunnerExtension</code> is also available for JUnit 5. <code>StubRunnerRule</code> and
+<code>StubRunnerExtension</code> work in a very similar fashion. After the rule or extension is
+executed, Stub Runner connects to your Maven repository and, for the given list of
+dependencies, tries to:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Download them</p>
+</li>
+<li>
+<p>Cache them locally</p>
+</li>
+<li>
+<p>Unzip them to a temporary folder</p>
+</li>
+<li>
+<p>Start a WireMock server for each Maven dependency on a random port from the provided
+range of ports or the provided port</p>
+</li>
+<li>
+<p>Feed the WireMock server with all JSON files that are valid WireMock definitions</p>
+</li>
+<li>
+<p>Send messages (remember to pass an implementation of <code>MessageVerifier</code> interface)</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Stub Runner uses the <a href="https://wiki.eclipse.org/Aether">Eclipse Aether</a> mechanism to download the Maven dependencies.
+Check their <a href="https://wiki.eclipse.org/Aether">docs</a> for more information.</p>
+</div>
+<div class="paragraph">
+<p>Since the <code>StubRunnerRule</code> and <code>StubRunnerExtension</code> implement the <code>StubFinder</code> they let
+you find the started stubs, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package org.springframework.cloud.contract.stubrunner;
+
+import java.net.URL;
+import java.util.Collection;
+import java.util.Map;
+
+import org.springframework.cloud.contract.spec.Contract;
+
+/**
+ * Contract for finding registered stubs.
+ *
+ * @author Marcin Grzejszczak
+ */
+public interface StubFinder extends StubTrigger {
+
+    /**
+     * For the given groupId and artifactId tries to find the matching URL of the running
+     * stub.
+     * @param groupId - might be null. In that case a search only via artifactId takes
+     * place
+     * @param artifactId - artifact id of the stub
+     * @return URL of a running stub or throws exception if not found
+     * @throws StubNotFoundException in case of not finding a stub
+     */
+    URL findStubUrl(String groupId, String artifactId) throws StubNotFoundException;
+
+    /**
+     * For the given Ivy notation {@code [groupId]:artifactId:[version]:[classifier]}
+     * tries to find the matching URL of the running stub. You can also pass only
+     * {@code artifactId}.
+     * @param ivyNotation - Ivy representation of the Maven artifact
+     * @return URL of a running stub or throws exception if not found
+     * @throws StubNotFoundException in case of not finding a stub
+     */
+    URL findStubUrl(String ivyNotation) throws StubNotFoundException;
+
+    /**
+     * @return all running stubs
+     */
+    RunningStubs findAllRunningStubs();
+
+    /**
+     * @return the list of Contracts
+     */
+    Map&lt;StubConfiguration, Collection&lt;Contract&gt;&gt; getContracts();
+
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following examples provide more detail about using Stub Runner:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">spock</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@ClassRule
+@Shared
+StubRunnerRule rule = new StubRunnerRule()
+        .stubsMode(StubRunnerProperties.StubsMode.REMOTE)
+        .repoRoot(StubRunnerRuleSpec.getResource("/m2repo/repository").toURI().toString())
+        .downloadStub("org.springframework.cloud.contract.verifier.stubs", "loanIssuance")
+        .downloadStub("org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer")
+        .withMappingsOutputFolder("target/outputmappingsforrule")
+
+
+def 'should start WireMock servers'() {
+    expect: 'WireMocks are running'
+        rule.findStubUrl('org.springframework.cloud.contract.verifier.stubs', 'loanIssuance') != null
+        rule.findStubUrl('loanIssuance') != null
+        rule.findStubUrl('loanIssuance') == rule.findStubUrl('org.springframework.cloud.contract.verifier.stubs', 'loanIssuance')
+        rule.findStubUrl('org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer') != null
+    and:
+        rule.findAllRunningStubs().isPresent('loanIssuance')
+        rule.findAllRunningStubs().isPresent('org.springframework.cloud.contract.verifier.stubs', 'fraudDetectionServer')
+        rule.findAllRunningStubs().isPresent('org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer')
+    and: 'Stubs were registered'
+        "${rule.findStubUrl('loanIssuance').toString()}/name".toURL().text == 'loanIssuance'
+        "${rule.findStubUrl('fraudDetectionServer').toString()}/name".toURL().text == 'fraudDetectionServer'
+}
+
+def 'should output mappings to output folder'() {
+    when:
+        def url = rule.findStubUrl('fraudDetectionServer')
+    then:
+        new File("target/outputmappingsforrule", "fraudDetectionServer_${url.port}").exists()
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">junit 4</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Test
+public void should_start_wiremock_servers() throws Exception {
+    // expect: 'WireMocks are running'
+    then(rule.findStubUrl("org.springframework.cloud.contract.verifier.stubs",
+            "loanIssuance")).isNotNull();
+    then(rule.findStubUrl("loanIssuance")).isNotNull();
+    then(rule.findStubUrl("loanIssuance")).isEqualTo(rule.findStubUrl(
+            "org.springframework.cloud.contract.verifier.stubs", "loanIssuance"));
+    then(rule.findStubUrl(
+            "org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer"))
+                    .isNotNull();
+    // and:
+    then(rule.findAllRunningStubs().isPresent("loanIssuance")).isTrue();
+    then(rule.findAllRunningStubs().isPresent(
+            "org.springframework.cloud.contract.verifier.stubs",
+            "fraudDetectionServer")).isTrue();
+    then(rule.findAllRunningStubs().isPresent(
+            "org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer"))
+                    .isTrue();
+    // and: 'Stubs were registered'
+    then(httpGet(rule.findStubUrl("loanIssuance").toString() + "/name"))
+            .isEqualTo("loanIssuance");
+    then(httpGet(rule.findStubUrl("fraudDetectionServer").toString() + "/name"))
+            .isEqualTo("fraudDetectionServer");
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">junit 5</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">// Visible for Junit
+@RegisterExtension
+static StubRunnerExtension stubRunnerExtension = new StubRunnerExtension()
+        .repoRoot(repoRoot()).stubsMode(StubRunnerProperties.StubsMode.REMOTE)
+        .downloadStub("org.springframework.cloud.contract.verifier.stubs",
+                "loanIssuance")
+        .downloadStub(
+                "org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer")
+        .withMappingsOutputFolder("target/outputmappingsforrule");
+
+@BeforeAll
+@AfterAll
+static void setupProps() {
+    System.clearProperty("stubrunner.repository.root");
+    System.clearProperty("stubrunner.classifier");
+}
+
+private static String repoRoot() {
+    try {
+        return StubRunnerRuleJUnitTest.class.getResource("/m2repo/repository/")
+                .toURI().toString();
+    }
+    catch (Exception e) {
+        return "";
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>See the <a href="#features-stub-runner-common-properties-junit-spring">Common Properties for JUnit and Spring</a> for more information on
+how to apply global configuration of Stub Runner.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+To use the JUnit rule or JUnit 5 extension together with messaging, you have to provide an implementation of the
+<code>MessageVerifier</code> interface to the rule builder (for example, <code>rule.messageVerifier(new MyMessageVerifier())</code>).
+If you do not do this, then, whenever you try to send a message, an exception is thrown.
+</td>
+</tr>
+</table>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-rule-maven-settings"><a class="anchor" href="#features-stub-runner-rule-maven-settings"></a><a class="link" href="#features-stub-runner-rule-maven-settings">Maven Settings</a></h5>
+<div class="paragraph">
+<p>The stub downloader honors Maven settings for a different local repository folder.
+Authentication details for repositories and profiles are currently not taken into account,
+so you need to specify it by using the properties mentioned above.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-rule-fixed-ports"><a class="anchor" href="#features-stub-runner-rule-fixed-ports"></a><a class="link" href="#features-stub-runner-rule-fixed-ports">Providing Fixed Ports</a></h5>
+<div class="paragraph">
+<p>You can also run your stubs on fixed ports. You can do it in two different ways.
+One is to pass it in the properties, and the other is to use the fluent API of
+JUnit rule.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-rule-fluent-api"><a class="anchor" href="#features-stub-runner-rule-fluent-api"></a><a class="link" href="#features-stub-runner-rule-fluent-api">Fluent API</a></h5>
+<div class="paragraph">
+<p>When using the <code>StubRunnerRule</code> or <code>StubRunnerExtension</code>, you can add a stub to download
+and then pass the port for the last downloaded stub. The following example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ClassRule
+public static StubRunnerRule rule = new StubRunnerRule().repoRoot(repoRoot())
+        .stubsMode(StubRunnerProperties.StubsMode.REMOTE)
+        .downloadStub("org.springframework.cloud.contract.verifier.stubs",
+                "loanIssuance")
+        .withPort(12345).downloadStub(
+                "org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer:12346");
+
+@BeforeClass
+@AfterClass
+public static void setupProps() {
+    System.clearProperty("stubrunner.repository.root");
+    System.clearProperty("stubrunner.classifier");
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>For the preceding example, the following test is valid:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">then(rule.findStubUrl("loanIssuance"))
+        .isEqualTo(URI.create("http://localhost:12345").toURL());
+then(rule.findStubUrl("fraudDetectionServer"))
+        .isEqualTo(URI.create("http://localhost:12346").toURL());</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-rule-spring"><a class="anchor" href="#features-stub-runner-rule-spring"></a><a class="link" href="#features-stub-runner-rule-spring">Stub Runner with Spring</a></h5>
+<div class="paragraph">
+<p>Stub Runner with Spring sets up Spring configuration of the Stub Runner project.</p>
+</div>
+<div class="paragraph">
+<p>By providing a list of stubs inside your configuration file, Stub Runner automatically downloads
+and registers in WireMock the selected stubs.</p>
+</div>
+<div class="paragraph">
+<p>If you want to find the URL of your stubbed dependency, you can autowire the <code>StubFinder</code> interface and use
+its methods, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@ContextConfiguration(classes = Config, loader = SpringBootContextLoader)
+@SpringBootTest(properties = [" stubrunner.cloud.enabled=false",
+        'foo=${stubrunner.runningstubs.fraudDetectionServer.port}',
+        'fooWithGroup=${stubrunner.runningstubs.org.springframework.cloud.contract.verifier.stubs.fraudDetectionServer.port}'])
+@AutoConfigureStubRunner(mappingsOutputFolder = "target/outputmappings/",
+        httpServerStubConfigurer = HttpsForFraudDetection)
+@ActiveProfiles("test")
+class StubRunnerConfigurationSpec extends Specification {
+
+    @Autowired
+    StubFinder stubFinder
+    @Autowired
+    Environment environment
+    @StubRunnerPort("fraudDetectionServer")
+    int fraudDetectionServerPort
+    @StubRunnerPort("org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer")
+    int fraudDetectionServerPortWithGroupId
+    @Value('${foo}')
+    Integer foo
+
+    @BeforeClass
+    @AfterClass
+    void setupProps() {
+        System.clearProperty("stubrunner.repository.root")
+        System.clearProperty("stubrunner.classifier")
+        WireMockHttpServerStubAccessor.clear()
+    }
+
+    def 'should mark all ports as random'() {
+        expect:
+            WireMockHttpServerStubAccessor.everyPortRandom()
+    }
+
+    def 'should start WireMock servers'() {
+        expect: 'WireMocks are running'
+            stubFinder.findStubUrl('org.springframework.cloud.contract.verifier.stubs', 'loanIssuance') != null
+            stubFinder.findStubUrl('loanIssuance') != null
+            stubFinder.findStubUrl('loanIssuance') == stubFinder.findStubUrl('org.springframework.cloud.contract.verifier.stubs', 'loanIssuance')
+            stubFinder.findStubUrl('loanIssuance') == stubFinder.findStubUrl('org.springframework.cloud.contract.verifier.stubs:loanIssuance')
+            stubFinder.findStubUrl('org.springframework.cloud.contract.verifier.stubs:loanIssuance:0.0.1-SNAPSHOT') == stubFinder.findStubUrl('org.springframework.cloud.contract.verifier.stubs:loanIssuance:0.0.1-SNAPSHOT:stubs')
+            stubFinder.findStubUrl('org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer') != null
+        and:
+            stubFinder.findAllRunningStubs().isPresent('loanIssuance')
+            stubFinder.findAllRunningStubs().isPresent('org.springframework.cloud.contract.verifier.stubs', 'fraudDetectionServer')
+            stubFinder.findAllRunningStubs().isPresent('org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer')
+        and: 'Stubs were registered'
+            "${stubFinder.findStubUrl('loanIssuance').toString()}/name".toURL().text == 'loanIssuance'
+            "${stubFinder.findStubUrl('fraudDetectionServer').toString()}/name".toURL().text == 'fraudDetectionServer'
+        and: 'Fraud Detection is an HTTPS endpoint'
+            stubFinder.findStubUrl('fraudDetectionServer').toString().startsWith("https")
+    }
+
+    def 'should throw an exception when stub is not found'() {
+        when:
+            stubFinder.findStubUrl('nonExistingService')
+        then:
+            thrown(StubNotFoundException)
+        when:
+            stubFinder.findStubUrl('nonExistingGroupId', 'nonExistingArtifactId')
+        then:
+            thrown(StubNotFoundException)
+    }
+
+    def 'should register started servers as environment variables'() {
+        expect:
+            environment.getProperty("stubrunner.runningstubs.loanIssuance.port") != null
+            stubFinder.findAllRunningStubs().getPort("loanIssuance") == (environment.getProperty("stubrunner.runningstubs.loanIssuance.port") as Integer)
+        and:
+            environment.getProperty("stubrunner.runningstubs.fraudDetectionServer.port") != null
+            stubFinder.findAllRunningStubs().getPort("fraudDetectionServer") == (environment.getProperty("stubrunner.runningstubs.fraudDetectionServer.port") as Integer)
+        and:
+            environment.getProperty("stubrunner.runningstubs.fraudDetectionServer.port") != null
+            stubFinder.findAllRunningStubs().getPort("fraudDetectionServer") == (environment.getProperty("stubrunner.runningstubs.org.springframework.cloud.contract.verifier.stubs.fraudDetectionServer.port") as Integer)
+    }
+
+    def 'should be able to interpolate a running stub in the passed test property'() {
+        given:
+            int fraudPort = stubFinder.findAllRunningStubs().getPort("fraudDetectionServer")
+        expect:
+            fraudPort &gt; 0
+            environment.getProperty("foo", Integer) == fraudPort
+            environment.getProperty("fooWithGroup", Integer) == fraudPort
+            foo == fraudPort
+    }
+
+    @Issue("#573")
+    def 'should be able to retrieve the port of a running stub via an annotation'() {
+        given:
+            int fraudPort = stubFinder.findAllRunningStubs().getPort("fraudDetectionServer")
+        expect:
+            fraudPort &gt; 0
+            fraudDetectionServerPort == fraudPort
+            fraudDetectionServerPortWithGroupId == fraudPort
+    }
+
+    def 'should dump all mappings to a file'() {
+        when:
+            def url = stubFinder.findStubUrl("fraudDetectionServer")
+        then:
+            new File("target/outputmappings/", "fraudDetectionServer_${url.port}").exists()
+    }
+
+    @Configuration
+    @EnableAutoConfiguration
+    static class Config {}
+
+    @CompileStatic
+    static class HttpsForFraudDetection extends WireMockHttpServerStubConfigurer {
+
+        private static final Log log = LogFactory.getLog(HttpsForFraudDetection)
+
+        @Override
+        WireMockConfiguration configure(WireMockConfiguration httpStubConfiguration, HttpServerStubConfiguration httpServerStubConfiguration) {
+            if (httpServerStubConfiguration.stubConfiguration.artifactId == "fraudDetectionServer") {
+                int httpsPort = SocketUtils.findAvailableTcpPort()
+                log.info("Will set HTTPs port [" + httpsPort + "] for fraud detection server")
+                return httpStubConfiguration
+                        .httpsPort(httpsPort)
+            }
+            return httpStubConfiguration
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Doing so depends on the following configuration file:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">stubrunner:
+  repositoryRoot: classpath:m2repo/repository/
+  ids:
+    - org.springframework.cloud.contract.verifier.stubs:loanIssuance
+    - org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer
+    - org.springframework.cloud.contract.verifier.stubs:bootService
+  stubs-mode: remote</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Instead of using the properties, you can also use the properties inside the <code>@AutoConfigureStubRunner</code>.
+The following example achieves the same result by setting values on the annotation:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@AutoConfigureStubRunner(
+        ids = ["org.springframework.cloud.contract.verifier.stubs:loanIssuance",
+                "org.springframework.cloud.contract.verifier.stubs:fraudDetectionServer",
+                "org.springframework.cloud.contract.verifier.stubs:bootService"],
+        stubsMode = StubRunnerProperties.StubsMode.REMOTE,
+        repositoryRoot = "classpath:m2repo/repository/")</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Stub Runner Spring registers environment variables in the following manner
+for every registered WireMock server. The following example shows Stub Runner IDs for
+<code>com.example:thing1</code> and <code>com.example:thing2</code>:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>stubrunner.runningstubs.thing1.port</code></p>
+</li>
+<li>
+<p><code>stubrunner.runningstubs.com.example.thing1.port</code></p>
+</li>
+<li>
+<p><code>stubrunner.runningstubs.thing2.port</code></p>
+</li>
+<li>
+<p><code>stubrunner.runningstubs.com.example.thing2.port</code></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>You can reference these values in your code.</p>
+</div>
+<div class="paragraph">
+<p>You can also use the <code>@StubRunnerPort</code> annotation to inject the port of a running stub.
+The value of the annotation can be the <code>groupid:artifactid</code> or just the <code>artifactid</code>.
+The following example works shows Stub Runner IDs for
+<code>com.example:thing1</code> and <code>com.example:thing2</code>.</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@StubRunnerPort("thing1")
+int thing1Port;
+@StubRunnerPort("com.example:thing2")
+int thing2Port;</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-stub-runner-cloud"><a class="anchor" href="#features-stub-runner-cloud"></a><a class="link" href="#features-stub-runner-cloud">3.5.5. Stub Runner Spring Cloud</a></h4>
+<div class="paragraph">
+<p>Stub Runner can integrate with Spring Cloud.</p>
+</div>
+<div class="paragraph">
+<p>For real life examples, see:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x/producer">The producer app sample</a></p>
+</li>
+<li>
+<p><a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x/consumer_with_discovery">The consumer app sample</a></p>
+</li>
+</ul>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-cloud-stubbing-discovery"><a class="anchor" href="#features-stub-runner-cloud-stubbing-discovery"></a><a class="link" href="#features-stub-runner-cloud-stubbing-discovery">Stubbing Service Discovery</a></h5>
+<div class="paragraph">
+<p>The most important feature of <code>Stub Runner Spring Cloud</code> is the fact that it stubs:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>DiscoveryClient</code></p>
+</li>
+<li>
+<p><code>Ribbon</code> <code>ServerList</code></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>That means that, regardless of whether you use Zookeeper, Consul, Eureka, or anything
+else, you do not need that in your tests. We are starting WireMock instances of your
+dependencies and we are telling your application, whenever you use <code>Feign</code>, to load a
+balanced <code>RestTemplate</code> or <code>DiscoveryClient</code> directly, to call those stubbed servers
+instead of calling the real Service Discovery tool.</p>
+</div>
+<div class="paragraph">
+<p>For example, the following test passes:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">def 'should make service discovery work'() {
+    expect: 'WireMocks are running'
+        "${stubFinder.findStubUrl('loanIssuance').toString()}/name".toURL().text == 'loanIssuance'
+        "${stubFinder.findStubUrl('fraudDetectionServer').toString()}/name".toURL().text == 'fraudDetectionServer'
+    and: 'Stubs can be reached via load service discovery'
+        restTemplate.getForObject('http://loanIssuance/name', String) == 'loanIssuance'
+        restTemplate.getForObject('http://someNameThatShouldMapFraudDetectionServer/name', String) == 'fraudDetectionServer'
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Note that the preceding example requires the following configuration file:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">stubrunner:
+  idsToServiceIds:
+    ivyNotation: someValueInsideYourCode
+    fraudDetectionServer: someNameThatShouldMapFraudDetectionServer</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-stub-runner-cloud-stubbing-profiles"><a class="anchor" href="#features-stub-runner-cloud-stubbing-profiles"></a><a class="link" href="#features-stub-runner-cloud-stubbing-profiles">Test Profiles and Service Discovery</a></h6>
+<div class="paragraph">
+<p>In your integration tests, you typically do not want to call either a discovery service (such as Eureka)
+or Config Server. That is why you create an additional test configuration in which you want to disable
+these features.</p>
+</div>
+<div class="paragraph">
+<p>Due to certain limitations of <a href="https://github.com/spring-cloud/spring-cloud-commons/issues/156"><code>spring-cloud-commons</code></a>,
+to achieve this, you have to disable these properties
+in a static block such as the following example (for Eureka):</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">    //Hack to work around https://github.com/spring-cloud/spring-cloud-commons/issues/156
+    static {
+        System.setProperty("eureka.client.enabled", "false");
+        System.setProperty("spring.cloud.config.failFast", "false");
+    }</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-additional-config"><a class="anchor" href="#features-stub-runner-additional-config"></a><a class="link" href="#features-stub-runner-additional-config">Additional Configuration</a></h5>
+<div class="paragraph">
+<p>You can match the <code>artifactId</code> of the stub with the name of your application by using the <code>stubrunner.idsToServiceIds:</code> map.
+You can disable Stub Runner Ribbon support by setting <code>stubrunner.cloud.ribbon.enabled</code> to <code>false</code>
+You can disable Stub Runner support by setting <code>stubrunner.cloud.enabled</code> to <code>false</code></p>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+By default, all service discovery is stubbed. This means that, regardless of whether you have
+an existing <code>DiscoveryClient</code>, its results are ignored. However, if you want to reuse it, you can set
+ <code>stubrunner.cloud.delegate.enabled</code> to <code>true</code>, and then your existing <code>DiscoveryClient</code> results are
+ merged with the stubbed ones.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The default Maven configuration used by Stub Runner can be tweaked either
+by setting the following system properties or by setting the corresponding environment variables:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>maven.repo.local</code>: Path to the custom maven local repository location</p>
+</li>
+<li>
+<p><code>org.apache.maven.user-settings</code>: Path to custom maven user settings location</p>
+</li>
+<li>
+<p><code>org.apache.maven.global-settings</code>: Path to maven global settings location</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-stub-runner-boot"><a class="anchor" href="#features-stub-runner-boot"></a><a class="link" href="#features-stub-runner-boot">3.5.6. Using the Stub Runner Boot Application</a></h4>
+<div class="paragraph">
+<p>Spring Cloud Contract Stub Runner Boot is a Spring Boot application that exposes REST endpoints to
+trigger the messaging labels and to access WireMock servers.</p>
+</div>
+<div class="paragraph">
+<p>One of the use cases is to run some smoke (end-to-end) tests on a deployed application.
+You can check out the <a href="https://github.com/spring-cloud/spring-cloud-pipelines">Spring Cloud Pipelines</a>
+project for more information.</p>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-boot-server"><a class="anchor" href="#features-stub-runner-boot-server"></a><a class="link" href="#features-stub-runner-boot-server">Stub Runner Server</a></h5>
+<div class="paragraph">
+<p>To use the Stub Runner Server, add the following dependency:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">compile "org.springframework.cloud:spring-cloud-starter-stub-runner"</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Then annotate a class with <code>@EnableStubRunnerServer</code>, build a fat jar, and it is ready to work.</p>
+</div>
+<div class="paragraph">
+<p>For the properties, see the <a href="#features-stub-runner-rule-spring">Stub Runner Spring</a> section.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-boot-how-fat-jar"><a class="anchor" href="#features-stub-runner-boot-how-fat-jar"></a><a class="link" href="#features-stub-runner-boot-how-fat-jar">Stub Runner Server Fat Jar</a></h5>
+<div class="paragraph">
+<p>You can download a standalone JAR from Maven (for example, for version 2.0.1.RELEASE)
+by running the following commands:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ wget -O stub-runner.jar 'https://search.maven.org/remotecontent?filepath=org/springframework/cloud/spring-cloud-contract-stub-runner-boot/2.0.1.RELEASE/spring-cloud-contract-stub-runner-boot-2.0.1.RELEASE.jar'
+$ java -jar stub-runner.jar --stubrunner.ids=... --stubrunner.repositoryRoot=...</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-boot-how-cli"><a class="anchor" href="#features-stub-runner-boot-how-cli"></a><a class="link" href="#features-stub-runner-boot-how-cli">Spring Cloud CLI</a></h5>
+<div class="paragraph">
+<p>Starting from the <code>1.4.0.RELEASE</code> version of the <a href="https://cloud.spring.io/spring-cloud-cli">Spring Cloud CLI</a>
+project, you can start Stub Runner Boot by running <code>spring cloud stubrunner</code>.</p>
+</div>
+<div class="paragraph">
+<p>In order to pass the configuration, you can create a <code>stubrunner.yml</code> file in the current working directory,
+in a subdirectory called <code>config</code>, or in <code>~/.spring-cloud</code>. The file could resemble the following
+example for running stubs installed locally:</p>
+</div>
+<div class="exampleblock">
+<div class="title">Example 2. stubrunner.yml</div>
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-yml hljs" data-lang="yml">stubrunner:
+  stubsMode: LOCAL
+  ids:
+    - com.example:beer-api-producer:+:9876</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Then you can call <code>spring cloud stubrunner</code> from your terminal window to start
+the Stub Runner server. It is available at port <code>8750</code>.</p>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-boot-endpoints"><a class="anchor" href="#features-stub-runner-boot-endpoints"></a><a class="link" href="#features-stub-runner-boot-endpoints">Endpoints</a></h5>
+<div class="paragraph">
+<p>Stub Runner Boot offers two endpoints:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="#features-stub-runner-boot-endpoints-http">HTTP</a></p>
+</li>
+<li>
+<p><a href="#features-stub-runner-boot-endpoints-messaging">Messaging</a></p>
+</li>
+</ul>
+</div>
+<div class="sect5">
+<h6 id="features-stub-runner-boot-endpoints-http"><a class="anchor" href="#features-stub-runner-boot-endpoints-http"></a><a class="link" href="#features-stub-runner-boot-endpoints-http">HTTP</a></h6>
+<div class="paragraph">
+<p>For HTTP, Stub Runner Boot makes the following endpoints available:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>GET <code>/stubs</code>: Returns a list of all running stubs in <code>ivy:integer</code> notation</p>
+</li>
+<li>
+<p>GET <code>/stubs/{ivy}</code>: Returns a port for the given <code>ivy</code> notation (when calling the endpoint <code>ivy</code> can also be <code>artifactId</code> only)</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect5">
+<h6 id="features-stub-runner-boot-endpoints-messaging"><a class="anchor" href="#features-stub-runner-boot-endpoints-messaging"></a><a class="link" href="#features-stub-runner-boot-endpoints-messaging">Messaging</a></h6>
+<div class="paragraph">
+<p>For Messaging, Stub Runner Boot makes the following endpoints available:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>GET <code>/triggers</code>: Returns a list of all running labels in <code>ivy : [ label1, label2 &#8230;&#8203;]</code> notation</p>
+</li>
+<li>
+<p>POST <code>/triggers/{label}</code>: Runs a trigger with <code>label</code></p>
+</li>
+<li>
+<p>POST <code>/triggers/{ivy}/{label}</code>: Runs a trigger with a <code>label</code> for the given <code>ivy</code> notation
+(when calling the endpoint, <code>ivy</code> can also be <code>artifactId</code> only)</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-boot-endpoints-example"><a class="anchor" href="#features-stub-runner-boot-endpoints-example"></a><a class="link" href="#features-stub-runner-boot-endpoints-example">Example</a></h5>
+<div class="paragraph">
+<p>The following example shows typical usage of Stub Runner Boot:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@ContextConfiguration(classes = StubRunnerBoot, loader = SpringBootContextLoader)
+@SpringBootTest(properties = "spring.cloud.zookeeper.enabled=false")
+@ActiveProfiles("test")
+class StubRunnerBootSpec extends Specification {
+
+    @Autowired
+    StubRunning stubRunning
+
+    def setup() {
+        RestAssuredMockMvc.standaloneSetup(new HttpStubsController(stubRunning),
+                new TriggerController(stubRunning))
+    }
+
+    def 'should return a list of running stub servers in "full ivy:port" notation'() {
+        when:
+            String response = RestAssuredMockMvc.get('/stubs').body.asString()
+        then:
+            def root = new JsonSlurper().parseText(response)
+            root.'org.springframework.cloud.contract.verifier.stubs:bootService:0.0.1-SNAPSHOT:stubs' instanceof Integer
+    }
+
+    def 'should return a port on which a [#stubId] stub is running'() {
+        when:
+            def response = RestAssuredMockMvc.get("/stubs/${stubId}")
+        then:
+            response.statusCode == 200
+            Integer.valueOf(response.body.asString()) &gt; 0
+        where:
+            stubId &lt;&lt; ['org.springframework.cloud.contract.verifier.stubs:bootService:+:stubs',
+                       'org.springframework.cloud.contract.verifier.stubs:bootService:0.0.1-SNAPSHOT:stubs',
+                       'org.springframework.cloud.contract.verifier.stubs:bootService:+',
+                       'org.springframework.cloud.contract.verifier.stubs:bootService',
+                       'bootService']
+    }
+
+    def 'should return 404 when missing stub was called'() {
+        when:
+            def response = RestAssuredMockMvc.get("/stubs/a:b:c:d")
+        then:
+            response.statusCode == 404
+    }
+
+    def 'should return a list of messaging labels that can be triggered when version and classifier are passed'() {
+        when:
+            String response = RestAssuredMockMvc.get('/triggers').body.asString()
+        then:
+            def root = new JsonSlurper().parseText(response)
+            root.'org.springframework.cloud.contract.verifier.stubs:bootService:0.0.1-SNAPSHOT:stubs'?.containsAll(["delete_book", "return_book_1", "return_book_2"])
+    }
+
+    def 'should trigger a messaging label'() {
+        given:
+            StubRunning stubRunning = Mock()
+            RestAssuredMockMvc.standaloneSetup(new HttpStubsController(stubRunning), new TriggerController(stubRunning))
+        when:
+            def response = RestAssuredMockMvc.post("/triggers/delete_book")
+        then:
+            response.statusCode == 200
+        and:
+            1 * stubRunning.trigger('delete_book')
+    }
+
+    def 'should trigger a messaging label for a stub with [#stubId] ivy notation'() {
+        given:
+            StubRunning stubRunning = Mock()
+            RestAssuredMockMvc.standaloneSetup(new HttpStubsController(stubRunning), new TriggerController(stubRunning))
+        when:
+            def response = RestAssuredMockMvc.post("/triggers/$stubId/delete_book")
+        then:
+            response.statusCode == 200
+        and:
+            1 * stubRunning.trigger(stubId, 'delete_book')
+        where:
+            stubId &lt;&lt; ['org.springframework.cloud.contract.verifier.stubs:bootService:stubs', 'org.springframework.cloud.contract.verifier.stubs:bootService', 'bootService']
+    }
+
+    def 'should throw exception when trigger is missing'() {
+        when:
+            RestAssuredMockMvc.post("/triggers/missing_label")
+        then:
+            Exception e = thrown(Exception)
+            e.message.contains("Exception occurred while trying to return [missing_label] label.")
+            e.message.contains("Available labels are")
+            e.message.contains("org.springframework.cloud.contract.verifier.stubs:loanIssuance:0.0.1-SNAPSHOT:stubs=[]")
+            e.message.contains("org.springframework.cloud.contract.verifier.stubs:bootService:0.0.1-SNAPSHOT:stubs=")
+    }
+
+}</code></pre>
+</div>
+</div>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-boot-service-discovery"><a class="anchor" href="#features-stub-runner-boot-service-discovery"></a><a class="link" href="#features-stub-runner-boot-service-discovery">Stub Runner Boot with Service Discovery</a></h5>
+<div class="paragraph">
+<p>One way to use Stub Runner Boot is to use it as a feed of stubs for &#8220;smoke tests&#8221;. What does that mean?
+Assume that you do not want to deploy 50 microservices to a test environment in order
+to see whether your application works. You have already executed a suite of tests during the build process,
+but you would also like to ensure that the packaging of your application works. You can
+deploy your application to an environment, start it, and run a couple of tests on it to see whether
+it works. We can call those tests &#8220;smoke tests&#8221;, because their purpose is to check only a handful
+of testing scenarios.</p>
+</div>
+<div class="paragraph">
+<p>The problem with this approach is thatm if you use microservices, you most likely also
+use a service discovery tool. Stub Runner Boot lets you solve this issue by starting the
+required stubs and registering them in a service discovery tool. Consider the following example of
+such a setup with Eureka (assume that Eureka is already running):</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@SpringBootApplication
+@EnableStubRunnerServer
+@EnableEurekaClient
+@AutoConfigureStubRunner
+public class StubRunnerBootEurekaExample {
+
+    public static void main(String[] args) {
+        SpringApplication.run(StubRunnerBootEurekaExample.class, args);
+    }
+
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>We want to start a Stub Runner Boot server (<code>@EnableStubRunnerServer</code>), enable the Eureka client (<code>@EnableEurekaClient</code>),
+and have the stub runner feature turned on (<code>@AutoConfigureStubRunner</code>).</p>
+</div>
+<div class="paragraph">
+<p>Now assume that we want to start this application so that the stubs get automatically registered.
+We can do so by running the application with <code>java -jar ${SYSTEM_PROPS} stub-runner-boot-eureka-example.jar</code>, where
+<code>${SYSTEM_PROPS}</code> contains the following list of properties:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">* -Dstubrunner.repositoryRoot=https://repo.spring.io/snapshot (1)
+* -Dstubrunner.cloud.stubbed.discovery.enabled=false (2)
+* -Dstubrunner.ids=org.springframework.cloud.contract.verifier.stubs:loanIssuance,org.
+* springframework.cloud.contract.verifier.stubs:fraudDetectionServer,org.springframework.
+* cloud.contract.verifier.stubs:bootService (3)
+* -Dstubrunner.idsToServiceIds.fraudDetectionServer=
+* someNameThatShouldMapFraudDetectionServer (4)
+*
+* (1) - we tell Stub Runner where all the stubs reside (2) - we don't want the default
+* behaviour where the discovery service is stubbed. That's why the stub registration will
+* be picked (3) - we provide a list of stubs to download (4) - we provide a list of</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>That way, your deployed application can send requests to started WireMock servers through service
+discovery. Most likely, points 1 through 3 could be set by default in <code>application.yml</code>, because they are not
+likely to change. That way, you can provide only the list of stubs to download whenever you start
+the Stub Runner Boot.</p>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-stub-runner-stubs-per-consumer"><a class="anchor" href="#features-stub-runner-stubs-per-consumer"></a><a class="link" href="#features-stub-runner-stubs-per-consumer">3.5.7. Consumer-Driven Contracts: Stubs Per Consumer</a></h4>
+<div class="paragraph">
+<p>There are cases in which two consumers of the same endpoint want to have two different responses.</p>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+This approach also lets you immediately know which consumer uses which part of your API.
+You can remove part of a response that your API produces and see which of your autogenerated tests
+fails. If none fails, you can safely delete that part of the response, because nobody uses it.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>Consider the following example of a contract defined for the producer called <code>producer</code>,
+which has two consumers (<code>foo-consumer</code> and <code>bar-consumer</code>):</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="title">Consumer <code>foo-service</code></div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">request {
+   url '/foo'
+   method GET()
+}
+response {
+    status OK()
+    body(
+       foo: "foo"
+    }
+}</code></pre>
+</div>
+</div>
+<div class="listingblock">
+<div class="title">Consumer <code>bar-service</code></div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">request {
+   url '/bar'
+   method GET()
+}
+response {
+    status OK()
+    body(
+       bar: "bar"
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You cannot produce two different responses for the same request. That is why you can properly package the
+contracts and then profit from the <code>stubsPerConsumer</code> feature.</p>
+</div>
+<div class="paragraph">
+<p>On the producer side, the consumers can have a folder that contains contracts related only to them.
+By setting the <code>stubrunner.stubs-per-consumer</code> flag to <code>true</code>, we no longer register all stubs but only those that
+correspond to the consumer application&#8217;s name. In other words, we scan the path of every stub and,
+if it contains a subfolder with name of the consumer in the path, only then is it registered.</p>
+</div>
+<div class="paragraph">
+<p>On the <code>foo</code> producer side the contracts would look like this</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">.
+└── contracts
+    ├── bar-consumer
+    │   ├── bookReturnedForBar.groovy
+    │   └── shouldCallBar.groovy
+    └── foo-consumer
+        ├── bookReturnedForFoo.groovy
+        └── shouldCallFoo.groovy</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The <code>bar-consumer</code> consumer can either set the <code>spring.application.name</code> or the <code>stubrunner.consumer-name</code> to <code>bar-consumer</code>
+Alternatively, you can set the test as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@ContextConfiguration(classes = Config, loader = SpringBootContextLoader)
+@SpringBootTest(properties = ["spring.application.name=bar-consumer"])
+@AutoConfigureStubRunner(ids = "org.springframework.cloud.contract.verifier.stubs:producerWithMultipleConsumers",
+        repositoryRoot = "classpath:m2repo/repository/",
+        stubsMode = StubRunnerProperties.StubsMode.REMOTE,
+        stubsPerConsumer = true)
+@ActiveProfiles("streamconsumer")
+class StubRunnerStubsPerConsumerSpec extends Specification {
+...
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Then only the stubs registered under a path that contains <code>bar-consumer</code> in its name (that is, those from the
+<code>src/test/resources/contracts/bar-consumer/some/contracts/&#8230;&#8203;</code> folder) are allowed to be referenced.</p>
+</div>
+<div class="paragraph">
+<p>You can also set the consumer name explicitly, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@ContextConfiguration(classes = Config, loader = SpringBootContextLoader)
+@SpringBootTest
+@AutoConfigureStubRunner(ids = "org.springframework.cloud.contract.verifier.stubs:producerWithMultipleConsumers",
+        repositoryRoot = "classpath:m2repo/repository/",
+        consumerName = "foo-consumer",
+        stubsMode = StubRunnerProperties.StubsMode.REMOTE,
+        stubsPerConsumer = true)
+@ActiveProfiles("streamconsumer")
+class StubRunnerStubsPerConsumerWithConsumerNameSpec extends Specification {
+...
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Then only the stubs registered under a path that contains the <code>foo-consumer</code> in its name (that is, those from the
+<code>src/test/resources/contracts/foo-consumer/some/contracts/&#8230;&#8203;</code> folder) are allowed to be referenced.</p>
+</div>
+<div class="paragraph">
+<p>See <a href="https://github.com/spring-cloud/spring-cloud-contract/issues/224">issue 224</a> for more
+information about the reasons behind this change.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-stub-runner-stubs-protocol"><a class="anchor" href="#features-stub-runner-stubs-protocol"></a><a class="link" href="#features-stub-runner-stubs-protocol">3.5.8. Fetching Stubs or Contract Definitions From A Location</a></h4>
+<div class="paragraph">
+<p>Instead of picking the stubs or contract definitions from
+Artifactory / Nexus or Git, one can just want to point to
+a location on drive or classpath. This can be especially useful in a multimodule project, where one module wants
+to reuse stubs or contracts from another module without
+the need to actually install those in a local maven
+repository ot commit those changes to Git.</p>
+</div>
+<div class="paragraph">
+<p>In order to achieve this it&#8217;s enough to use the <code>stubs://</code>
+protocol when the repository root parameter is set either
+in Stub Runner or in a Spring Cloud Contract plugin.</p>
+</div>
+<div class="paragraph">
+<p>In this example the <code>producer</code> project has been successfully
+built and stubs were generated under the <code>target/stubs</code> folder. As a consumer one can setup the Stub Runner to pick the stubs from that location using the <code>stubs://</code> protocol.</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Annotation</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(
+stubsMode = StubRunnerProperties.StubsMode.REMOTE,
+        repositoryRoot = "stubs://file://location/to/the/producer/target/stubs/",
+        ids = "com.example:some-producer")</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">JUnit 4 Rule</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Rule
+    public StubRunnerRule rule = new StubRunnerRule()
+            .downloadStub("com.example:some-producer")
+            .repoRoot("stubs://file://location/to/the/producer/target/stubs/")
+            .stubsMode(StubRunnerProperties.StubsMode.REMOTE);</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">JUnit 5 Extension</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RegisterExtension
+    public StubRunnerExtension stubRunnerExtension = new StubRunnerExtension()
+            .downloadStub("com.example:some-producer")
+            .repoRoot("stubs://file://location/to/the/producer/target/stubs/")
+            .stubsMode(StubRunnerProperties.StubsMode.REMOTE);</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Contracts and stubs may be stored in a location, where each producer has its own, dedicated folder for contracts and stub mappings. Under that folder each consumer can have its own setup. To make Stub Runner find the dedicated folder from the provided ids one can pass a property <code>stubs.find-producer=true</code> or a system property <code>stubrunner.stubs.find-producer=true</code> .</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">└── com.example <i class="conum" data-value="1"></i><b>(1)</b>
+    ├── some-artifact-id <i class="conum" data-value="2"></i><b>(2)</b>
+    │   └── 0.0.1
+    │       ├── contracts <i class="conum" data-value="3"></i><b>(3)</b>
+    │       │   └── shouldReturnStuffForArtifactId.groovy
+    │       └── mappings <i class="conum" data-value="4"></i><b>(4)</b>
+    │           └── shouldReturnStuffForArtifactId.json
+    └── some-other-artifact-id <i class="conum" data-value="5"></i><b>(5)</b>
+        ├── contracts
+        │   └── shouldReturnStuffForOtherArtifactId.groovy
+        └── mappings
+            └── shouldReturnStuffForOtherArtifactId.json</code></pre>
+</div>
+</div>
+<div class="colist arabic">
+<table>
+<tr>
+<td><i class="conum" data-value="1"></i><b>1</b></td>
+<td>group id of the consumers</td>
+</tr>
+<tr>
+<td><i class="conum" data-value="2"></i><b>2</b></td>
+<td>consumer with artifact id [some-artifact-id]</td>
+</tr>
+<tr>
+<td><i class="conum" data-value="3"></i><b>3</b></td>
+<td>contracts for the consumer with artifact id [some-artifact-id]</td>
+</tr>
+<tr>
+<td><i class="conum" data-value="4"></i><b>4</b></td>
+<td>mappings for the consumer with artifact id [some-artifact-id]</td>
+</tr>
+<tr>
+<td><i class="conum" data-value="5"></i><b>5</b></td>
+<td>consumer with artifact id [some-other-artifact-id]</td>
+</tr>
+</table>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Annotation</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(
+stubsMode = StubRunnerProperties.StubsMode.REMOTE,
+        repositoryRoot = "stubs://file://location/to/the/contracts/directory",
+        ids = "com.example:some-producer",
+        properties="stubs.find-producer=true")</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">JUnit 4 Rule</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">    static Map&lt;String, String&gt; contractProperties() {
+        Map&lt;String, String&gt; map = new HashMap&lt;&gt;();
+        map.put("stubs.find-producer", "true");
+        return map;
+    }
+
+@Rule
+    public StubRunnerRule rule = new StubRunnerRule()
+            .downloadStub("com.example:some-producer")
+            .repoRoot("stubs://file://location/to/the/contracts/directory")
+            .stubsMode(StubRunnerProperties.StubsMode.REMOTE)
+            .properties(contractProperties());</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">JUnit 5 Extension</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">    static Map&lt;String, String&gt; contractProperties() {
+        Map&lt;String, String&gt; map = new HashMap&lt;&gt;();
+        map.put("stubs.find-producer", "true");
+        return map;
+    }
+
+@RegisterExtension
+    public StubRunnerExtension stubRunnerExtension = new StubRunnerExtension()
+            .downloadStub("com.example:some-producer")
+            .repoRoot("stubs://file://location/to/the/contracts/directory")
+            .stubsMode(StubRunnerProperties.StubsMode.REMOTE)
+            .properties(contractProperties());</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-stub-runner-generate-stubs-at-runtime"><a class="anchor" href="#features-stub-runner-generate-stubs-at-runtime"></a><a class="link" href="#features-stub-runner-generate-stubs-at-runtime">3.5.9. Generating Stubs at Runtime</a></h4>
+<div class="paragraph">
+<p>As a consumer, you might not want to wait for the producer to finish its implementation and then publish their stubs. A solution to this problem can be generation of stubs at runtime.</p>
+</div>
+<div class="paragraph">
+<p>As a producer, when a contract is defined, you are required to make the generated tests pass in order for the stubs to be published. There are cases where you would like to unblock the consumers so that they can fetch the stubs before your tests are actually passing. In this case you should set such contracts as in progress. You can read more about this under the <a href="#contract-dsl-in-progress">Contracts in Progress</a> section. That way your tests will not be generated, but the stubs will.</p>
+</div>
+<div class="paragraph">
+<p>As a consumer, you can toggle a switch to generate stubs at runtime. Stub Runner will ignore all the existing stub mappings and will generate new ones for all the contract definitions. Another option is to pass the <code>stubrunner.generate-stubs</code> system property. Below you can find an example of such setup.</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Annotation</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(
+stubsMode = StubRunnerProperties.StubsMode.REMOTE,
+        repositoryRoot = "stubs://file://location/to/the/contracts",
+        ids = "com.example:some-producer",
+        generateStubs = true)</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">JUnit 4 Rule</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Rule
+    public StubRunnerRule rule = new StubRunnerRule()
+            .downloadStub("com.example:some-producer")
+            .repoRoot("stubs://file://location/to/the/contracts")
+            .stubsMode(StubRunnerProperties.StubsMode.REMOTE)
+            .withGenerateStubs(true);</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">JUnit 5 Extension</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RegisterExtension
+    public StubRunnerExtension stubRunnerExtension = new StubRunnerExtension()
+            .downloadStub("com.example:some-producer")
+            .repoRoot("stubs://file://location/to/the/contracts")
+            .stubsMode(StubRunnerProperties.StubsMode.REMOTE)
+            .withGenerateStubs(true);</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-stub-runner-fail-on-no-stubs"><a class="anchor" href="#features-stub-runner-fail-on-no-stubs"></a><a class="link" href="#features-stub-runner-fail-on-no-stubs">3.5.10. Fail On No Stubs</a></h4>
+<div class="paragraph">
+<p>By default Stub Runner will fail if no stubs were found. In order to change that behaviour, just set to <code>false</code> the <code>failOnNoStubs</code> property in the annotation or call the <code>withFailOnNoStubs(false)</code> method on a JUnit Rule or Extension.</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Annotation</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(
+stubsMode = StubRunnerProperties.StubsMode.REMOTE,
+        repositoryRoot = "stubs://file://location/to/the/contracts",
+        ids = "com.example:some-producer",
+        failOnNoStubs = false)</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">JUnit 4 Rule</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Rule
+    public StubRunnerRule rule = new StubRunnerRule()
+            .downloadStub("com.example:some-producer")
+            .repoRoot("stubs://file://location/to/the/contracts")
+            .stubsMode(StubRunnerProperties.StubsMode.REMOTE)
+            .withFailOnNoStubs(false);</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">JUnit 5 Extension</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RegisterExtension
+    public StubRunnerExtension stubRunnerExtension = new StubRunnerExtension()
+            .downloadStub("com.example:some-producer")
+            .repoRoot("stubs://file://location/to/the/contracts")
+            .stubsMode(StubRunnerProperties.StubsMode.REMOTE)
+            .withFailOnNoStubs(false);</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-stub-runner-common"><a class="anchor" href="#features-stub-runner-common"></a><a class="link" href="#features-stub-runner-common">3.5.11. Common Properties</a></h4>
+<div class="paragraph">
+<p>This section briefly describes common properties, including:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="#features-stub-runner-common-properties-junit-spring">Common Properties for JUnit and Spring</a></p>
+</li>
+<li>
+<p><a href="#features-stub-runner-stub-runner-stub-ids">Stub Runner Stubs IDs</a></p>
+</li>
+</ul>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-common-properties-junit-spring"><a class="anchor" href="#features-stub-runner-common-properties-junit-spring"></a><a class="link" href="#features-stub-runner-common-properties-junit-spring">Common Properties for JUnit and Spring</a></h5>
+<div class="paragraph">
+<p>You can set repetitive properties by using system properties or Spring configuration
+properties. The following table shows their names with their default values:</p>
+</div>
+<table class="tableblock frame-topbot grid-all stretch">
+<colgroup>
+<col style="width: 33.3333%;">
+<col style="width: 33.3333%;">
+<col style="width: 33.3334%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Property name</th>
+<th class="tableblock halign-left valign-top">Default value</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.minPort</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">10000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Minimum value of a port for a started WireMock with stubs.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.maxPort</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">15000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Maximum value of a port for a started WireMock with stubs.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.repositoryRoot</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Maven repo URL. If blank, then call the local Maven repo.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.classifier</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubs</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Default classifier for the stub artifacts.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.stubsMode</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">CLASSPATH</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The way you want to fetch and register the stubs</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.ids</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Array of Ivy notation stubs to download.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.username</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Optional username to access the tool that stores the JARs with
+stubs.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.password</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Optional password to access the tool that stores the JARs with
+stubs.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.stubsPerConsumer</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>false</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Set to <code>true</code> if you want to use different stubs for
+each consumer instead of registering all stubs for every consumer.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.consumerName</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If you want to use a stub for each consumer and want to
+override the consumer name, change this value.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect4">
+<h5 id="features-stub-runner-stub-runner-stub-ids"><a class="anchor" href="#features-stub-runner-stub-runner-stub-ids"></a><a class="link" href="#features-stub-runner-stub-runner-stub-ids">Stub Runner Stubs IDs</a></h5>
+<div class="paragraph">
+<p>You can set the stubs to download in the <code>stubrunner.ids</code> system property. They
+use the following pattern:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">groupId:artifactId:version:classifier:port</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Note that <code>version</code>, <code>classifier</code>, and <code>port</code> are optional.</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>If you do not provide the <code>port</code>, a random one is picked.</p>
+</li>
+<li>
+<p>If you do not provide the <code>classifier</code>, the default is used. (Note that you can
+pass an empty classifier this way: <code>groupId:artifactId:version:</code>).</p>
+</li>
+<li>
+<p>If you do not provide the <code>version</code>, then <code>+</code> is passed, and the latest one is
+downloaded.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p><code>port</code> means the port of the WireMock server.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+Starting with version 1.0.4, you can provide a range of versions that you
+would like the Stub Runner to take into consideration. You can read more about the
+<a href="https://wiki.eclipse.org/Aether/New_and_Noteworthy#Version_Ranges">Aether versioning
+ranges here</a>.
+</td>
+</tr>
+</table>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="features-wiremock"><a class="anchor" href="#features-wiremock"></a><a class="link" href="#features-wiremock">3.6. Spring Cloud Contract WireMock</a></h3>
+<div class="paragraph">
+<p>The Spring Cloud Contract WireMock modules let you use <a href="https://github.com/tomakehurst/wiremock">WireMock</a> in a
+Spring Boot application. Check out the
+<a href="https://github.com/spring-cloud/spring-cloud-contract/tree/master/samples">samples</a>
+for more details.</p>
+</div>
+<div class="paragraph">
+<p>If you have a Spring Boot application that uses Tomcat as an embedded server (which is
+the default with <code>spring-boot-starter-web</code>), you can add
+<code>spring-cloud-starter-contract-stub-runner</code> to your classpath and add <code>@AutoConfigureWireMock</code>
+to use Wiremock in your tests. Wiremock runs as a stub server, and you
+can register stub behavior by using a Java API or by using static JSON declarations as part of
+your test. The following code shows an example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@SpringBootTest(webEnvironment = WebEnvironment.RANDOM_PORT)
+@AutoConfigureWireMock(port = 0)
+public class WiremockForDocsTests {
+
+    // A service that calls out over HTTP
+    @Autowired
+    private Service service;
+
+    @BeforeEach
+    public void setup() {
+        this.service.setBase("http://localhost:"
+                + this.environment.getProperty("wiremock.server.port"));
+    }
+
+    // Using the WireMock APIs in the normal way:
+    @Test
+    public void contextLoads() throws Exception {
+        // Stubbing WireMock
+        stubFor(get(urlEqualTo("/resource")).willReturn(aResponse()
+                .withHeader("Content-Type", "text/plain").withBody("Hello World!")));
+        // We're asserting if WireMock responded properly
+        assertThat(this.service.go()).isEqualTo("Hello World!");
+    }
+
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>To start the stub server on a different port, use (for example),
+<code>@AutoConfigureWireMock(port=9999)</code>. For a random port, use a value of <code>0</code>. The stub
+server port can be bound in the test application context with the "wiremock.server.port"
+property. Using <code>@AutoConfigureWireMock</code> adds a bean of type <code>WiremockConfiguration</code> to
+your test application context, where it is cached between methods and classes
+having the same context. The same is true for Spring integration tests. Also, you can
+inject a bean of type <code>WireMockServer</code> into your test.
+The registered WireMock server is reset after each test class, however, if you need to reset it after each test method, just set the <code>wiremock.reset-mappings-after-each-test</code> property to <code>true</code>.</p>
+</div>
+<div class="sect3">
+<h4 id="features-wiremock-registering-stubs"><a class="anchor" href="#features-wiremock-registering-stubs"></a><a class="link" href="#features-wiremock-registering-stubs">3.6.1. Registering Stubs Automatically</a></h4>
+<div class="paragraph">
+<p>If you use <code>@AutoConfigureWireMock</code>, it registers WireMock JSON stubs from the file
+system or classpath (by default, from <code>file:src/test/resources/mappings</code>). You can
+customize the locations by using the <code>stubs</code> attribute in the annotation, which can be an
+Ant-style resource pattern or a directory. In the case of a directory, <code><strong>*/</strong>.json</code> is
+appended. The following code shows an example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre>@RunWith(SpringRunner.class)
+@SpringBootTest
+@AutoConfigureWireMock(stubs="classpath:/stubs")
+public class WiremockImportApplicationTests {
+
+    @Autowired
+    private Service service;
+
+    @Test
+    public void contextLoads() throws Exception {
+        assertThat(this.service.go()).isEqualTo("Hello World!");
+    }
+
+}</pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+Actually, WireMock always loads mappings from <code>src/test/resources/mappings</code> <strong>as
+well as</strong> the custom locations in the <code>stubs</code> attribute. To change this behavior, you can
+also specify a files root, as described in the next section of this document.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>If you use Spring Cloud Contract&#8217;s default stub jars, your
+stubs are stored in the <code>/META-INF/group-id/artifact-id/versions/mappings/</code> folder.
+If you want to register all stubs from that location, from all embedded JARs, you can use
+the following syntax:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureWireMock(port = 0, stubs = "classpath*:/META-INF/**/mappings/**/*.json")</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-wiremock-using-files"><a class="anchor" href="#features-wiremock-using-files"></a><a class="link" href="#features-wiremock-using-files">3.6.2. Using Files to Specify the Stub Bodies</a></h4>
+<div class="paragraph">
+<p>WireMock can read response bodies from files on the classpath or the file system. In the
+case of the file system, you can see in the JSON DSL that the response has a <code>bodyFileName</code> instead of a
+(literal) <code>body</code>. The files are resolved relative to a root directory (by default,
+<code>src/test/resources/__files</code>). To customize this location, you can set the <code>files</code>
+attribute in the <code>@AutoConfigureWireMock</code> annotation to the location of the parent
+directory (in other words, <code>__files</code> is a subdirectory). You can use Spring resource
+notation to refer to <code>file:&#8230;&#8203;</code> or <code>classpath:&#8230;&#8203;</code> locations. Generic URLs are not
+supported. A list of values can be given&#8201;&#8212;&#8201;in which case, WireMock resolves the first file
+that exists when it needs to find a response body.</p>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+When you configure the <code>files</code> root, it also affects the
+automatic loading of stubs, because they come from the root location
+in a subdirectory called <code>mappings</code>. The value of <code>files</code> has no
+effect on the stubs loaded explicitly from the <code>stubs</code> attribute.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-wiremock-junit-rule"><a class="anchor" href="#features-wiremock-junit-rule"></a><a class="link" href="#features-wiremock-junit-rule">3.6.3. Alternative: Using JUnit Rules</a></h4>
+<div class="paragraph">
+<p>For a more conventional WireMock experience, you can use JUnit <code>@Rules</code> to start and stop
+the server. To do so, use the <code>WireMockSpring</code> convenience class to obtain an <code>Options</code>
+instance, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@SpringBootTest(webEnvironment = WebEnvironment.RANDOM_PORT)
+public class WiremockForDocsClassRuleTests {
+
+    // Start WireMock on some dynamic port
+    // for some reason `dynamicPort()` is not working properly
+    public static WireMockServer wiremock = new WireMockServer(WireMockSpring.options().dynamicPort());
+
+    @BeforeAll
+    static void setupClass() {
+        wiremock.start();
+    }
+
+    @AfterEach
+    void after() {
+        wiremock.resetAll();
+    }
+
+    @AfterAll
+    static void clean() {
+        wiremock.shutdown();
+    }
+
+    // A service that calls out over HTTP to wiremock's port
+    @Autowired
+    private Service service;
+
+    @BeforeEach
+    public void setup() {
+        this.service.setBase("http://localhost:" + wiremock.port());
+    }
+
+    // Using the WireMock APIs in the normal way:
+    @Test
+    public void contextLoads() throws Exception {
+        // Stubbing WireMock
+        wiremock.stubFor(get(urlEqualTo("/resource")).willReturn(aResponse()
+                .withHeader("Content-Type", "text/plain").withBody("Hello World!")));
+        // We're asserting if WireMock responded properly
+        assertThat(this.service.go()).isEqualTo("Hello World!");
+    }
+
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The <code>@ClassRule</code> means that the server shuts down after all the methods in this class
+have been run.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-wiremock-relaxed-ssl"><a class="anchor" href="#features-wiremock-relaxed-ssl"></a><a class="link" href="#features-wiremock-relaxed-ssl">3.6.4. Relaxed SSL Validation for Rest Template</a></h4>
+<div class="paragraph">
+<p>WireMock lets you stub a &#8220;secure&#8221; server with an <code>https</code> URL protocol. If your
+application wants to contact that stub server in an integration test, it will find that
+the SSL certificates are not valid (the usual problem with self-installed certificates).
+The best option is often to re-configure the client to use <code>http</code>. If that is not an
+option, you can ask Spring to configure an HTTP client that ignores SSL validation errors
+(do so only for tests, of course).</p>
+</div>
+<div class="paragraph">
+<p>To make this work with minimum fuss, you need to use the Spring Boot
+<code>RestTemplateBuilder</code> in your application, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Bean
+public RestTemplate restTemplate(RestTemplateBuilder builder) {
+    return builder.build();
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You need <code>RestTemplateBuilder</code> because the builder is passed through callbacks to
+initialize it, so the SSL validation can be set up in the client at that point. This
+happens automatically in your test if you use the <code>@AutoConfigureWireMock</code>
+annotation or the stub runner. If you use the JUnit <code>@Rule</code> approach, you need to add the
+<code>@AutoConfigureHttpClient</code> annotation as well, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
+@SpringBootTest("app.baseUrl=https://localhost:6443")
+@AutoConfigureHttpClient
+public class WiremockHttpsServerApplicationTests {
+
+    @ClassRule
+    public static WireMockClassRule wiremock = new WireMockClassRule(
+            WireMockSpring.options().httpsPort(6443));
+...
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>If you use <code>spring-boot-starter-test</code>, you have the Apache HTTP client on the
+classpath, and it is selected by the <code>RestTemplateBuilder</code> and configured to ignore SSL
+errors. If you use the default <code>java.net</code> client, you do not need the annotation (but it
+does no harm). There is currently no support for other clients, but it may be added
+in future releases.</p>
+</div>
+<div class="paragraph">
+<p>To disable the custom <code>RestTemplateBuilder</code>, set the <code>wiremock.rest-template-ssl-enabled</code>
+property to <code>false</code>.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="features-wiremock-spring-mvc-mocks"><a class="anchor" href="#features-wiremock-spring-mvc-mocks"></a><a class="link" href="#features-wiremock-spring-mvc-mocks">3.6.5. WireMock and Spring MVC Mocks</a></h4>
+<div class="paragraph">
+<p>Spring Cloud Contract provides a convenience class that can load JSON WireMock stubs into
+a Spring <code>MockRestServiceServer</code>. The following code shows an example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@SpringBootTest(webEnvironment = WebEnvironment.NONE)
+public class WiremockForDocsMockServerApplicationTests {
+
+    @Autowired
+    private RestTemplate restTemplate;
+
+    @Autowired
+    private Service service;
+
+    @Test
+    public void contextLoads() throws Exception {
+        // will read stubs classpath
+        MockRestServiceServer server = WireMockRestServiceServer.with(this.restTemplate)
+                .baseUrl("https://example.org").stubs("classpath:/stubs/resource.json")
+                .build();
+        // We're asserting if WireMock responded properly
+        assertThat(this.service.go()).isEqualTo("Hello World");
+        server.verify();
+    }
+
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The <code>baseUrl</code> value is prepended to all mock calls, and the <code>stubs()</code> method takes a stub
+path resource pattern as an argument. In the preceding example, the stub defined at
+<code>/stubs/resource.json</code> is loaded into the mock server. If the <code>RestTemplate</code> is asked to
+visit <code><a href="https://example.org/" class="bare">example.org/</a></code>, it gets the responses as being declared at that URL. More
+than one stub pattern can be specified, and each one can be a directory (for a recursive
+list of all <code>.json</code>), a fixed filename (as in the preceding example), or an Ant-style
+pattern. The JSON format is the normal WireMock format, which you can read about at the
+<a href="https://wiremock.org/docs/stubbing/">WireMock website</a>.</p>
+</div>
+<div class="paragraph">
+<p>Currently, the Spring Cloud Contract Verifier supports Tomcat, Jetty, and Undertow as
+Spring Boot embedded servers, and Wiremock itself has &#8220;native&#8221; support for a particular
+version of Jetty (currently 9.2). To use the native Jetty, you need to add the native
+Wiremock dependencies and exclude the Spring Boot container (if there is one).</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="features-build-tools"><a class="anchor" href="#features-build-tools"></a><a class="link" href="#features-build-tools">3.7. Build Tools Integration</a></h3>
+<div class="paragraph">
+<p>You can run test generation and stub execution in various ways. The most common ones are
+as follows:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="maven-project.html">Maven</a></p>
+</li>
+<li>
+<p><a href="gradle-project.html">Gradle</a></p>
+</li>
+<li>
+<p><a href="docker-project.html">Docker</a></p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="features-whats-next"><a class="anchor" href="#features-whats-next"></a><a class="link" href="#features-whats-next">3.8. What to Read Next</a></h3>
+<div class="paragraph">
+<p>If you want to learn more about any of the classes discussed in this section, you can browse the
+<a href="https://github.com/spring-cloud/spring-cloud-contract/tree/master">source code directly</a>. If you have specific questions, see the
+<a href="#howto">how-to</a> section.</p>
+</div>
+<div class="paragraph">
+<p>If you are comfortable with Spring Cloud Contract&#8217;s core features, you can continue on and read
+about
+<a href="#advanced.adoc">Spring Cloud Contract&#8217;s advanced features</a>.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="maven-project"><a class="anchor" href="#maven-project"></a><a class="link" href="#maven-project">4. Maven Project</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>To learn how to set up the Maven project for Spring Cloud Contract Verifier, read the
+following sections:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="#maven-add-plugin">Adding the Maven Plugin</a></p>
+</li>
+<li>
+<p><a href="#maven-rest-assured">Maven and Rest Assured 2.0</a></p>
+</li>
+<li>
+<p><a href="#maven-snapshot-versions">Using Snapshot and Milestone Versions for Maven</a></p>
+</li>
+<li>
+<p><a href="#maven-add-stubs">Adding stubs</a></p>
+</li>
+<li>
+<p><a href="#maven-run-plugin">Run plugin</a></p>
+</li>
+<li>
+<p><a href="#maven-configure-plugin">Configure plugin</a></p>
+</li>
+<li>
+<p><a href="#maven-configuration-options">Configuration Options</a></p>
+</li>
+<li>
+<p><a href="#maven-single-base">Single Base Class for All Tests</a></p>
+</li>
+<li>
+<p><a href="#maven-different-base">Using Different Base Classes for Contracts</a></p>
+</li>
+<li>
+<p><a href="#maven-invoking-generated-tests">Invoking Generated Tests</a></p>
+</li>
+<li>
+<p><a href="#maven-pushing-stubs-to-scm">Pushing Stubs to SCM</a></p>
+</li>
+<li>
+<p><a href="#maven-sts">Maven Plugin and STS</a></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>You can also check the plugin&#8217;s documentation  <a href="../../spring-cloud-contract-maven-plugin/index.html">here</a>.</p>
+</div>
+<div class="sect2">
+<h3 id="maven-add-plugin"><a class="anchor" href="#maven-add-plugin"></a><a class="link" href="#maven-add-plugin">4.1. Adding the Maven Plugin</a></h3>
+<div class="paragraph">
+<p>Add the Spring Cloud Contract BOM in a fashion similar to the following:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependencyManagement&gt;
+    &lt;dependencies&gt;
+        &lt;dependency&gt;
+            &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+            &lt;artifactId&gt;spring-cloud-dependencies&lt;/artifactId&gt;
+            &lt;version&gt;${spring-cloud-release.version}&lt;/version&gt;
+            &lt;type&gt;pom&lt;/type&gt;
+            &lt;scope&gt;import&lt;/scope&gt;
+        &lt;/dependency&gt;
+    &lt;/dependencies&gt;
+&lt;/dependencyManagement&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Next, add the <code>Spring Cloud Contract Verifier</code> Maven plugin, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">            &lt;plugin&gt;
+                &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+                &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+                &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+                &lt;extensions&gt;true&lt;/extensions&gt;
+                &lt;configuration&gt;
+                    &lt;packageWithBaseClasses&gt;com.example.fraud&lt;/packageWithBaseClasses&gt;
+&lt;!--                    &lt;convertToYaml&gt;true&lt;/convertToYaml&gt;--&gt;
+                &lt;/configuration&gt;
+                &lt;!-- if additional dependencies are needed e.g. for Pact --&gt;
+                &lt;dependencies&gt;
+                    &lt;dependency&gt;
+                        &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+                        &lt;artifactId&gt;spring-cloud-contract-pact&lt;/artifactId&gt;
+                        &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+                    &lt;/dependency&gt;
+                &lt;/dependencies&gt;
+            &lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You can read more in the
+spring-cloud-contract-maven-plugin/index.html[Spring
+Cloud Contract Maven Plugin Documentation].</p>
+</div>
+<div class="paragraph">
+<p>Sometimes, regardless of the picked IDE, you can see that the <code>target/generated-test-source</code> folder is not visible on the IDE&#8217;s classpath. To ensure that it&#8217;s always there, you can add the following entry to your <code>pom.xml</code></p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+                &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
+                &lt;artifactId&gt;build-helper-maven-plugin&lt;/artifactId&gt;
+                &lt;executions&gt;
+                    &lt;execution&gt;
+                        &lt;id&gt;add-source&lt;/id&gt;
+                        &lt;phase&gt;generate-test-sources&lt;/phase&gt;
+                        &lt;goals&gt;
+                            &lt;goal&gt;add-test-source&lt;/goal&gt;
+                        &lt;/goals&gt;
+                        &lt;configuration&gt;
+                            &lt;sources&gt;
+                                &lt;source&gt;${project.build.directory}/generated-test-sources/contracts/&lt;/source&gt;
+                            &lt;/sources&gt;
+                        &lt;/configuration&gt;
+                    &lt;/execution&gt;
+                &lt;/executions&gt;
+            &lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="maven-rest-assured"><a class="anchor" href="#maven-rest-assured"></a><a class="link" href="#maven-rest-assured">4.2. Maven and Rest Assured 2.0</a></h3>
+<div class="paragraph">
+<p>By default, Rest Assured 3.x is added to the classpath. However, you can use Rest
+Assured 2.x by adding it to the plugins classpath, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;packageWithBaseClasses&gt;com.example&lt;/packageWithBaseClasses&gt;
+    &lt;/configuration&gt;
+    &lt;dependencies&gt;
+        &lt;dependency&gt;
+            &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+            &lt;artifactId&gt;spring-cloud-contract-verifier&lt;/artifactId&gt;
+            &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+        &lt;/dependency&gt;
+        &lt;dependency&gt;
+           &lt;groupId&gt;com.jayway.restassured&lt;/groupId&gt;
+           &lt;artifactId&gt;rest-assured&lt;/artifactId&gt;
+           &lt;version&gt;2.5.0&lt;/version&gt;
+           &lt;scope&gt;compile&lt;/scope&gt;
+        &lt;/dependency&gt;
+        &lt;dependency&gt;
+           &lt;groupId&gt;com.jayway.restassured&lt;/groupId&gt;
+           &lt;artifactId&gt;spring-mock-mvc&lt;/artifactId&gt;
+           &lt;version&gt;2.5.0&lt;/version&gt;
+           &lt;scope&gt;compile&lt;/scope&gt;
+        &lt;/dependency&gt;
+    &lt;/dependencies&gt;
+&lt;/plugin&gt;
+
+&lt;dependencies&gt;
+    &lt;!-- all dependencies --&gt;
+    &lt;!-- you can exclude rest-assured from spring-cloud-contract-verifier --&gt;
+    &lt;dependency&gt;
+       &lt;groupId&gt;com.jayway.restassured&lt;/groupId&gt;
+       &lt;artifactId&gt;rest-assured&lt;/artifactId&gt;
+       &lt;version&gt;2.5.0&lt;/version&gt;
+       &lt;scope&gt;test&lt;/scope&gt;
+    &lt;/dependency&gt;
+    &lt;dependency&gt;
+       &lt;groupId&gt;com.jayway.restassured&lt;/groupId&gt;
+       &lt;artifactId&gt;spring-mock-mvc&lt;/artifactId&gt;
+       &lt;version&gt;2.5.0&lt;/version&gt;
+       &lt;scope&gt;test&lt;/scope&gt;
+    &lt;/dependency&gt;
+&lt;/dependencies&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>That way, the plugin automatically sees that Rest Assured 2.x is present on the classpath
+and modifies the imports accordingly.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="maven-snapshot-versions"><a class="anchor" href="#maven-snapshot-versions"></a><a class="link" href="#maven-snapshot-versions">4.3. Using Snapshot and Milestone Versions for Maven</a></h3>
+<div class="paragraph">
+<p>To use Snapshot and Milestone versions, you have to add the following section to your
+<code>pom.xml</code>:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;repositories&gt;
+    &lt;repository&gt;
+        &lt;id&gt;spring-snapshots&lt;/id&gt;
+        &lt;name&gt;Spring Snapshots&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;true&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/repository&gt;
+    &lt;repository&gt;
+        &lt;id&gt;spring-milestones&lt;/id&gt;
+        &lt;name&gt;Spring Milestones&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;false&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/repository&gt;
+    &lt;repository&gt;
+        &lt;id&gt;spring-releases&lt;/id&gt;
+        &lt;name&gt;Spring Releases&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;false&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/repository&gt;
+&lt;/repositories&gt;
+&lt;pluginRepositories&gt;
+    &lt;pluginRepository&gt;
+        &lt;id&gt;spring-snapshots&lt;/id&gt;
+        &lt;name&gt;Spring Snapshots&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;true&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/pluginRepository&gt;
+    &lt;pluginRepository&gt;
+        &lt;id&gt;spring-milestones&lt;/id&gt;
+        &lt;name&gt;Spring Milestones&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;false&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/pluginRepository&gt;
+    &lt;pluginRepository&gt;
+        &lt;id&gt;spring-releases&lt;/id&gt;
+        &lt;name&gt;Spring Releases&lt;/name&gt;
+        &lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
+        &lt;snapshots&gt;
+            &lt;enabled&gt;false&lt;/enabled&gt;
+        &lt;/snapshots&gt;
+    &lt;/pluginRepository&gt;
+&lt;/pluginRepositories&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="maven-add-stubs"><a class="anchor" href="#maven-add-stubs"></a><a class="link" href="#maven-add-stubs">4.4. Adding stubs</a></h3>
+<div class="paragraph">
+<p>By default, Spring Cloud Contract Verifier looks for stubs in the
+<code>src/test/resources/contracts</code> directory. The directory containing stub definitions is
+treated as a class name, and each stub definition is treated as a single test. We assume
+that it contains at least one directory to be used as the test class name. If there is more
+than one level of nested directories, all except the last one is used as the package name.
+Consider the following structure:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">src/test/resources/contracts/myservice/shouldCreateUser.groovy
+src/test/resources/contracts/myservice/shouldReturnUser.groovy</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Given that structure, Spring Cloud Contract Verifier creates a test class named
+<code>defaultBasePackage.MyService</code> with two methods:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>shouldCreateUser()</code></p>
+</li>
+<li>
+<p><code>shouldReturnUser()</code></p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="maven-run-plugin"><a class="anchor" href="#maven-run-plugin"></a><a class="link" href="#maven-run-plugin">4.5. Run plugin</a></h3>
+<div class="paragraph">
+<p>The <code>generateTests</code> plugin goal is assigned to be invoked in the phase called
+<code>generate-test-sources</code>. If you want it to be part of your build process, you need not do
+anything. If you want only to generate tests, invoke the <code>generateTests</code> goal.</p>
+</div>
+<div class="paragraph">
+<p>If you want to run stubs via Maven it&#8217;s enough to call the <code>run</code> goal with the stubs to run as the <code>spring.cloud.contract.verifier.stubs</code> system property as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="paragraph">
+<p>mvn org.springframework.cloud:spring-cloud-contract-maven-plugin:run \
+-Dspring.cloud.contract.verifier.stubs="com.acme:service-name"</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="maven-configure-plugin"><a class="anchor" href="#maven-configure-plugin"></a><a class="link" href="#maven-configure-plugin">4.6. Configure plugin</a></h3>
+<div class="paragraph">
+<p>To change the default configuration, you can add a <code>configuration</code> section to the plugin
+definition or the <code>execution</code> definition, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;executions&gt;
+        &lt;execution&gt;
+            &lt;goals&gt;
+                &lt;goal&gt;convert&lt;/goal&gt;
+                &lt;goal&gt;generateStubs&lt;/goal&gt;
+                &lt;goal&gt;generateTests&lt;/goal&gt;
+            &lt;/goals&gt;
+        &lt;/execution&gt;
+    &lt;/executions&gt;
+    &lt;configuration&gt;
+        &lt;basePackageForTests&gt;org.springframework.cloud.verifier.twitter.place&lt;/basePackageForTests&gt;
+        &lt;baseClassForTests&gt;org.springframework.cloud.verifier.twitter.place.BaseMockMvcSpec&lt;/baseClassForTests&gt;
+    &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="maven-configuration-options"><a class="anchor" href="#maven-configuration-options"></a><a class="link" href="#maven-configuration-options">4.7. Configuration Options</a></h3>
+<div class="ulist">
+<ul>
+<li>
+<p><code>testMode</code>: Defines the mode for acceptance tests. By default, the mode is <code>MockMvc</code>,
+which is based on Spring&#8217;s MockMvc. You can also change it to <code>WebTestClient</code>, <code>JaxRsClient</code>, or
+<code>Explicit</code> (for real HTTP calls).</p>
+</li>
+<li>
+<p><code>basePackageForTests</code>: Specifies the base package for all generated tests. If not set,
+the value is picked from the package of <code>baseClassForTests</code> and from <code>packageWithBaseClasses</code>.
+If neither of these values are set, the value is set to
+<code>org.springframework.cloud.contract.verifier.tests</code>.</p>
+</li>
+<li>
+<p><code>ruleClassForTests</code>: Specifies a rule that should be added to the generated test
+classes.</p>
+</li>
+<li>
+<p><code>baseClassForTests</code>: Creates a base class for all generated tests. By default, if you
+use Spock classes, the class is <code>spock.lang.Specification</code>.</p>
+</li>
+<li>
+<p>contractsDirectory: Specifies a directory that contains contracts written with the
+Groovyn DSL. The default directory is <code>/src/test/resources/contracts</code>.</p>
+</li>
+<li>
+<p><code>generatedTestSourcesDir</code>: Specifies the test source directory where tests generated
+from the Groovy DSL should be placed. By default, its value is
+<code>$buildDir/generated-test-sources/contracts</code>.</p>
+</li>
+<li>
+<p><code>generatedTestResourcesDir</code>: Specifies the test resource directory for resources used by the generated tests.</p>
+</li>
+<li>
+<p><code>testFramework</code>: Specifies the target test framework to be used. Currently, Spock, JUnit 4 (<code>TestFramework.JUNIT</code>), and
+JUnit 5 are supported, with JUnit 4 being the default framework.</p>
+</li>
+<li>
+<p><code>packageWithBaseClasses</code>: Defines a package where all the base classes reside. This
+setting takes precedence over <code>baseClassForTests</code>. The convention is such that, if you
+have a contract under (for example) <code>src/test/resources/contract/foo/bar/baz/</code> and set
+the value of the <code>packageWithBaseClasses</code> property to <code>com.example.base</code>, Spring
+Cloud Contract Verifier assumes that there is a <code>BarBazBase</code> class under the
+<code>com.example.base</code> package. In other words, the system takes the last two parts of the
+package, if they exist, and forms a class with <code>Base</code> as a suffix.</p>
+</li>
+<li>
+<p><code>baseClassMappings</code>: Specifies a list of base class mappings that provide
+<code>contractPackageRegex</code> (which is checked against the package where the contract is
+located) and <code>baseClassFQN</code>( which maps to the fully qualified name of the base class for
+the matched contract). For example, if you have a contract under
+<code>src/test/resources/contract/foo/bar/baz/</code> and map the
+<code>.* &#8594; com.example.base.BaseClass</code> property, the test class generated from these contracts
+extends <code>com.example.base.BaseClass</code>. This setting takes precedence over
+<code>packageWithBaseClasses</code> and <code>baseClassForTests</code>.</p>
+</li>
+<li>
+<p><code>contractsProperties</code>: A map that contains properties to be passed to Spring Cloud Contract
+components. Those properties might be used by (for example) built-in or custom Stub Downloaders.</p>
+</li>
+<li>
+<p><code>failOnNoContracts</code>: When enabled, will throw an exception when no contracts were found. Defaults to <code>true</code>.</p>
+</li>
+<li>
+<p><code>failOnInProgress</code>: If set to true then if any contracts that are in progress are found, will break the build. On the producer side you need to be explicit about the fact that you have contracts in progress and take into consideration that you might be causing false positive test execution results on the consumer side.. Defaults to <code>true</code>.</p>
+</li>
+<li>
+<p><code>incrementalContractTests</code>: When enabled, tests are created only when contracts have changed since last build. Defaults to <code>true</code>.</p>
+</li>
+<li>
+<p><code>incrementalContractStubs</code>: When enabled, stubs are created only when contracts have changed since last build. Defaults to <code>true</code>.</p>
+</li>
+<li>
+<p><code>incrementalContractStubsJar</code>: When enabled, stubs jar is created only when stubs have changed since last build. Defaults to <code>true</code>.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>If you want to download your contract definitions from a Maven repository, you can use
+the following options:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>contractDependency</code>: The contract dependency that contains all the packaged contracts.</p>
+</li>
+<li>
+<p><code>contractsPath</code>: The path to the concrete contracts in the JAR with packaged contracts.
+Defaults to <code>groupid/artifactid</code> where <code>gropuid</code> is slash separated.</p>
+</li>
+<li>
+<p><code>contractsMode</code>: Picks the mode in which stubs are found and registered.</p>
+</li>
+<li>
+<p><code>deleteStubsAfterTest</code>: If set to <code>false</code> will not remove any downloaded
+contracts from temporary directories.</p>
+</li>
+<li>
+<p><code>contractsRepositoryUrl</code>: URL to a repository with the artifacts that have contracts. If it is not provided,
+use the current Maven ones.</p>
+</li>
+<li>
+<p><code>contractsRepositoryUsername</code>: The user name to be used to connect to the repo with contracts.</p>
+</li>
+<li>
+<p><code>contractsRepositoryPassword</code>: The password to be used to connect to the repo with contracts.</p>
+</li>
+<li>
+<p><code>contractsRepositoryProxyHost</code>: The proxy host to be used to connect to the repo with contracts.</p>
+</li>
+<li>
+<p><code>contractsRepositoryProxyPort</code>: The proxy port to be used to connect to the repo with contracts.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>We cache only non-snapshot, explicitly provided versions (for example
+<code>+</code> or <code>1.0.0.BUILD-SNAPSHOT</code> do not get cached). By default, this feature is turned on.</p>
+</div>
+<div class="paragraph">
+<p>The following list describes experimental features that you can turn on in the plugin:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>convertToYaml</code>: Converts all DSLs to the declarative YAML format. This can be extremely useful when you use external libraries in your Groovy DSLs. By turning this feature on (by setting it to <code>true</code>) you need not add the library dependency on the consumer side.</p>
+</li>
+<li>
+<p><code>assertJsonSize</code>: You can check the size of JSON arrays in the generated tests. This feature is disabled by default.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="maven-single-base"><a class="anchor" href="#maven-single-base"></a><a class="link" href="#maven-single-base">4.8. Single Base Class for All Tests</a></h3>
+<div class="paragraph">
+<p>When using Spring Cloud Contract Verifier in the default (<code>MockMvc</code>), you need to create a base
+specification for all generated acceptance tests. In this class, you need to point to an
+endpoint, which should be verified. The following example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package org.mycompany.tests
+
+import org.mycompany.ExampleSpringController
+import com.jayway.restassured.module.mockmvc.RestAssuredMockMvc
+import spock.lang.Specification
+
+class MvcSpec extends Specification {
+  def setup() {
+   RestAssuredMockMvc.standaloneSetup(new ExampleSpringController())
+  }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You can also setup the whole context if necessary, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import io.restassured.module.mockmvc.RestAssuredMockMvc;
+import org.junit.Before;
+import org.junit.runner.RunWith;
+import org.springframework.beans.factory.annotation.Autowired;
+import org.springframework.boot.test.context.SpringBootTest;
+import org.springframework.test.context.junit4.SpringRunner;
+import org.springframework.web.context.WebApplicationContext;
+
+@RunWith(SpringRunner.class)
+@SpringBootTest(webEnvironment = WebEnvironment.RANDOM_PORT, classes = SomeConfig.class, properties="some=property")
+public abstract class BaseTestClass {
+
+    @Autowired
+    WebApplicationContext context;
+
+    @Before
+    public void setup() {
+        RestAssuredMockMvc.webAppContextSetup(this.context);
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>If you use <code>EXPLICIT</code> mode, you can use a base class to initialize the whole tested app,
+similar to what you might do in regular integration tests. The following example shows
+how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import io.restassured.RestAssured;
+import org.junit.Before;
+import org.junit.runner.RunWith;
+import org.springframework.beans.factory.annotation.Autowired;
+import org.springframework.boot.test.context.SpringBootTest;
+import org.springframework.boot.web.server.LocalServerPort
+import org.springframework.test.context.junit4.SpringRunner;
+import org.springframework.web.context.WebApplicationContext;
+
+@RunWith(SpringRunner.class)
+@SpringBootTest(webEnvironment = WebEnvironment.RANDOM_PORT, classes = SomeConfig.class, properties="some=property")
+public abstract class BaseTestClass {
+
+    @LocalServerPort
+    int port;
+
+    @Before
+    public void setup() {
+        RestAssured.baseURI = "http://localhost:" + this.port;
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>If you use the <code>JAXRSCLIENT</code> mode, this base class should also contain a <code>protected WebTarget webTarget</code> field. Right
+now, the only way to test the JAX-RS API is to start a web server.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="maven-different-base"><a class="anchor" href="#maven-different-base"></a><a class="link" href="#maven-different-base">4.9. Using Different Base Classes for Contracts</a></h3>
+<div class="paragraph">
+<p>If your base classes differ between contracts, you can tell the Spring Cloud Contract
+plugin which class should get extended by the autogenerated tests. You have two options:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Follow a convention by providing a value for <code>packageWithBaseClasses</code></p>
+</li>
+<li>
+<p>Provide explicit mapping with <code>baseClassMappings</code></p>
+</li>
+</ul>
+</div>
+<div class="sect3">
+<h4 id="by-convention"><a class="anchor" href="#by-convention"></a><a class="link" href="#by-convention">4.9.1. By Convention</a></h4>
+<div class="paragraph">
+<p>The convention is such that if you have a contract under (for example)
+<code>src/test/resources/contract/foo/bar/baz/</code> and set the value of the
+<code>packageWithBaseClasses</code> property to <code>com.example.base</code>, then Spring Cloud Contract
+Verifier assumes that there is a <code>BarBazBase</code> class under the <code>com.example.base</code> package.
+In other words, the system takes the last two parts of the package, if they exist, and
+forms a class with a <code>Base</code> suffix. This rule takes precedence over <code>baseClassForTests</code>.
+The following example shows how it works in the <code>contracts</code> closure:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;configuration&gt;
+        &lt;packageWithBaseClasses&gt;hello&lt;/packageWithBaseClasses&gt;
+    &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="by-mapping"><a class="anchor" href="#by-mapping"></a><a class="link" href="#by-mapping">4.9.2. By Mapping</a></h4>
+<div class="paragraph">
+<p>You can manually map a regular expression of the contract&#8217;s package to the fully qualified
+name of the base class for the matched contract. You have to provide a list called
+<code>baseClassMappings</code> that consists of <code>baseClassMapping</code> objects that each take a
+<code>contractPackageRegex</code> to <code>baseClassFQN</code> mapping. Consider the following example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;configuration&gt;
+        &lt;baseClassForTests&gt;com.example.FooBase&lt;/baseClassForTests&gt;
+        &lt;baseClassMappings&gt;
+            &lt;baseClassMapping&gt;
+                &lt;contractPackageRegex&gt;.*com.*&lt;/contractPackageRegex&gt;
+                &lt;baseClassFQN&gt;com.example.TestBase&lt;/baseClassFQN&gt;
+            &lt;/baseClassMapping&gt;
+        &lt;/baseClassMappings&gt;
+    &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Assume that you have contracts under these two locations:
+* <code>src/test/resources/contract/com/</code>
+* <code>src/test/resources/contract/foo/</code></p>
+</div>
+<div class="paragraph">
+<p>By providing the <code>baseClassForTests</code>, we have a fallback in case mapping did not succeed.
+(You can also provide the <code>packageWithBaseClasses</code> as a fallback.) That way, the tests
+generated from <code>src/test/resources/contract/com/</code> contracts extend the
+<code>com.example.ComBase</code>, whereas the rest of the tests extend <code>com.example.FooBase</code>.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="maven-invoking-generated-tests"><a class="anchor" href="#maven-invoking-generated-tests"></a><a class="link" href="#maven-invoking-generated-tests">4.10. Invoking Generated Tests</a></h3>
+<div class="paragraph">
+<p>The Spring Cloud Contract Maven Plugin generates verification code in a directory called
+<code>/generated-test-sources/contractVerifier</code> and attaches this directory to <code>testCompile</code>
+goal.</p>
+</div>
+<div class="paragraph">
+<p>For Groovy Spock code, you can use the following:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.codehaus.gmavenplus&lt;/groupId&gt;
+    &lt;artifactId&gt;gmavenplus-plugin&lt;/artifactId&gt;
+    &lt;version&gt;1.5&lt;/version&gt;
+    &lt;executions&gt;
+        &lt;execution&gt;
+            &lt;goals&gt;
+                &lt;goal&gt;testCompile&lt;/goal&gt;
+            &lt;/goals&gt;
+        &lt;/execution&gt;
+    &lt;/executions&gt;
+    &lt;configuration&gt;
+        &lt;testSources&gt;
+            &lt;testSource&gt;
+                &lt;directory&gt;${project.basedir}/src/test/groovy&lt;/directory&gt;
+                &lt;includes&gt;
+                    &lt;include&gt;**/*.groovy&lt;/include&gt;
+                &lt;/includes&gt;
+            &lt;/testSource&gt;
+            &lt;testSource&gt;
+                &lt;directory&gt;${project.build.directory}/generated-test-sources/contractVerifier&lt;/directory&gt;
+                &lt;includes&gt;
+                    &lt;include&gt;**/*.groovy&lt;/include&gt;
+                &lt;/includes&gt;
+            &lt;/testSource&gt;
+        &lt;/testSources&gt;
+    &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>To ensure that the provider side is compliant with defined contracts, you need to invoke
+<code>mvn generateTest test</code>.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="maven-pushing-stubs-to-scm"><a class="anchor" href="#maven-pushing-stubs-to-scm"></a><a class="link" href="#maven-pushing-stubs-to-scm">4.11. Pushing Stubs to SCM</a></h3>
+<div class="paragraph">
+<p>If you use the SCM (Source Control Management) repository to keep the contracts and
+stubs, you might want to automate the step of pushing stubs to
+the repository. To do that, you can add the <code>pushStubsToScm</code>
+goal. The following example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;!-- Base class mappings etc. --&gt;
+
+        &lt;!-- We want to pick contracts from a Git repository --&gt;
+        &lt;contractsRepositoryUrl&gt;git://https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git&lt;/contractsRepositoryUrl&gt;
+
+        &lt;!-- We reuse the contract dependency section to set up the path
+        to the folder that contains the contract definitions. In our case the
+        path will be /groupId/artifactId/version/contracts --&gt;
+        &lt;contractDependency&gt;
+            &lt;groupId&gt;${project.groupId}&lt;/groupId&gt;
+            &lt;artifactId&gt;${project.artifactId}&lt;/artifactId&gt;
+            &lt;version&gt;${project.version}&lt;/version&gt;
+        &lt;/contractDependency&gt;
+
+        &lt;!-- The contracts mode can't be classpath --&gt;
+        &lt;contractsMode&gt;REMOTE&lt;/contractsMode&gt;
+    &lt;/configuration&gt;
+    &lt;executions&gt;
+        &lt;execution&gt;
+            &lt;phase&gt;package&lt;/phase&gt;
+            &lt;goals&gt;
+                &lt;!-- By default we will not push the stubs back to SCM,
+                you have to explicitly add it as a goal --&gt;
+                &lt;goal&gt;pushStubsToScm&lt;/goal&gt;
+            &lt;/goals&gt;
+        &lt;/execution&gt;
+    &lt;/executions&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Under <a href="#scm-stub-downloader">Using the SCM Stub Downloader</a>, you can find all possible
+configuration options that you can pass through
+the <code>&lt;configuration&gt;&lt;contractProperties&gt;</code> map, a system property,
+or an environment variable.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="maven-sts"><a class="anchor" href="#maven-sts"></a><a class="link" href="#maven-sts">4.12. Maven Plugin and STS</a></h3>
+<div class="paragraph">
+<p>The following image shows an exception that you may see when you use STS:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="https://raw.githubusercontent.com/spring-cloud/spring-cloud-contract/master/docs/src/main/asciidoc/images/sts_exception.png" alt="STS Exception">
+</div>
+</div>
+<div class="paragraph">
+<p>When you click on the error marker you should see something like the following:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash"> plugin:1.1.0.M1:convert:default-convert:process-test-resources) org.apache.maven.plugin.PluginExecutionException: Execution default-convert of goal org.springframework.cloud:spring-
+ cloud-contract-maven-plugin:1.1.0.M1:convert failed. at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145) at
+ org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331) at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362) at
+...
+ org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.lang.NullPointerException at
+ org.eclipse.m2e.core.internal.builder.plexusbuildapi.EclipseIncrementalBuildContext.hasDelta(EclipseIncrementalBuildContext.java:53) at
+ org.sonatype.plexus.build.incremental.ThreadBuildContext.hasDelta(ThreadBuildContext.java:59) at</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>In order to fix this issue, provide the following section in your <code>pom.xml</code>:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;build&gt;
+    &lt;pluginManagement&gt;
+        &lt;plugins&gt;
+            &lt;!--This plugin's configuration is used to store Eclipse m2e settings
+                only. It has no influence on the Maven build itself. --&gt;
+            &lt;plugin&gt;
+                &lt;groupId&gt;org.eclipse.m2e&lt;/groupId&gt;
+                &lt;artifactId&gt;lifecycle-mapping&lt;/artifactId&gt;
+                &lt;version&gt;1.0.0&lt;/version&gt;
+                &lt;configuration&gt;
+                    &lt;lifecycleMappingMetadata&gt;
+                        &lt;pluginExecutions&gt;
+                             &lt;pluginExecution&gt;
+                                &lt;pluginExecutionFilter&gt;
+                                    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+                                    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+                                    &lt;versionRange&gt;[1.0,)&lt;/versionRange&gt;
+                                    &lt;goals&gt;
+                                        &lt;goal&gt;convert&lt;/goal&gt;
+                                    &lt;/goals&gt;
+                                &lt;/pluginExecutionFilter&gt;
+                                &lt;action&gt;
+                                    &lt;execute /&gt;
+                                &lt;/action&gt;
+                             &lt;/pluginExecution&gt;
+                        &lt;/pluginExecutions&gt;
+                    &lt;/lifecycleMappingMetadata&gt;
+                &lt;/configuration&gt;
+            &lt;/plugin&gt;
+        &lt;/plugins&gt;
+    &lt;/pluginManagement&gt;
+&lt;/build&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="maven-plugin-with-spock-tests"><a class="anchor" href="#maven-plugin-with-spock-tests"></a><a class="link" href="#maven-plugin-with-spock-tests">4.13. Maven Plugin with Spock Tests</a></h3>
+<div class="paragraph">
+<p>You can select the <a href="http://spockframework.org/">Spock Framework</a> for creating and running the auto-generated contract
+verification tests with both Maven and Gradle. However, whereas using Gradle is straightforward,
+in Maven, you will require some additional setup in order to make the tests compile and execute properly.</p>
+</div>
+<div class="paragraph">
+<p>First of all, you must use a plugin, such as the <a href="https://github.com/groovy/GMavenPlus">GMavenPlus</a> plugin,
+to add Groovy to your project. In GMavenPlus plugin, you need to explicitly set test sources, including both the
+path where your base test classes are defined and the path were the generated contract tests are added.
+The following example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.codehaus.gmavenplus&lt;/groupId&gt;
+    &lt;artifactId&gt;gmavenplus-plugin&lt;/artifactId&gt;
+    &lt;version&gt;1.6.1&lt;/version&gt;
+    &lt;executions&gt;
+        &lt;execution&gt;
+            &lt;goals&gt;
+                &lt;goal&gt;compileTests&lt;/goal&gt;
+                &lt;goal&gt;addTestSources&lt;/goal&gt;
+            &lt;/goals&gt;
+        &lt;/execution&gt;
+    &lt;/executions&gt;
+    &lt;configuration&gt;
+        &lt;testSources&gt;
+            &lt;testSource&gt;
+                &lt;directory&gt;${project.basedir}/src/test/groovy&lt;/directory&gt;
+                &lt;includes&gt;
+                    &lt;include&gt;**/*.groovy&lt;/include&gt;
+                &lt;/includes&gt;
+            &lt;/testSource&gt;
+            &lt;testSource&gt;
+                &lt;directory&gt;
+                    ${project.basedir}/target/generated-test-sources/contracts/com/example/beer
+                &lt;/directory&gt;
+                &lt;includes&gt;
+                    &lt;include&gt;**/*.groovy&lt;/include&gt;
+                    &lt;include&gt;**/*.gvy&lt;/include&gt;
+                &lt;/includes&gt;
+            &lt;/testSource&gt;
+        &lt;/testSources&gt;
+    &lt;/configuration&gt;
+    &lt;dependencies&gt;
+        &lt;dependency&gt;
+            &lt;groupId&gt;org.codehaus.groovy&lt;/groupId&gt;
+            &lt;artifactId&gt;groovy-all&lt;/artifactId&gt;
+            &lt;version&gt;${groovy.version}&lt;/version&gt;
+            &lt;scope&gt;runtime&lt;/scope&gt;
+            &lt;type&gt;pom&lt;/type&gt;
+        &lt;/dependency&gt;
+    &lt;/dependencies&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>If you uphold the Spock convention of ending the test class names with <code>Spec</code>, you also need to adjust your Maven
+Surefire plugin setup, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
+    &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
+    &lt;configuration&gt;
+        &lt;includes&gt;
+            &lt;include&gt;**/*Test.java&lt;/include&gt;
+            &lt;include&gt;**/*Spec.java&lt;/include&gt;
+        &lt;/includes&gt;
+        &lt;failIfNoTests&gt;true&lt;/failIfNoTests&gt;
+    &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="gradle-project"><a class="anchor" href="#gradle-project"></a><a class="link" href="#gradle-project">5. Gradle Project</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>To learn how to set up the Gradle project for Spring Cloud Contract Verifier, read the
+following sections:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="#gradle-prerequisites">Prerequisites</a></p>
+</li>
+<li>
+<p><a href="#gradle-add-gradle-plugin">Add Gradle Plugin with Dependencies</a></p>
+</li>
+<li>
+<p><a href="#gradle-and-rest-assured">Gradle and Rest Assured 2.0</a></p>
+</li>
+<li>
+<p><a href="#gradle-snapshot-versions">Snapshot Versions for Gradle</a></p>
+</li>
+<li>
+<p><a href="#gradle-add-stubs">Add stubs</a></p>
+</li>
+<li>
+<p><a href="#gradle-default-setup">Default Setup</a></p>
+</li>
+<li>
+<p><a href="#gradle-configure-plugin">Configuring the Plugin</a></p>
+</li>
+<li>
+<p><a href="#gradle-configuration-options">Configuration Options</a></p>
+</li>
+<li>
+<p><a href="#gradle-single-base-class">Single Base Class for All Tests</a></p>
+</li>
+<li>
+<p><a href="#gradle-different-base-classes">Different Base Classes for Contracts</a></p>
+</li>
+<li>
+<p><a href="#gradle-invoking-generated-tests">Invoking Generated Tests</a></p>
+</li>
+<li>
+<p><a href="#gradle-pushing-stubs-to-scm">Pushing Stubs to SCM</a></p>
+</li>
+<li>
+<p><a href="#gradle-consumer">Spring Cloud Contract Verifier on the Consumer Side</a></p>
+</li>
+</ul>
+</div>
+<div class="sect2">
+<h3 id="gradle-prerequisites"><a class="anchor" href="#gradle-prerequisites"></a><a class="link" href="#gradle-prerequisites">5.1. Prerequisites</a></h3>
+<div class="paragraph">
+<p>In order to use Spring Cloud Contract Verifier with WireMock, you must use either a
+Gradle or a Maven plugin.</p>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-warning" title="Warning"></i>
+</td>
+<td class="content">
+If you want to use Spock in your projects, you must separately add the
+<code>spock-core</code> and <code>spock-spring</code> modules. See <a href="https://spockframework.github.io/">Spock&#8217;s
+documnetation for more information</a>
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gradle-add-gradle-plugin"><a class="anchor" href="#gradle-add-gradle-plugin"></a><a class="link" href="#gradle-add-gradle-plugin">5.2. Add Gradle Plugin with Dependencies</a></h3>
+<div class="paragraph">
+<p>To add a Gradle plugin with dependencies, you can use code similar to the following:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Plugin DSL GA versions</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">// build.gradle
+plugins {
+  id "groovy"
+  // this will work only for GA versions of Spring Cloud Contract
+  id "org.springframework.cloud.contract" version "${GAVerifierVersion}"
+}
+
+dependencyManagement {
+    imports {
+        mavenBom "org.springframework.cloud:spring-cloud-contract-dependencies:${GAVerifierVersion}"
+    }
+}
+
+dependencies {
+    testCompile "org.codehaus.groovy:groovy-all:${groovyVersion}"
+    // example with adding Spock core and Spock Spring
+    testCompile "org.spockframework:spock-core:${spockVersion}"
+    testCompile "org.spockframework:spock-spring:${spockVersion}"
+    testCompile 'org.springframework.cloud:spring-cloud-starter-contract-verifier'
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Plugin DSL non GA versions</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">// settings.gradle
+pluginManagement {
+    plugins {
+        id "org.springframework.cloud.contract" version "${verifierVersion}"
+    }
+    repositories {
+        // to pick from local .m2
+        mavenLocal()
+        // for snapshots
+        maven { url "https://repo.spring.io/snapshot" }
+        // for milestones
+        maven { url "https://repo.spring.io/milestone" }
+        // for GA versions
+        gradlePluginPortal()
+    }
+}
+
+// build.gradle
+plugins {
+  id "groovy"
+  id "org.springframework.cloud.contract"
+}
+
+dependencyManagement {
+    imports {
+        mavenBom "org.springframework.cloud:spring-cloud-contract-dependencies:${verifierVersion}"
+    }
+}
+
+dependencies {
+    testCompile "org.codehaus.groovy:groovy-all:${groovyVersion}"
+    // example with adding Spock core and Spock Spring
+    testCompile "org.spockframework:spock-core:${spockVersion}"
+    testCompile "org.spockframework:spock-spring:${spockVersion}"
+    testCompile 'org.springframework.cloud:spring-cloud-starter-contract-verifier'
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Legacy Plugin Application</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">// build.gradle
+buildscript {
+    repositories {
+        mavenCentral()
+    }
+    dependencies {
+        classpath "org.springframework.boot:spring-boot-gradle-plugin:${springboot_version}"
+        classpath "org.springframework.cloud:spring-cloud-contract-gradle-plugin:${verifier_version}"
+        // here you can also pass additional dependencies such as Pact or Kotlin spec e.g.:
+        // classpath "org.springframework.cloud:spring-cloud-contract-spec-kotlin:${verifier_version}"
+    }
+}
+
+apply plugin: 'groovy'
+apply plugin: 'spring-cloud-contract'
+
+dependencyManagement {
+    imports {
+        mavenBom "org.springframework.cloud:spring-cloud-contract-dependencies:${verifier_version}"
+    }
+}
+
+dependencies {
+    testCompile "org.codehaus.groovy:groovy-all:${groovyVersion}"
+    // example with adding Spock core and Spock Spring
+    testCompile "org.spockframework:spock-core:${spockVersion}"
+    testCompile "org.spockframework:spock-spring:${spockVersion}"
+    testCompile 'org.springframework.cloud:spring-cloud-starter-contract-verifier'
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gradle-and-rest-assured"><a class="anchor" href="#gradle-and-rest-assured"></a><a class="link" href="#gradle-and-rest-assured">5.3. Gradle and Rest Assured 2.0</a></h3>
+<div class="paragraph">
+<p>By default, Rest Assured 3.x is added to the classpath. However, to use Rest Assured 2.x
+you can add it to the plugins classpath, as the following listing shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">buildscript {
+    repositories {
+        mavenCentral()
+    }
+    dependencies {
+        classpath "org.springframework.boot:spring-boot-gradle-plugin:${springboot_version}"
+        classpath "org.springframework.cloud:spring-cloud-contract-gradle-plugin:${verifier_version}"
+        classpath "com.jayway.restassured:rest-assured:2.5.0"
+        classpath "com.jayway.restassured:spring-mock-mvc:2.5.0"
+    }
+}
+
+depenendencies {
+    // all dependencies
+    // you can exclude rest-assured from spring-cloud-contract-verifier
+    testCompile "com.jayway.restassured:rest-assured:2.5.0"
+    testCompile "com.jayway.restassured:spring-mock-mvc:2.5.0"
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>That way, the plugin automatically sees that Rest Assured 2.x is present on the classpath
+and modifies the imports accordingly.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gradle-snapshot-versions"><a class="anchor" href="#gradle-snapshot-versions"></a><a class="link" href="#gradle-snapshot-versions">5.4. Snapshot Versions for Gradle</a></h3>
+<div class="paragraph">
+<p>You can add the additional snapshot repository to your <code>build.gradle</code> to use snapshot versions,
+which are automatically uploaded after every successful build, as the following listing shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">/*
+ We need to use the [buildscript {}] section when we have to modify
+ the classpath for the plugins. If that's not the case this section
+ can be skipped.
+
+ If you don't need to modify the classpath (e.g. add a Pact dependency),
+ then you can just set the [pluginManagement {}] section in [settings.gradle] file.
+
+ // settings.gradle
+ pluginManagement {
+    repositories {
+        // for snapshots
+        maven {url "https://repo.spring.io/snapshot"}
+        // for milestones
+        maven {url "https://repo.spring.io/milestone"}
+        // for GA versions
+        gradlePluginPortal()
+    }
+ }
+
+ */
+buildscript {
+    repositories {
+        mavenCentral()
+        mavenLocal()
+        maven { url "https://repo.spring.io/snapshot" }
+        maven { url "https://repo.spring.io/milestone" }
+        maven { url "https://repo.spring.io/release" }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gradle-add-stubs"><a class="anchor" href="#gradle-add-stubs"></a><a class="link" href="#gradle-add-stubs">5.5. Add stubs</a></h3>
+<div class="paragraph">
+<p>By default, Spring Cloud Contract Verifier looks for stubs in the
+<code>src/test/resources/contracts</code> directory.</p>
+</div>
+<div class="paragraph">
+<p>The directory that contains stub definitions is treated as a class name, and each stub
+definition is treated as a single test. Spring Cloud Contract Verifier assumes that it
+contains at  least one level of directories that are to be used as the test class name.
+If more than  one level of nested directories is present, all except the last one is used
+as the package name. Consider the following structure:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">src/test/resources/contracts/myservice/shouldCreateUser.groovy
+src/test/resources/contracts/myservice/shouldReturnUser.groovy</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Given the preceding structure, Spring Cloud Contract Verifier creates a test class named
+<code>defaultBasePackage.MyService</code> with two methods:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>shouldCreateUser()</code></p>
+</li>
+<li>
+<p><code>shouldReturnUser()</code></p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gradle-run-plugin"><a class="anchor" href="#gradle-run-plugin"></a><a class="link" href="#gradle-run-plugin">5.6. Running the Plugin</a></h3>
+<div class="paragraph">
+<p>The plugin registers itself to be invoked before a <code>check</code> task. If you want it to be
+part of your build process, you need do nothing more. If you just want to generate
+tests, invoke the <code>generateContractTests</code> task.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gradle-default-setup"><a class="anchor" href="#gradle-default-setup"></a><a class="link" href="#gradle-default-setup">5.7. Default Setup</a></h3>
+<div class="paragraph">
+<p>The default Gradle Plugin setup creates the following Gradle part of the build (in
+pseudocode):</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
+    testFramework ='JUNIT'
+    testMode = 'MockMvc'
+    generatedTestSourcesDir = project.file("${project.buildDir}/generated-test-sources/contracts")
+    generatedTestResourcesDir = project.file("${project.buildDir}/generated-test-resources/contracts")
+    contractsDslDir = project.file("${project.rootDir}/src/test/resources/contracts")
+    basePackageForTests = 'org.springframework.cloud.verifier.tests'
+    stubsOutputDir = project.file("${project.buildDir}/stubs")
+    sourceSet = null
+
+    // the following properties are used when you want to provide where the JAR with contract lays
+    contractDependency {
+        stringNotation = ''
+    }
+    contractsPath = ''
+    contractsWorkOffline = false
+    contractRepository {
+        cacheDownloadedContracts(true)
+    }
+}
+
+tasks.create(type: Jar, name: 'verifierStubsJar', dependsOn: 'generateClientStubs') {
+    baseName = project.name
+    classifier = contracts.stubsSuffix
+    from contractVerifier.stubsOutputDir
+}
+
+project.artifacts {
+    archives task
+}
+
+tasks.create(type: Copy, name: 'copyContracts') {
+    from contracts.contractsDslDir
+    into contracts.stubsOutputDir
+}
+
+verifierStubsJar.dependsOn 'copyContracts'
+
+publishing {
+    publications {
+        stubs(MavenPublication) {
+            artifactId project.name
+            artifact verifierStubsJar
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gradle-configure-plugin"><a class="anchor" href="#gradle-configure-plugin"></a><a class="link" href="#gradle-configure-plugin">5.8. Configuring the Plugin</a></h3>
+<div class="paragraph">
+<p>To change the default configuration, you can add a <code>contracts</code> snippet to your Gradle
+configuration, as the following listing shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
+    testMode = 'MockMvc'
+    baseClassForTests = 'org.mycompany.tests'
+    generatedTestSourcesDir = project.file('src/generatedContract')
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gradle-configuration-options"><a class="anchor" href="#gradle-configuration-options"></a><a class="link" href="#gradle-configuration-options">5.9. Configuration Options</a></h3>
+<div class="ulist">
+<ul>
+<li>
+<p><code>testMode</code>: Defines the mode for acceptance tests. By default, the mode is MockMvc,
+which is based on Spring&#8217;s MockMvc. It can also be changed to WebTestClient, JaxRsClient, or
+Explicit (for real HTTP calls).</p>
+</li>
+<li>
+<p><code>imports</code>: Creates an array with imports that should be included in the generated tests
+(for example, <code>['org.myorg.Matchers']</code>). By default, it creates an empty array.</p>
+</li>
+<li>
+<p><code>staticImports</code>: Creates an array with static imports that should be included in
+generated tests(for example, <code>['org.myorg.Matchers.*']</code>). By default, it creates an empty
+array.</p>
+</li>
+<li>
+<p><code>basePackageForTests</code>: Specifies the base package for all generated tests. If not set,
+the value is picked from the package of <code>baseClassForTests</code> and from <code>packageWithBaseClasses</code>.
+If neither of these values are set, the value is set to
+<code>org.springframework.cloud.contract.verifier.tests</code>.</p>
+</li>
+<li>
+<p><code>baseClassForTests</code>: Creates a base class for all generated tests. By default, if you
+use Spock classes, the class is <code>spock.lang.Specification</code>.</p>
+</li>
+<li>
+<p><code>packageWithBaseClasses</code>: Defines a package where all the base classes reside. This
+setting takes precedence over <code>baseClassForTests</code>.</p>
+</li>
+<li>
+<p><code>baseClassMappings</code>: Explicitly maps a contract package to a FQN of a base class. This
+setting takes precedence over <code>packageWithBaseClasses</code> and <code>baseClassForTests</code>.</p>
+</li>
+<li>
+<p><code>ruleClassForTests</code>: Specifies a rule that should be added to the generated test
+classes.</p>
+</li>
+<li>
+<p><code>ignoredFiles</code>: Uses an <code>Antmatcher</code> to allow defining stub files for which processing
+should be skipped. By default, it is an empty array.</p>
+</li>
+<li>
+<p><code>contractsDslDir</code>: Specifies the directory that contains contracts written by using the
+GroovyDSL. By default, its value is <code>$rootDir/src/test/resources/contracts</code>.</p>
+</li>
+<li>
+<p><code>generatedTestSourcesDir</code>: Specifies the test source directory where tests generated
+from the Groovy DSL should be placed. By default, its value is
+<code>$buildDir/generated-test-sources/contracts</code>.</p>
+</li>
+<li>
+<p><code>generatedTestResourcesDir</code>: Specifies the test resource directory where resources used by the tests generated
+from the Groovy DSL should be placed. By default, its value is
+<code>$buildDir/generated-test-resources/contracts</code>.</p>
+</li>
+<li>
+<p><code>stubsOutputDir</code>: Specifies the directory where the generated WireMock stubs from
+the Groovy DSL should be placed.</p>
+</li>
+<li>
+<p><code>testFramework</code>: Specifies the target test framework to be used. Currently, Spock, JUnit 4 (<code>TestFramework.JUNIT</code>), and
+JUnit 5 are supported, with JUnit 4 being the default framework.</p>
+</li>
+<li>
+<p><code>contractsProperties</code>: A map that contains properties to be passed to Spring Cloud Contract
+components. Those properties might be used by (for example) built-in or custom Stub Downloaders.</p>
+</li>
+<li>
+<p><code>sourceSet</code>: Source set where the contracts are stored. If not provided will assume <code>test</code> (e.g. <code>project.sourceSets.test.java</code> for JUnit or <code>project.sourceSets.test.groovy</code> for Spock).</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>You can use the following properties when you want to specify the location of the JAR
+that contains the contracts:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>contractDependency</code>: Specifies the Dependency that provides
+<code>groupid:artifactid:version:classifier</code> coordinates. You can use the <code>contractDependency</code>
+closure to set it up.</p>
+</li>
+<li>
+<p><code>contractsPath</code>: Specifies the path to the jar. If contract dependencies are
+downloaded, the path defaults to <code>groupid/artifactid</code> where <code>groupid</code> is slash
+separated. Otherwise, it scans contracts under the provided directory.</p>
+</li>
+<li>
+<p><code>contractsMode</code>: Specifies the mode for downloading contracts (whether the
+JAR is available offline, remotely, and so on).</p>
+</li>
+<li>
+<p><code>deleteStubsAfterTest</code>: If set to <code>false</code>, do not remove any downloaded
+contracts from temporary directories.</p>
+</li>
+<li>
+<p><code>failOnNoContracts</code>: When enabled, will throw an exception when no contracts were found. Defaults to <code>true</code>.</p>
+</li>
+<li>
+<p><code>failOnInProgress</code>: If set to true then if any contracts that are in progress are found, will break the build. On the producer side you need to be explicit about the fact that you have contracts in progress and take into consideration that you might be causing false positive test execution results on the consumer side.. Defaults to <code>true</code>.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>There is also the <code>contractRepository { &#8230;&#8203; }</code> closure that contains the following properties</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>repositoryUrl</code>: the URL to the repository with contract definitions</p>
+</li>
+<li>
+<p><code>username</code> : Repository username</p>
+</li>
+<li>
+<p><code>password</code> : Repository password</p>
+</li>
+<li>
+<p><code>proxyPort</code> : the port of the proxy</p>
+</li>
+<li>
+<p><code>proxyHost</code> : the host of the proxy</p>
+</li>
+<li>
+<p><code>cacheDownloadedContracts</code> : If set to <code>true</code> then will cache the folder where non snapshot contract artifacts got downloaded. Defaults to <code>true</code>.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>You can also turn on the following experimental features in the plugin:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>convertToYaml</code>: Converts all DSLs to the declarative YAML format. This can be extremely
+useful when you use external libraries in your Groovy DSLs. By turning this feature on
+(by setting it to <code>true</code>) you need not add the library dependency on the consumer side.</p>
+</li>
+<li>
+<p><code>assertJsonSize</code>: You can check the size of JSON arrays in the generated tests. This
+feature is disabled by default.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gradle-single-base-class"><a class="anchor" href="#gradle-single-base-class"></a><a class="link" href="#gradle-single-base-class">5.10. Single Base Class for All Tests</a></h3>
+<div class="paragraph">
+<p>When using Spring Cloud Contract Verifier in default MockMvc, you need to create a base
+specification for all generated acceptance tests. In this class, you need to point to an
+endpoint, which should be verified. The following example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">abstract class BaseMockMvcSpec extends Specification {
+
+    def setup() {
+        RestAssuredMockMvc.standaloneSetup(new PairIdController())
+    }
+
+    void isProperCorrelationId(Integer correlationId) {
+        assert correlationId == 123456
+    }
+
+    void isEmpty(String value) {
+        assert value == null
+    }
+
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>If you use <code>Explicit</code> mode, you can use a base class to initialize the whole tested application,
+as you might see in regular integration tests. If you use the <code>JAXRSCLIENT</code> mode, this
+base class should also contain a <code>protected WebTarget webTarget</code> field. Right now, the
+only option to test the JAX-RS API is to start a web server.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gradle-different-base-classes"><a class="anchor" href="#gradle-different-base-classes"></a><a class="link" href="#gradle-different-base-classes">5.11. Different Base Classes for Contracts</a></h3>
+<div class="paragraph">
+<p>If your base classes differ between contracts, you can tell the Spring Cloud Contract
+plugin which class should get extended by the autogenerated tests. You have two options:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Follow a convention by providing the <code>packageWithBaseClasses</code></p>
+</li>
+<li>
+<p>Provide explicit mapping by using <code>baseClassMappings</code></p>
+</li>
+</ul>
+</div>
+<div class="sect3">
+<h4 id="by-convention-2"><a class="anchor" href="#by-convention-2"></a><a class="link" href="#by-convention-2">5.11.1. By Convention</a></h4>
+<div class="paragraph">
+<p>The convention is such that if you have a contract in (for example)
+<code>src/test/resources/contract/foo/bar/baz/</code> and set the value of the
+<code>packageWithBaseClasses</code> property to <code>com.example.base</code>, then Spring Cloud Contract
+Verifier assumes that there is a <code>BarBazBase</code> class under the <code>com.example.base</code> package.
+In other words, the system takes the last two parts of the package, if they exist, and
+forms a class with a <code>Base</code> suffix. This rule takes precedence over <code>baseClassForTests</code>.
+The following example shows how it works in the <code>contracts</code> closure:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">packageWithBaseClasses = 'com.example.base'</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="by-mapping-2"><a class="anchor" href="#by-mapping-2"></a><a class="link" href="#by-mapping-2">5.11.2. By Mapping</a></h4>
+<div class="paragraph">
+<p>You can manually map a regular expression of the contract&#8217;s package to the fully qualified
+name of the base class for the matched contract. You have to provide a list called
+<code>baseClassMappings</code> that consists of <code>baseClassMapping</code> objects that take a
+<code>contractPackageRegex</code> to <code>baseClassFQN</code> mapping. Consider the following example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">baseClassForTests = "com.example.FooBase"
+baseClassMappings {
+    baseClassMapping('.*/com/.*', 'com.example.ComBase')
+    baseClassMapping('.*/bar/.*': 'com.example.BarBase')
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Let&#8217;s assume that you have contracts in the following directories:
+ - <code>src/test/resources/contract/com/</code>
+ - <code>src/test/resources/contract/foo/</code></p>
+</div>
+<div class="paragraph">
+<p>By providing <code>baseClassForTests</code>, we have a fallback in case mapping did not succeed.
+(You could also provide the <code>packageWithBaseClasses</code> as a fallback.) That way, the tests
+generated from <code>src/test/resources/contract/com/</code> contracts extend the
+<code>com.example.ComBase</code>, whereas the rest of the tests extend <code>com.example.FooBase</code>.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gradle-invoking-generated-tests"><a class="anchor" href="#gradle-invoking-generated-tests"></a><a class="link" href="#gradle-invoking-generated-tests">5.12. Invoking Generated Tests</a></h3>
+<div class="paragraph">
+<p>To ensure that the provider side is compliant with your defined contracts, you need to run
+the following command:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">./gradlew generateContractTests test</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gradle-pushing-stubs-to-scm"><a class="anchor" href="#gradle-pushing-stubs-to-scm"></a><a class="link" href="#gradle-pushing-stubs-to-scm">5.13. Pushing Stubs to SCM</a></h3>
+<div class="paragraph">
+<p>If you use the SCM repository to keep the contracts and
+stubs, you might want to automate the step of pushing stubs to
+the repository. To do that, you can call the <code>pushStubsToScm</code>
+task by running the following command:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ ./gradlew pushStubsToScm</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Under <a href="#scm-stub-downloader">Using the SCM Stub Downloader</a> you can find all possible
+configuration options that you can pass either through
+the <code>contractsProperties</code> field (for example, <code>contracts { contractsProperties = [foo:"bar"] }</code>),
+through the <code>contractsProperties</code> method (for example, <code>contracts { contractsProperties([foo:"bar"]) }</code>),
+or through a system property or an environment variable.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="gradle-consumer"><a class="anchor" href="#gradle-consumer"></a><a class="link" href="#gradle-consumer">5.14. Spring Cloud Contract Verifier on the Consumer Side</a></h3>
+<div class="paragraph">
+<p>In a consuming service, you need to configure the Spring Cloud Contract Verifier plugin
+in exactly the same way as in the case of a provider. If you do not want to use Stub Runner,
+you need to copy the contracts stored in <code>src/test/resources/contracts</code> and generate
+WireMock JSON stubs by using the following command:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">./gradlew generateClientStubs</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+The <code>stubsOutputDir</code> option has to be set for stub generation to work.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>When present, JSON stubs can be used in automated tests to consume a service. The
+following example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">@ContextConfiguration(loader == SpringApplicationContextLoader, classes == Application)
+class LoanApplicationServiceSpec extends Specification {
+
+ @ClassRule
+ @Shared
+ WireMockClassRule wireMockRule == new WireMockClassRule()
+
+ @Autowired
+ LoanApplicationService sut
+
+ def 'should successfully apply for loan'() {
+   given:
+    LoanApplication application =
+            new LoanApplication(client: new Client(clientPesel: '12345678901'), amount: 123.123)
+   when:
+    LoanApplicationResult loanApplication == sut.loanApplication(application)
+   then:
+    loanApplication.loanApplicationStatus == LoanApplicationStatus.LOAN_APPLIED
+    loanApplication.rejectionReason == null
+ }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>In the preceding example, <code>LoanApplication</code> makes a call to the <code>FraudDetection</code> service.
+This request is handled by a WireMock server configured with stubs that were generated by
+Spring Cloud Contract Verifier.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="docker"><a class="anchor" href="#docker"></a><a class="link" href="#docker">6. Docker Project</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>In this section, we publish a <code>springcloud/spring-cloud-contract</code> Docker image
+that contains a project that generates tests and runs them in <code>EXPLICIT</code> mode
+against a running application.</p>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+The <code>EXPLICIT</code> mode means that the tests generated from contracts send
+real requests and not the mocked ones.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>We also publish a <code>spring-cloud/spring-cloud-contract-stub-runner</code> Docker image
+that starts the standalone version of Stub Runner.</p>
+</div>
+<div class="sect2">
+<h3 id="docker-intro"><a class="anchor" href="#docker-intro"></a><a class="link" href="#docker-intro">6.1. A Short Introduction to Maven, JARs and Binary storage</a></h3>
+<div class="paragraph">
+<p>Since non-JVM projects can use the Docker image, it is good to
+explain the basic terms behind Spring Cloud Contract packaging defaults.</p>
+</div>
+<div class="paragraph">
+<p>Parts of the following definitions were taken from the <a href="https://maven.apache.org/glossary.html">Maven Glossary</a>:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>Project</code>: Maven thinks in terms of projects. Projects
+are all you build. Those projects follow a well defined
+“Project Object Model”. Projects can depend on other projects,
+in which case the latter are called “dependencies”. A project may
+consistent of several subprojects. However, these subprojects are still
+treated equally as projects.</p>
+</li>
+<li>
+<p><code>Artifact</code>: An artifact is something that is either produced or used
+by a project. Examples of artifacts produced by Maven for a project
+include JAR files and source and binary distributions. Each artifact
+is uniquely identified by a group ID and an artifact ID that is
+unique within a group.</p>
+</li>
+<li>
+<p><code>JAR</code>: JAR stands for Java ARchive. Its format is based on
+the ZIP file format. Spring Cloud Contract packages the contracts and generated
+stubs in a JAR file.</p>
+</li>
+<li>
+<p><code>GroupId</code>: A group ID is a universally unique identifier for a project.
+While this is often just the project name (for example, <code>commons-collections</code>),
+it is helpful to use a fully-qualified package name to distinguish it
+from other projects with a similar name (for example, <code>org.apache.maven</code>).
+Typically, when published to the Artifact Manager, the <code>GroupId</code> gets
+slash separated and forms part of the URL. For example, for a group ID of <code>com.example</code>
+and an artifact ID of <code>application</code>, the result would be <code>/com/example/application/</code>.</p>
+</li>
+<li>
+<p><code>Classifier</code>: The Maven dependency notation looks as follows:
+<code>groupId:artifactId:version:classifier</code>. The classifier is an additional suffix
+passed to the dependency&#8201;&#8212;&#8201;for example, <code>stubs</code> or <code>sources</code>. The same dependency
+(for example, <code>com.example:application</code>) can produce multiple artifacts that
+differ from each other with the classifier.</p>
+</li>
+<li>
+<p><code>Artifact manager</code>: When you generate binaries, sources, or packages, you would
+like them to be available for others to download, reference, or reuse. In the case
+of the JVM world, those artifacts are generally JARs. For Ruby, those artifacts are gems.
+For Docker, those artifacts are Docker images. You can store those artifacts
+in a manager. Examples of such managers include <a href="https://jfrog.com/artifactory/">Artifactory</a>
+or <a href="https://www.sonatype.org/nexus/">Nexus</a>.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="docker-how-it-works"><a class="anchor" href="#docker-how-it-works"></a><a class="link" href="#docker-how-it-works">6.2. Generating Tests on the Producer Side</a></h3>
+<div class="paragraph">
+<p>The image searches for contracts under the <code>/contracts</code> folder.
+The output from running the tests is available in the
+<code>/spring-cloud-contract/build</code> folder (useful for debugging
+purposes).</p>
+</div>
+<div class="paragraph">
+<p>You can mount your contracts and pass the environment variables.
+The image then:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Generates the contract tests</p>
+</li>
+<li>
+<p>Runs the tests against the provided URL</p>
+</li>
+<li>
+<p>Generates the <a href="https://github.com/tomakehurst/wiremock">WireMock</a> stubs</p>
+</li>
+<li>
+<p>Publishes the stubs to a Artifact Manager (optional - turned on by default)</p>
+</li>
+</ul>
+</div>
+<div class="sect3">
+<h4 id="docker-env-vars"><a class="anchor" href="#docker-env-vars"></a><a class="link" href="#docker-env-vars">6.2.1. Environment Variables</a></h4>
+<div class="paragraph">
+<p>The Docker image requires some environment variables to point to
+your running application, to the Artifact manager instance, and so on.
+The following list describes the environment variables:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>PROJECT_GROUP</code>: Your project&#8217;s group ID. Defaults to <code>com.example</code>.</p>
+</li>
+<li>
+<p><code>PROJECT_VERSION</code>: Your project&#8217;s version. Defaults to <code>0.0.1-SNAPSHOT</code>.</p>
+</li>
+<li>
+<p><code>PROJECT_NAME</code>: Your project&#8217;s artifact id. Defaults to <code>example</code>.</p>
+</li>
+<li>
+<p><code>PRODUCER_STUBS_CLASSIFIER</code>: Archive classifier used for generated producer stubs. Defaults to <code>stubs</code>.</p>
+</li>
+<li>
+<p><code>REPO_WITH_BINARIES_URL</code>: URL of your Artifact Manager. Defaults to <code><a href="http://localhost:8081/artifactory/libs-release-local" class="bare">localhost:8081/artifactory/libs-release-local</a></code>,
+which is the default URL of <a href="https://jfrog.com/artifactory/">Artifactory</a> running locally.</p>
+</li>
+<li>
+<p><code>REPO_WITH_BINARIES_USERNAME</code>: (optional) Username when the Artifact Manager is secured. Defaults to <code>admin</code>.</p>
+</li>
+<li>
+<p><code>REPO_WITH_BINARIES_PASSWORD</code>: (optional) Password when the Artifact Manager is secured. Defaults to <code>password</code>.</p>
+</li>
+<li>
+<p><code>PUBLISH_ARTIFACTS</code>: If set to <code>true</code>, publishes the artifact to binary storage. Defaults to <code>true</code>.</p>
+</li>
+<li>
+<p><code>PUBLISH_ARTIFACTS_OFFLINE</code>: If set to <code>true</code>, it will publish the artifacts to local <code>.m2</code>. Defaults to <code>false</code>.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>These environment variables are used when contracts lay in an external repository. To enable
+this feature, you must set the <code>EXTERNAL_CONTRACTS_ARTIFACT_ID</code> environment variable.</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>EXTERNAL_CONTRACTS_GROUP_ID</code>: Group ID of the project with contracts. Defaults to <code>com.example</code></p>
+</li>
+<li>
+<p><code>EXTERNAL_CONTRACTS_ARTIFACT_ID</code>: Artifact ID of the project with contracts.</p>
+</li>
+<li>
+<p><code>EXTERNAL_CONTRACTS_CLASSIFIER</code>: Classifier of the project with contracts. Empty by default.</p>
+</li>
+<li>
+<p><code>EXTERNAL_CONTRACTS_VERSION</code>: Version of the project with contracts. Defaults to <code>+</code>, equivalent to picking the latest.</p>
+</li>
+<li>
+<p><code>EXTERNAL_CONTRACTS_REPO_WITH_BINARIES_URL</code>: URL of your Artifact Manager. It defaults to
+the value of <code>REPO_WITH_BINARIES_URL</code> environment variable.
+If that is not set, it defaults to <code><a href="http://localhost:8081/artifactory/libs-release-local" class="bare">localhost:8081/artifactory/libs-release-local</a></code>,
+which is the default URL of <a href="https://jfrog.com/artifactory/">Artifactory</a> running locally.</p>
+</li>
+<li>
+<p><code>EXTERNAL_CONTRACTS_REPO_WITH_BINARIES_USERNAME</code>: (optional) Username if the <code>EXTERNAL_CONTRACTS_REPO_WITH_BINARIES_URL</code>
+requires authentication. It defaults to <code>REPO_WITH_BINARIES_USERNAME</code>. If that is not set, it defaults to <code>admin</code>.</p>
+</li>
+<li>
+<p><code>EXTERNAL_CONTRACTS_REPO_WITH_BINARIES_PASSWORD</code>: (optional) Password if the <code>EXTERNAL_CONTRACTS_REPO_WITH_BINARIES_URL</code>
+requires authentication. It defaults to <code>REPO_WITH_BINARIES_PASSWORD</code>. If that is not set, it defaults to <code>password</code>.</p>
+</li>
+<li>
+<p><code>EXTERNAL_CONTRACTS_PATH</code>: Path to contracts for the given project, inside the project with contracts.
+Defaults to slash-separated <code>EXTERNAL_CONTRACTS_GROUP_ID</code> concatenated with <code>/</code> and <code>EXTERNAL_CONTRACTS_ARTIFACT_ID</code>. For example,
+for group id <code>cat-server-side.dog</code> and artifact id <code>fish</code>, would result in <code>cat/dog/fish</code> for the contracts path.</p>
+</li>
+<li>
+<p><code>EXTERNAL_CONTRACTS_WORK_OFFLINE</code>; If set to <code>true</code>, retrieves the artifact with contracts
+from the container&#8217;s <code>.m2</code>. Mount your local <code>.m2</code> as a volume available at the container&#8217;s <code>/root/.m2</code> path.</p>
+</li>
+</ul>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-warning" title="Warning"></i>
+</td>
+<td class="content">
+You must not set both <code>EXTERNAL_CONTRACTS_WORK_OFFLINE</code> and <code>EXTERNAL_CONTRACTS_REPO_WITH_BINARIES_URL</code>.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The following environment variables are used when tests are executed:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>APPLICATION_BASE_URL</code>: URL against which tests should be run.
+Remember that it has to be accessible from the Docker container (for example, <code>localhost</code>
+does not work)</p>
+</li>
+<li>
+<p><code>APPLICATION_USERNAME</code>: (optional) Username for basic authentication to your application.</p>
+</li>
+<li>
+<p><code>APPLICATION_PASSWORD</code>: (optional) Password for basic authentication to your application.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="docker-example-of-usage"><a class="anchor" href="#docker-example-of-usage"></a><a class="link" href="#docker-example-of-usage">6.2.2. Example of Usage</a></h4>
+<div class="paragraph">
+<p>In this section, we explore a simple MVC application. To get started, clone the following
+git repository and cd to the resulting directory, by running the following commands:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ git clone https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs
+$ cd bookstore</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The contracts are available in the <code>/contracts</code> folder.</p>
+</div>
+<div class="paragraph">
+<p>Since we want to run tests, we can run the following command:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ npm test</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>However, for learning purposes, we split it into pieces, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash"># Stop docker infra (nodejs, artifactory)
+$ ./stop_infra.sh
+# Start docker infra (nodejs, artifactory)
+$ ./setup_infra.sh
+
+# Kill &amp; Run app
+$ pkill -f "node app"
+$ nohup node app &amp;
+
+# Prepare environment variables
+$ SC_CONTRACT_DOCKER_VERSION="..."
+$ APP_IP="192.168.0.100"
+$ APP_PORT="3000"
+$ ARTIFACTORY_PORT="8081"
+$ APPLICATION_BASE_URL="http://${APP_IP}:${APP_PORT}"
+$ ARTIFACTORY_URL="http://${APP_IP}:${ARTIFACTORY_PORT}/artifactory/libs-release-local"
+$ CURRENT_DIR="$( pwd )"
+$ CURRENT_FOLDER_NAME=${PWD##*/}
+$ PROJECT_VERSION="0.0.1.RELEASE"
+
+# Execute contract tests
+$ docker run  --rm -e "APPLICATION_BASE_URL=${APPLICATION_BASE_URL}" -e "PUBLISH_ARTIFACTS=true" -e "PROJECT_NAME=${CURRENT_FOLDER_NAME}" -e "REPO_WITH_BINARIES_URL=${ARTIFACTORY_URL}" -e "PROJECT_VERSION=${PROJECT_VERSION}" -v "${CURRENT_DIR}/contracts/:/contracts:ro" -v "${CURRENT_DIR}/node_modules/spring-cloud-contract/output:/spring-cloud-contract-output/" springcloud/spring-cloud-contract:"${SC_CONTRACT_DOCKER_VERSION}"
+
+# Kill app
+$ pkill -f "node app"</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Through bash scripts, the following happens:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>The infrastructure (MongoDb and Artifactory) is set up.
+In a real-life scenario, you would run the NodeJS application
+with a mocked database. In this example, we want to show how we can
+benefit from Spring Cloud Contract in very little time.</p>
+</li>
+<li>
+<p>Due to those constraints, the contracts also represent the
+stateful situation.</p>
+<div class="ulist">
+<ul>
+<li>
+<p>The first request is a <code>POST</code> that causes data to get inserted to the database.</p>
+</li>
+<li>
+<p>The second request is a <code>GET</code> that returns a list of data with 1 previously inserted element.</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>The NodeJS application is started (on port <code>3000</code>).</p>
+</li>
+<li>
+<p>The contract tests are generated through Docker, and tests
+are run against the running application.</p>
+<div class="ulist">
+<ul>
+<li>
+<p>The contracts are taken from <code>/contracts</code> folder.</p>
+</li>
+<li>
+<p>The output of the test execution is available under
+<code>node_modules/spring-cloud-contract/output</code>.</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>The stubs are uploaded to Artifactory. You can find them in
+<a href="http://localhost:8081/artifactory/libs-release-local/com/example/bookstore/0.0.1.RELEASE/" class="bare">localhost:8081/artifactory/libs-release-local/com/example/bookstore/0.0.1.RELEASE/</a> .
+The stubs are at <a href="http://localhost:8081/artifactory/libs-release-local/com/example/bookstore/0.0.1.RELEASE/bookstore-0.0.1.RELEASE-stubs.jar" class="bare">localhost:8081/artifactory/libs-release-local/com/example/bookstore/0.0.1.RELEASE/bookstore-0.0.1.RELEASE-stubs.jar</a>.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="docker-stubrunner"><a class="anchor" href="#docker-stubrunner"></a><a class="link" href="#docker-stubrunner">6.3. Running Stubs on the Consumer Side</a></h3>
+<div class="paragraph">
+<p>This section describes how to use Docker on the consumer side to fetch and run stubs.</p>
+</div>
+<div class="paragraph">
+<p>We publish a <code>spring-cloud/spring-cloud-contract-stub-runner</code> Docker image
+that starts the standalone version of Stub Runner.</p>
+</div>
+<div class="sect3">
+<h4 id="docker-stubrunner-env-vars"><a class="anchor" href="#docker-stubrunner-env-vars"></a><a class="link" href="#docker-stubrunner-env-vars">6.3.1. Environment Variables</a></h4>
+<div class="paragraph">
+<p>You can run the docker image and pass any of the <a href="#features-stub-runner-common-properties-junit-spring">Common Properties for JUnit and Spring</a>
+as environment variables. The convention is that all the
+letters should be upper case.
+The dot (<code>.</code>) should be replaced with underscore (<code>_</code>) characters. For example,
+the <code>stubrunner.repositoryRoot</code> property should be represented
+as a <code>STUBRUNNER_REPOSITORY_ROOT</code> environment variable.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="docker-stubrunner-example"><a class="anchor" href="#docker-stubrunner-example"></a><a class="link" href="#docker-stubrunner-example">6.3.2. Example of Usage</a></h4>
+<div class="paragraph">
+<p>We want to use the stubs created in this <a href="#docker-server-side">[docker-server-side]</a> step.
+Assume that we want to run the stubs on port <code>9876</code>. You can see the NodeJS code
+by cloning the repository and changing to the directory indicated in the following commands:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">$ git clone https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs
+$ cd bookstore</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Now we can run the Stub Runner Boot application with the stubs, by running the following
+commands:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash"># Provide the Spring Cloud Contract Docker version
+$ SC_CONTRACT_DOCKER_VERSION="..."
+# The IP at which the app is running and Docker container can reach it
+$ APP_IP="192.168.0.100"
+# Spring Cloud Contract Stub Runner properties
+$ STUBRUNNER_PORT="8083"
+# Stub coordinates 'groupId:artifactId:version:classifier:port'
+$ STUBRUNNER_IDS="com.example:bookstore:0.0.1.RELEASE:stubs:9876"
+$ STUBRUNNER_REPOSITORY_ROOT="http://${APP_IP}:8081/artifactory/libs-release-local"
+# Run the docker with Stub Runner Boot
+$ docker run  --rm -e "STUBRUNNER_IDS=${STUBRUNNER_IDS}" -e "STUBRUNNER_REPOSITORY_ROOT=${STUBRUNNER_REPOSITORY_ROOT}" -e "STUBRUNNER_STUBS_MODE=REMOTE" -p "${STUBRUNNER_PORT}:${STUBRUNNER_PORT}" -p "9876:9876" springcloud/spring-cloud-contract-stub-runner:"${SC_CONTRACT_DOCKER_VERSION}"</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>When the preceding commands run,</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>A standalone Stub Runner application gets started.</p>
+</li>
+<li>
+<p>It downloads the stub with coordinates <code>com.example:bookstore:0.0.1.RELEASE:stubs</code> on port <code>9876</code>.</p>
+</li>
+<li>
+<p>It gets downloads from Artifactory running at <code><a href="http://192.168.0.100:8081/artifactory/libs-release-local" class="bare">192.168.0.100:8081/artifactory/libs-release-local</a></code>.</p>
+</li>
+<li>
+<p>After a whil, Stub Runner is running on port <code>8083</code>.</p>
+</li>
+<li>
+<p>The stubs are running at port <code>9876</code>.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>On the server side, we built a stateful stub. We can use curl to assert
+that the stubs are setup properly. To do so, run the following commands:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash"># let's execute the first request (no response is returned)
+$ curl -H "Content-Type:application/json" -X POST --data '{ "title" : "Title", "genre" : "Genre", "description" : "Description", "author" : "Author", "publisher" : "Publisher", "pages" : 100, "image_url" : "https://d213dhlpdb53mu.cloudfront.net/assets/pivotal-square-logo-41418bd391196c3022f3cd9f3959b3f6d7764c47873d858583384e759c7db435.svg", "buy_url" : "https://pivotal.io" }' http://localhost:9876/api/books
+# Now time for the second request
+$ curl -X GET http://localhost:9876/api/books
+# You will receive contents of the JSON</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+If you want use the stubs that you have built locally, on your host,
+you should set the <code>-e STUBRUNNER_STUBS_MODE=LOCAL</code> environment variable and mount
+the volume of your local m2 (<code>-v "${HOME}/.m2/:/root/.m2:ro"</code>).
+</td>
+</tr>
+</table>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="contract-customization"><a class="anchor" href="#contract-customization"></a><a class="link" href="#contract-customization">7. Spring Cloud Contract customization</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>In this section, we describe how to customize various parts of Spring Cloud Contract.</p>
+</div>
+<div class="sect2">
+<h3 id="customization-customization"><a class="anchor" href="#customization-customization"></a><a class="link" href="#customization-customization">7.1. DSL Customization</a></h3>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+This section is valid only for the Groovy DSL
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>You can customize the Spring Cloud Contract Verifier by extending the DSL, as shown in
+the remainder of this section.</p>
+</div>
+<div class="sect3">
+<h4 id="customization-extending"><a class="anchor" href="#customization-extending"></a><a class="link" href="#customization-extending">7.1.1. Extending the DSL</a></h4>
+<div class="paragraph">
+<p>You can provide your own functions to the DSL. The key requirement for this feature is to
+maintain the static compatibility. Later in this document, you can see examples of:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Creating a JAR with reusable classes.</p>
+</li>
+<li>
+<p>Referencing of these classes in the DSLs.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>You can find the full example
+<a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples">here</a>.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="customization-extending-common-jar"><a class="anchor" href="#customization-extending-common-jar"></a><a class="link" href="#customization-extending-common-jar">7.1.2. Common JAR</a></h4>
+<div class="paragraph">
+<p>The following examples show three classes that can be reused in the DSLs.</p>
+</div>
+<div class="paragraph">
+<p><code>PatternUtils</code> contains functions used by both the consumer and the producer.
+The following listing shows the <code>PatternUtils</code> class:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package com.example;
+
+import java.util.regex.Pattern;
+
+/**
+ * If you want to use {@link Pattern} directly in your tests
+ * then you can create a class resembling this one. It can
+ * contain all the {@link Pattern} you want to use in the DSL.
+ *
+ * &lt;pre&gt;
+ * {@code
+ * request {
+ *     body(
+ *         [ age: $(c(PatternUtils.oldEnough()))]
+ *     )
+ * }
+ * &lt;/pre&gt;
+ *
+ * Notice that we're using both {@code $()} for dynamic values
+ * and {@code c()} for the consumer side.
+ *
+ * @author Marcin Grzejszczak
+ */
+//tag::impl[]
+public class PatternUtils {
+
+    public static String tooYoung() {
+        //remove::start[]
+        return "[0-1][0-9]";
+        //remove::end[return]
+    }
+
+    public static Pattern oldEnough() {
+        //remove::start[]
+        return Pattern.compile("[2-9][0-9]");
+        //remove::end[return]
+    }
+
+    /**
+     * Makes little sense but it's just an example ;)
+     */
+    public static Pattern ok() {
+        //remove::start[]
+        return Pattern.compile("OK");
+        //remove::end[return]
+    }
+}
+//end::impl[]</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p><code>ConsumerUtils</code> contains functions used by the consumer.
+The following listing shows the <code>ConsumerUtils</code> class:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package com.example;
+
+import org.springframework.cloud.contract.spec.internal.ClientDslProperty;
+
+/**
+ * DSL Properties passed to the DSL from the consumer's perspective.
+ * That means that on the input side {@code Request} for HTTP
+ * or {@code Input} for messaging you can have a regular expression.
+ * On the {@code Response} for HTTP or {@code Output} for messaging
+ * you have to have a concrete value.
+ *
+ * @author Marcin Grzejszczak
+ */
+//tag::impl[]
+public class ConsumerUtils {
+    /**
+     * Consumer side property. By using the {@link ClientDslProperty}
+     * you can omit most of boilerplate code from the perspective
+     * of dynamic values. Example
+     *
+     * &lt;pre&gt;
+     * {@code
+     * request {
+     *     body(
+     *         [ age: $(ConsumerUtils.oldEnough())]
+     *     )
+     * }
+     * &lt;/pre&gt;
+     *
+     * That way it's in the implementation that we decide what value we will pass to the consumer
+     * and which one to the producer.
+     *
+     * @author Marcin Grzejszczak
+     */
+    public static ClientDslProperty oldEnough() {
+        //remove::start[]
+        // this example is not the best one and
+        // theoretically you could just pass the regex instead of `ServerDslProperty` but
+        // it's just to show some new tricks :)
+        return new ClientDslProperty(PatternUtils.oldEnough(), 40);
+        //remove::end[return]
+    }
+
+}
+//end::impl[]</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p><code>ProducerUtils</code> contains functions used by the producer.
+The following listing shows the <code>ProducerUtils</code> class:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package com.example;
+
+import org.springframework.cloud.contract.spec.internal.ServerDslProperty;
+
+/**
+ * DSL Properties passed to the DSL from the producer's perspective.
+ * That means that on the input side {@code Request} for HTTP
+ * or {@code Input} for messaging you have to have a concrete value.
+ * On the {@code Response} for HTTP or {@code Output} for messaging
+ * you can have a regular expression.
+ *
+ * @author Marcin Grzejszczak
+ */
+//tag::impl[]
+public class ProducerUtils {
+
+    /**
+     * Producer side property. By using the {@link ProducerUtils}
+     * you can omit most of boilerplate code from the perspective
+     * of dynamic values. Example
+     *
+     * &lt;pre&gt;
+     * {@code
+     * response {
+     *     body(
+     *         [ status: $(ProducerUtils.ok())]
+     *     )
+     * }
+     * &lt;/pre&gt;
+     *
+     * That way it's in the implementation that we decide what value we will pass to the consumer
+     * and which one to the producer.
+     */
+    public static ServerDslProperty ok() {
+        // this example is not the best one and
+        // theoretically you could just pass the regex instead of `ServerDslProperty` but
+        // it's just to show some new tricks :)
+        return new ServerDslProperty( PatternUtils.ok(), "OK");
+    }
+}
+//end::impl[]</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="customization-test-dep"><a class="anchor" href="#customization-test-dep"></a><a class="link" href="#customization-test-dep">7.1.3. Adding a Test Dependency in the Project&#8217;s Dependencies</a></h4>
+<div class="paragraph">
+<p>To add a test dependency in the project&#8217;s dependencies, you must first add the common jar
+dependency as a test dependency. Because your contracts files
+are available on the test resources path,  the common jar classes automatically become
+visible in your Groovy files. The following examples show how to test the dependency:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
+    &lt;groupId&gt;com.example&lt;/groupId&gt;
+    &lt;artifactId&gt;beer-common&lt;/artifactId&gt;
+    &lt;version&gt;${project.version}&lt;/version&gt;
+    &lt;scope&gt;test&lt;/scope&gt;
+&lt;/dependency&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">testCompile("com.example:beer-common:0.0.1.BUILD-SNAPSHOT")</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="customization-plugin-dep"><a class="anchor" href="#customization-plugin-dep"></a><a class="link" href="#customization-plugin-dep">7.1.4. Adding a Test Dependency in the Plugin&#8217;s Dependencies</a></h4>
+<div class="paragraph">
+<p>Now, you must add the dependency for the plugin to reuse at runtime, as the
+following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;packageWithBaseClasses&gt;com.example&lt;/packageWithBaseClasses&gt;
+        &lt;baseClassMappings&gt;
+            &lt;baseClassMapping&gt;
+                &lt;contractPackageRegex&gt;.*intoxication.*&lt;/contractPackageRegex&gt;
+                &lt;baseClassFQN&gt;com.example.intoxication.BeerIntoxicationBase&lt;/baseClassFQN&gt;
+            &lt;/baseClassMapping&gt;
+        &lt;/baseClassMappings&gt;
+    &lt;/configuration&gt;
+    &lt;dependencies&gt;
+        &lt;dependency&gt;
+            &lt;groupId&gt;com.example&lt;/groupId&gt;
+            &lt;artifactId&gt;beer-common&lt;/artifactId&gt;
+            &lt;version&gt;${project.version}&lt;/version&gt;
+            &lt;scope&gt;compile&lt;/scope&gt;
+        &lt;/dependency&gt;
+    &lt;/dependencies&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">classpath "com.example:beer-common:0.0.1.BUILD-SNAPSHOT"</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="customization-referencing"><a class="anchor" href="#customization-referencing"></a><a class="link" href="#customization-referencing">7.1.5. Referencing Classes in DSLs</a></h4>
+<div class="paragraph">
+<p>You can now reference your classes in your DSL, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package contracts.beer.rest
+
+import com.example.ConsumerUtils
+import com.example.ProducerUtils
+import org.springframework.cloud.contract.spec.Contract
+
+Contract.make {
+    description("""
+Represents a successful scenario of getting a beer
+
+```
+given:
+    client is old enough
+when:
+    he applies for a beer
+then:
+    we'll grant him the beer
+```
+
+""")
+    request {
+        method 'POST'
+        url '/check'
+        body(
+                age: $(ConsumerUtils.oldEnough())
+        )
+        headers {
+            contentType(applicationJson())
+        }
+    }
+    response {
+        status 200
+        body("""
+            {
+                "status": "${value(ProducerUtils.ok())}"
+            }
+            """)
+        headers {
+            contentType(applicationJson())
+        }
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+You can set the Spring Cloud Contract plugin up by setting <code>convertToYaml</code> to
+<code>true</code>. That way, you do NOT have to add the dependency with the extended functionality
+to the consumer side, since the consumer side uses YAML contracts instead of Groovy contracts.
+</td>
+</tr>
+</table>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="customization-wiremock"><a class="anchor" href="#customization-wiremock"></a><a class="link" href="#customization-wiremock">7.2. WireMock Customization</a></h3>
+<div class="paragraph">
+<p>In this section, we show how to customize the way you work with <a href="https://wiremock.org">WireMock</a>.</p>
+</div>
+<div class="sect3">
+<h4 id="customization-wiremock-extension"><a class="anchor" href="#customization-wiremock-extension"></a><a class="link" href="#customization-wiremock-extension">7.2.1. Registering Your Own WireMock Extension</a></h4>
+<div class="paragraph">
+<p>WireMock lets you register custom extensions. By default, Spring Cloud Contract registers
+the transformer, which lets you reference a request from a response. If you want to
+provide your own extensions, you can register an implementation of the
+<code>org.springframework.cloud.contract.verifier.dsl.wiremock.WireMockExtensions</code> interface.
+Since we use the <code>spring.factories</code> extension approach, you can create an entry in
+<code>META-INF/spring.factories</code> file similar to the following:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">org.springframework.cloud.contract.verifier.dsl.wiremock.WireMockExtensions=\
+org.springframework.cloud.contract.stubrunner.provider.wiremock.TestWireMockExtensions
+org.springframework.cloud.contract.spec.ContractConverter=\
+org.springframework.cloud.contract.stubrunner.TestCustomYamlContractConverter</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following example shows a custom extension:</p>
+</div>
+<div class="exampleblock">
+<div class="title">Example 3. TestWireMockExtensions.groovy</div>
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">/*
+ * Copyright 2013-2020 the original author or authors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *      https://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.springframework.cloud.contract.verifier.dsl.wiremock
+
+import com.github.tomakehurst.wiremock.extension.Extension
+
+/**
+ * Extension that registers the default transformer and the custom one
+ */
+class TestWireMockExtensions implements WireMockExtensions {
+    @Override
+    List&lt;Extension&gt; extensions() {
+        return [
+                new DefaultResponseTransformer(),
+                new CustomExtension()
+        ]
+    }
+}
+
+class CustomExtension implements Extension {
+
+    @Override
+    String getName() {
+        return "foo-transformer"
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+Remember to override the <code>applyGlobally()</code> method and set it to <code>false</code> if you
+want the transformation to be applied only for a mapping that explicitly requires it.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="customization-wiremock-configuration"><a class="anchor" href="#customization-wiremock-configuration"></a><a class="link" href="#customization-wiremock-configuration">7.2.2. Customization of WireMock Configuration</a></h4>
+<div class="paragraph">
+<p>You can register a bean of type <code>org.springframework.cloud.contract.wiremock.WireMockConfigurationCustomizer</code>
+to customize the WireMock configuration (for example, to add custom transformers).
+The following example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">        @Bean
+        WireMockConfigurationCustomizer optionsCustomizer() {
+            return new WireMockConfigurationCustomizer() {
+                @Override
+                public void customize(WireMockConfiguration options) {
+// perform your customization here
+                }
+            };
+        }</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="customization-pluggable-architecture"><a class="anchor" href="#customization-pluggable-architecture"></a><a class="link" href="#customization-pluggable-architecture">7.3. Using the Pluggable Architecture</a></h3>
+<div class="paragraph">
+<p>You may encounter cases where your contracts have been defined in other formats,
+such as YAML, RAML, or PACT. In those cases, you still want to benefit from the automatic
+generation of tests and stubs. You can add your own implementation for generating both
+tests and stubs. Also, you can customize the way tests are generated (for example, you
+can generate tests for other languages) and the way stubs are generated (for example, you
+can generate stubs for other HTTP server implementations).</p>
+</div>
+<div class="sect3">
+<h4 id="customization-custom-contract-converter"><a class="anchor" href="#customization-custom-contract-converter"></a><a class="link" href="#customization-custom-contract-converter">7.3.1. Custom Contract Converter</a></h4>
+<div class="paragraph">
+<p>The <code>ContractConverter</code> interface lets you register your own implementation of a contract
+structure converter. The following code listing shows the <code>ContractConverter</code> interface:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package org.springframework.cloud.contract.spec;
+
+import java.io.File;
+import java.util.Collection;
+
+/**
+ * Converter to be used to convert FROM {@link File} TO {@link Contract} and from
+ * {@link Contract} to {@code T}.
+ *
+ * @param &lt;T&gt; - type to which we want to convert the contract
+ * @author Marcin Grzejszczak
+ * @since 1.1.0
+ */
+public interface ContractConverter&lt;T&gt; extends ContractStorer&lt;T&gt; {
+
+    /**
+     * Should this file be accepted by the converter. Can use the file extension to check
+     * if the conversion is possible.
+     * @param file - file to be considered for conversion
+     * @return - {@code true} if the given implementation can convert the file
+     */
+    boolean isAccepted(File file);
+
+    /**
+     * Converts the given {@link File} to its {@link Contract} representation.
+     * @param file - file to convert
+     * @return - {@link Contract} representation of the file
+     */
+    Collection&lt;Contract&gt; convertFrom(File file);
+
+    /**
+     * Converts the given {@link Contract} to a {@link T} representation.
+     * @param contract - the parsed contract
+     * @return - {@link T} the type to which we do the conversion
+     */
+    T convertTo(Collection&lt;Contract&gt; contract);
+
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Your implementation must define the condition on which it should start the
+conversion. Also, you must define how to perform that conversion in both directions.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+Once you create your implementation, you must create a
+<code>/META-INF/spring.factories</code> file in which you provide the fully qualified name of your
+implementation.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The following example shows a typical <code>spring.factories</code> file:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code>org.springframework.cloud.contract.spec.ContractConverter=\
+org.springframework.cloud.contract.verifier.converter.YamlContractConverter</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="customization-custom-test-generator"><a class="anchor" href="#customization-custom-test-generator"></a><a class="link" href="#customization-custom-test-generator">7.3.2. Using the Custom Test Generator</a></h4>
+<div class="paragraph">
+<p>If you want to generate tests for languages other than Java or you are not happy with the
+way the verifier builds Java tests, you can register your own implementation.</p>
+</div>
+<div class="paragraph">
+<p>The <code>SingleTestGenerator</code> interface lets you register your own implementation.  The
+following code listing shows the <code>SingleTestGenerator</code> interface:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package org.springframework.cloud.contract.verifier.builder;
+
+import java.nio.file.Path;
+import java.util.Collection;
+
+import org.springframework.cloud.contract.verifier.config.ContractVerifierConfigProperties;
+import org.springframework.cloud.contract.verifier.file.ContractMetadata;
+
+/**
+ * Builds a single test.
+ *
+ * @since 1.1.0
+ */
+public interface SingleTestGenerator {
+
+    /**
+     * Creates contents of a single test class in which all test scenarios from the
+     * contract metadata should be placed.
+     * @param properties - properties passed to the plugin
+     * @param listOfFiles - list of parsed contracts with additional metadata
+     * @param className - the name of the generated test class
+     * @param classPackage - the name of the package in which the test class should be
+     * stored
+     * @param includedDirectoryRelativePath - relative path to the included directory
+     * @return contents of a single test class
+     * @deprecated use{@link SingleTestGenerator#buildClass(ContractVerifierConfigProperties, Collection, String, GeneratedClassData)}
+     */
+    @Deprecated
+    String buildClass(ContractVerifierConfigProperties properties,
+            Collection&lt;ContractMetadata&gt; listOfFiles, String className,
+            String classPackage, String includedDirectoryRelativePath);
+
+    /**
+     * Creates contents of a single test class in which all test scenarios from the
+     * contract metadata should be placed.
+     * @param properties - properties passed to the plugin
+     * @param listOfFiles - list of parsed contracts with additional metadata
+     * @param generatedClassData - information about the generated class
+     * @param includedDirectoryRelativePath - relative path to the included directory
+     * @return contents of a single test class
+     */
+    String buildClass(ContractVerifierConfigProperties properties,
+            Collection&lt;ContractMetadata&gt; listOfFiles,
+            String includedDirectoryRelativePath, GeneratedClassData generatedClassData);
+
+    class GeneratedClassData {
+
+        public final String className;
+
+        public final String classPackage;
+
+        public final Path testClassPath;
+
+        public GeneratedClassData(String className, String classPackage,
+                Path testClassPath) {
+            this.className = className;
+            this.classPackage = classPackage;
+            this.testClassPath = testClassPath;
+        }
+
+    }
+
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Again, you must provide a <code>spring.factories</code> file, such as the one shown in the following
+example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code>org.springframework.cloud.contract.verifier.builder.SingleTestGenerator=/
+com.example.MyGenerator</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="customization-custom-stub-generator"><a class="anchor" href="#customization-custom-stub-generator"></a><a class="link" href="#customization-custom-stub-generator">7.3.3. Using the Custom Stub Generator</a></h4>
+<div class="paragraph">
+<p>If you want to generate stubs for stub servers other than WireMock, you can plug in your
+own implementation of the <code>StubGenerator</code> interface. The following code listing shows the
+<code>StubGenerator</code> interface:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package org.springframework.cloud.contract.verifier.converter;
+
+import java.util.Map;
+
+import org.springframework.cloud.contract.spec.Contract;
+import org.springframework.cloud.contract.verifier.file.ContractMetadata;
+
+/**
+ * Converts contracts into their stub representation.
+ *
+ * @since 1.1.0
+ */
+public interface StubGenerator {
+
+    /**
+     * @param fileName - file name
+     * @return {@code true} if the converter can handle the file to convert it into a
+     * stub.
+     */
+    default boolean canHandleFileName(String fileName) {
+        return fileName.endsWith(fileExtension());
+    }
+
+    /**
+     * @param rootName - root name of the contract
+     * @param content - metadata of the contract
+     * @return the collection of converted contracts into stubs. One contract can result
+     * in multiple stubs.
+     */
+    Map&lt;Contract, String&gt; convertContents(String rootName, ContractMetadata content);
+
+    /**
+     * @param inputFileName - name of the input file
+     * @return the name of the converted stub file. If you have multiple contracts in a
+     * single file then a prefix will be added to the generated file. If you provide the
+     * {@link Contract#name} field then that field will override the generated file name.
+     *
+     * Example: name of file with 2 contracts is {@code foo.groovy}, it will be converted
+     * by the implementation to {@code foo.json}. The recursive file converter will create
+     * two files {@code 0_foo.json} and {@code 1_foo.json}
+     */
+    String generateOutputFileNameForInput(String inputFileName);
+
+    /**
+     * Describes the file extension that this stub generator can handle.
+     * @return string describing the file extension
+     */
+    default String fileExtension() {
+        return ".json";
+    }
+
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Again, you must provide a <code>spring.factories</code> file, such as the one shown in the following
+example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code># Stub converters
+org.springframework.cloud.contract.verifier.converter.StubGenerator=\
+org.springframework.cloud.contract.verifier.wiremock.DslToWireMockClientConverter</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The default implementation is the WireMock stub generation.</p>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+You can provide multiple stub generator implementations. For example, from a single
+DSL, you can produce both WireMock stubs and Pact files.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="customization-custom-stub-runner"><a class="anchor" href="#customization-custom-stub-runner"></a><a class="link" href="#customization-custom-stub-runner">7.3.4. Using the Custom Stub Runner</a></h4>
+<div class="paragraph">
+<p>If you decide to use a custom stub generation, you also need a custom way of running
+stubs with your different stub provider.</p>
+</div>
+<div class="paragraph">
+<p>Assume that you use <a href="https://github.com/dreamhead/moco">Moco</a> to build your stubs and that
+you have written a stub generator and placed your stubs in a JAR file.</p>
+</div>
+<div class="paragraph">
+<p>In order for Stub Runner to know how to run your stubs, you have to define a custom
+HTTP Stub server implementation, which might resemble the following example:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">package org.springframework.cloud.contract.stubrunner.provider.moco
+
+import com.github.dreamhead.moco.bootstrap.arg.HttpArgs
+import com.github.dreamhead.moco.runner.JsonRunner
+import com.github.dreamhead.moco.runner.RunnerSetting
+import groovy.transform.CompileStatic
+import groovy.util.logging.Commons
+
+import org.springframework.cloud.contract.stubrunner.HttpServerStub
+import org.springframework.util.SocketUtils
+
+@Commons
+@CompileStatic
+class MocoHttpServerStub implements HttpServerStub {
+
+    private boolean started
+    private JsonRunner runner
+    private int port
+
+    @Override
+    int port() {
+        if (!isRunning()) {
+            return -1
+        }
+        return port
+    }
+
+    @Override
+    boolean isRunning() {
+        return started
+    }
+
+    @Override
+    HttpServerStub start() {
+        return start(SocketUtils.findAvailableTcpPort())
+    }
+
+    @Override
+    HttpServerStub start(int port) {
+        this.port = port
+        return this
+    }
+
+    @Override
+    HttpServerStub stop() {
+        if (!isRunning()) {
+            return this
+        }
+        this.runner.stop()
+        return this
+    }
+
+    @Override
+    HttpServerStub registerMappings(Collection&lt;File&gt; stubFiles) {
+        List&lt;RunnerSetting&gt; settings = stubFiles.findAll { it.name.endsWith("json") }
+            .collect {
+            log.info("Trying to parse [${it.name}]")
+            try {
+                return RunnerSetting.aRunnerSetting().addStream(it.newInputStream()).
+                    build()
+            }
+            catch (Exception e) {
+                log.warn("Exception occurred while trying to parse file [${it.name}]", e)
+                return null
+            }
+        }.findAll { it }
+        this.runner = JsonRunner.newJsonRunnerWithSetting(settings,
+            HttpArgs.httpArgs().withPort(this.port).build())
+        this.runner.run()
+        this.started = true
+        return this
+    }
+
+    @Override
+    String registeredMappings() {
+        return ""
+    }
+
+    @Override
+    boolean isAccepted(File file) {
+        return file.name.endsWith(".json")
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Then you can register it in your <code>spring.factories</code> file, as the following
+example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code>org.springframework.cloud.contract.stubrunner.HttpServerStub=\
+org.springframework.cloud.contract.stubrunner.provider.moco.MocoHttpServerStub</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Now you can run stubs with Moco.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+If you do not provide any implementation, the default (WireMock)
+implementation is used. If you provide more than one, the first one on the list is used.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="customization-custom-stub-downloader"><a class="anchor" href="#customization-custom-stub-downloader"></a><a class="link" href="#customization-custom-stub-downloader">7.3.5. Using the Custom Stub Downloader</a></h4>
+<div class="paragraph">
+<p>You can customize the way your stubs are downloaded by creating an implementation of the
+<code>StubDownloaderBuilder</code> interface, as the following example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package com.example;
+
+class CustomStubDownloaderBuilder implements StubDownloaderBuilder {
+
+    @Override
+    public StubDownloader build(final StubRunnerOptions stubRunnerOptions) {
+        return new StubDownloader() {
+            @Override
+            public Map.Entry&lt;StubConfiguration, File&gt; downloadAndUnpackStubJar(
+                    StubConfiguration config) {
+                File unpackedStubs = retrieveStubs();
+                return new AbstractMap.SimpleEntry&lt;&gt;(
+                        new StubConfiguration(config.getGroupId(), config.getArtifactId(), version,
+                                config.getClassifier()), unpackedStubs);
+            }
+
+            File retrieveStubs() {
+                // here goes your custom logic to provide a folder where all the stubs reside
+            }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Then you can register it in your <code>spring.factories</code> file, as the following
+example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code># Example of a custom Stub Downloader Provider
+org.springframework.cloud.contract.stubrunner.StubDownloaderBuilder=\
+com.example.CustomStubDownloaderBuilder</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Now you can pick a folder with the source of your stubs.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+If you do not provide any implementation, the default (scanning the classpath) is used.
+If you provide the <code>stubsMode = StubRunnerProperties.StubsMode.LOCAL</code> or
+<code>stubsMode = StubRunnerProperties.StubsMode.REMOTE</code>, the Aether implementation is used
+If you provide more than one, the first one on the list is used.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="scm-stub-downloader"><a class="anchor" href="#scm-stub-downloader"></a><a class="link" href="#scm-stub-downloader">7.3.6. Using the SCM Stub Downloader</a></h4>
+<div class="paragraph">
+<p>Whenever the <code>repositoryRoot</code> starts with a SCM protocol
+(currently, we support only <code>git://</code>), the stub downloader tries
+to clone the repository and use it as a source of contracts
+to generate tests or stubs.</p>
+</div>
+<div class="paragraph">
+<p>Through environment variables, system properties, or properties set
+inside the plugin or the contracts repository configuration, you can
+tweak the downloader&#8217;s behavior. The following table describes the available
+properties:</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 1. SCM Stub Downloader properties</caption>
+<colgroup>
+<col style="width: 33.3333%;">
+<col style="width: 33.3333%;">
+<col style="width: 33.3334%;">
+</colgroup>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Type of a property</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Name of the property</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Description</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>git.branch</code> (plugin prop)</p>
+<p class="tableblock">* <code>stubrunner.properties.git.branch</code> (system prop)</p>
+<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_GIT_BRANCH</code> (env prop)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">master</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Which branch to checkout</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>git.username</code> (plugin prop)</p>
+<p class="tableblock">* <code>stubrunner.properties.git.username</code> (system prop)</p>
+<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_GIT_USERNAME</code> (env prop)</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Git clone username</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>git.password</code> (plugin prop)</p>
+<p class="tableblock">* <code>stubrunner.properties.git.password</code> (system prop)</p>
+<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_GIT_PASSWORD</code> (env prop)</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Git clone password</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>git.no-of-attempts</code> (plugin prop)</p>
+<p class="tableblock">* <code>stubrunner.properties.git.no-of-attempts</code> (system prop)</p>
+<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_GIT_NO_OF_ATTEMPTS</code> (env prop)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">10</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Number of attempts to push the commits to <code>origin</code></p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>git.wait-between-attempts</code> (Plugin prop)</p>
+<p class="tableblock">* <code>stubrunner.properties.git.wait-between-attempts</code>  (system prop)</p>
+<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_GIT_WAIT_BETWEEN_ATTEMPTS</code>  (env prop)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">1000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Number of milliseconds to wait between attempts to push the commits to <code>origin</code></p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="howto"><a class="anchor" href="#howto"></a><a class="link" href="#howto">8. &#8220;How-to&#8221; Guides</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>This section provides answers to some common &#8220;how do I do that&#8230;&#8203;&#8221; questions
+that often arise when using Spring Cloud Contract. Its coverage is not exhaustive, but it
+does cover quite a lot.</p>
+</div>
+<div class="paragraph">
+<p>If you have a specific problem that we do not cover here, you might want to check out
+<a href="https://stackoverflow.com/tags/spring-cloud-contract">stackoverflow.com</a> to see if someone has
+already provided an answer. Stack Overflow is also a great place to ask new questions (please use
+the <code>spring-cloud-contract</code> tag).</p>
+</div>
+<div class="paragraph">
+<p>We are also more than happy to extend this section. If you want to add a &#8220;how-to&#8221;,
+send us a <a href="https://github.com/spring-cloud/spring-cloud-contract/tree/master">pull request</a>.</p>
+</div>
+<div class="sect2">
+<h3 id="why-spring-cloud-contract"><a class="anchor" href="#why-spring-cloud-contract"></a><a class="link" href="#why-spring-cloud-contract">8.1. Why use Spring Cloud Contract?</a></h3>
+<div class="paragraph">
+<p>Spring Cloud Contract works great in a polyglot environment. This project has a lot of
+really interesting features. Quite a few of these features definitely make
+Spring Cloud Contract Verifier stand out on the market of Consumer Driven Contract
+(CDC) tooling. The most interesting features include the following:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Ability to do CDC with messaging.</p>
+</li>
+<li>
+<p>Clear and easy to use, statically typed DSL.</p>
+</li>
+<li>
+<p>Ability to copy-paste your current JSON file to the contract and only edit its elements.</p>
+</li>
+<li>
+<p>Automatic generation of tests from the defined Contract.</p>
+</li>
+<li>
+<p>Stub Runner functionality: The stubs are automatically downloaded at runtime from Nexus/Artifactory.</p>
+</li>
+<li>
+<p>Spring Cloud integration: No discovery service is needed for integration tests.</p>
+</li>
+<li>
+<p>Spring Cloud Contract integrates with Pact and provides easy hooks to extend its functionality.</p>
+</li>
+<li>
+<p>Ability to add support for any language &amp; framework through Docker.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-not-write-contracts-in-groovy"><a class="anchor" href="#how-to-not-write-contracts-in-groovy"></a><a class="link" href="#how-to-not-write-contracts-in-groovy">8.2. How Can I Write Contracts in a Language Other than Groovy?</a></h3>
+<div class="paragraph">
+<p>You can write a contract in YAML. See <a href="#contract-dsl">this section</a> for more information.</p>
+</div>
+<div class="paragraph">
+<p>We are working on allowing more ways of describing the contracts. You can check the <a href="https://github.com/spring-cloud/spring-cloud-contract/issues/">github-issues</a> for more information.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-provide-dynamic-values"><a class="anchor" href="#how-to-provide-dynamic-values"></a><a class="link" href="#how-to-provide-dynamic-values">8.3. How Can I Provide Dynamic Values to a Contract?</a></h3>
+<div class="paragraph">
+<p>One of the biggest challenges related to stubs is their reusability. Only if they can be widely used can they serve their purpose.
+The hard-coded values (such as dates and IDs) of request and response elements generally make that difficult.
+Consider the following JSON request:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
+    "time" : "2016-10-10 20:10:15",
+    "id" : "9febab1c-6f36-4a0b-88d6-3b6a6d81cd4a",
+    "body" : "foo"
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Now consider the following JSON response:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
+    "time" : "2016-10-10 21:10:15",
+    "id" : "c4231e1f-3ca9-48d3-b7e7-567d55f0d051",
+    "body" : "bar"
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Imagine the pain required to set the proper value of the <code>time</code> field (assume that this content is generated by the
+database) by changing the clock in the system or by providing stub implementations of data providers. The same is related
+to the field called <code>id</code>. You could create a stubbed implementation of UUID generator, but doing so makes little sense.</p>
+</div>
+<div class="paragraph">
+<p>So, as a consumer, you want to send a request that matches any form of a time or any UUID. That way, your system
+works as usual, generating data without you having to stub out anything. Assume that, in case of the aforementioned
+JSON, the most important part is the <code>body</code> field. You can focus on that and provide matching for other fields. In other words,
+you would like the stub to work as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
+    "time" : "SOMETHING THAT MATCHES TIME",
+    "id" : "SOMETHING THAT MATCHES UUID",
+    "body" : "foo"
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>As far as the response goes, as a consumer, you need a concrete value on which you can operate.
+Consequently, the following JSON is valid:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
+    "time" : "2016-10-10 21:10:15",
+    "id" : "c4231e1f-3ca9-48d3-b7e7-567d55f0d051",
+    "body" : "bar"
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>In the previous sections, we generated tests from contracts. So, from the producer&#8217;s side, the situation looks
+much different. We parse the provided contract, and, in the test, we want to send a real request to your endpoints.
+So, for the case of a producer for the request, we cannot have any sort of matching. We need concrete values on which the
+producer&#8217;s backend can work. Consequently, the following JSON would be valid:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
+    "time" : "2016-10-10 20:10:15",
+    "id" : "9febab1c-6f36-4a0b-88d6-3b6a6d81cd4a",
+    "body" : "foo"
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>On the other hand, from the point of view of the validity of the contract, the response does not necessarily have to
+contain concrete values for <code>time</code> or <code>id</code>. Suppose you generate those on the producer side. Again, you
+have to do a lot of stubbing to ensure that you always return the same values. That is why, from the producer&#8217;s side
+you might want the following response:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
+    "time" : "SOMETHING THAT MATCHES TIME",
+    "id" : "SOMETHING THAT MATCHES UUID",
+    "body" : "bar"
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>How can you then provide a matcher for the consumer and a concrete value for the producer (and the opposite at some other time)?
+Spring Cloud Contract lets you provide a dynamic value. That means that it can differ for both
+sides of the communication.</p>
+</div>
+<div class="paragraph">
+<p>You can read more about this in the <a href="#contract-dsl">Contract DSL</a> section.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+Read the <a href="https://groovy-lang.org/json.html">Groovy docs related to JSON</a> to understand how to
+properly structure the request and response bodies.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-do-stubs-versioning"><a class="anchor" href="#how-to-do-stubs-versioning"></a><a class="link" href="#how-to-do-stubs-versioning">8.4. How to Do Stubs versioning?</a></h3>
+<div class="paragraph">
+<p>This section covers version of the stubs, which you can handle in a number of different ways:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="#how-to-api-versioning">API Versioning</a></p>
+</li>
+<li>
+<p><a href="#how-to-jar-versioning">JAR versioning</a></p>
+</li>
+<li>
+<p><a href="#how-to-dev-or-prod-stubs">Development or Production Stubs</a></p>
+</li>
+</ul>
+</div>
+<div class="sect3">
+<h4 id="how-to-api-versioning"><a class="anchor" href="#how-to-api-versioning"></a><a class="link" href="#how-to-api-versioning">8.4.1. API Versioning</a></h4>
+<div class="paragraph">
+<p>What does versioning really mean? If you refer to the API version, there are
+different approaches:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Use hypermedia links and do not version your API by any means</p>
+</li>
+<li>
+<p>Pass the version through headers and URLs</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>We do not try to answer the question of which approach is better. You should pick whatever
+suits your needs and lets you generate business value.</p>
+</div>
+<div class="paragraph">
+<p>Assume that you do version your API. In that case, you should provide as many contracts with as many versions as you support.
+You can create a subfolder for every version or append it to the contract name&#8201;&#8212;&#8201;whatever suits you best.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-jar-versioning"><a class="anchor" href="#how-to-jar-versioning"></a><a class="link" href="#how-to-jar-versioning">8.4.2. JAR versioning</a></h4>
+<div class="paragraph">
+<p>If, by versioning, you mean the version of the JAR that contains the stubs, then there are essentially two main approaches.</p>
+</div>
+<div class="paragraph">
+<p>Assume that you do continuous delivery and deployment, which means that you generate a new version of
+the jar each time you go through the pipeline and that the jar can go to production at any time. For example, your jar version
+looks like the following (because it got built on the 20.10.2016 at 20:15:21) :</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">1.0.0.20161020-201521-RELEASE</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>In that case your, generated stub jar should look like the following:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">1.0.0.20161020-201521-RELEASE-stubs.jar</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>In this case, you should, inside your <code>application.yml</code> or <code>@AutoConfigureStubRunner</code> when
+referencing stubs, provide the latest version of the stubs. You can do that by passing the
+<code>+</code> sign. the following example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(ids = {"com.example:http-server-dsl:+:stubs:8080"})</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>If the versioning, however, is fixed (for example, <code>1.0.4.RELEASE</code> or <code>2.1.1</code>), you have to set the concrete value of the jar
+version. The following example shows how to do so for version 2.1.1:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(ids = {"com.example:http-server-dsl:2.1.1:stubs:8080"})</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-dev-or-prod-stubs"><a class="anchor" href="#how-to-dev-or-prod-stubs"></a><a class="link" href="#how-to-dev-or-prod-stubs">8.4.3. Development or Production Stubs</a></h4>
+<div class="paragraph">
+<p>You can manipulate the classifier to run the tests against current the development version
+of the stubs of other services or the ones that were deployed to production. If you alter
+your build to deploy the stubs with the <code>prod-stubs</code> classifier once you reach production
+deployment, you can run tests in one case with development stubs and one with production stubs.</p>
+</div>
+<div class="paragraph">
+<p>The following example works for tests that use the development version of the stubs:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(ids = {"com.example:http-server-dsl:+:stubs:8080"})</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The following example works for tests that use the production version of stubs:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(ids = {"com.example:http-server-dsl:+:prod-stubs:8080"})</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>You can also pass those values also in properties from your deployment pipeline.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-common-repo-with-contracts"><a class="anchor" href="#how-to-common-repo-with-contracts"></a><a class="link" href="#how-to-common-repo-with-contracts">8.5. How Can I use a Common Repository with Contracts Instead of Storing Them with the Producer?</a></h3>
+<div class="paragraph">
+<p>Another way of storing contracts, rather than having them with the producer, is to keep
+them in a common place. This situation can be related to security issues (where the
+consumers cannot clone the producer&#8217;s code). Also if you keep contracts in a single place,
+then you, as a producer, know how many consumers you have and which consumer you may break
+with your local changes.</p>
+</div>
+<div class="sect3">
+<h4 id="how-to-repo-structure"><a class="anchor" href="#how-to-repo-structure"></a><a class="link" href="#how-to-repo-structure">8.5.1. Repo Structure</a></h4>
+<div class="paragraph">
+<p>Assume that we have a producer with coordinates of <code>com.example:server</code> and three
+consumers: <code>client1</code>, <code>client2</code>, and <code>client3</code>. Then, in the repository with common
+contracts, you could have the following setup (which you can check out
+<a href="https://github.com/spring-cloud/spring-cloud-contract/tree/master/samples/standalone/contracts">here</a>).
+The following listing shows such a structure:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── com
+│   └── example
+│       └── server
+│           ├── client1
+│           │   └── expectation.groovy
+│           ├── client2
+│           │   └── expectation.groovy
+│           ├── client3
+│           │   └── expectation.groovy
+│           └── pom.xml
+├── mvnw
+├── mvnw.cmd
+├── pom.xml
+└── src
+    └── assembly
+        └── contracts.xml</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>As you can see under the slash-delimited <code>groupid/artifact id</code> folder (<code>com/example/server</code>) you have
+expectations of the three consumers (<code>client1</code>, <code>client2</code>, and <code>client3</code>). Expectations are the standard Groovy DSL
+contract files, as described throughout this documentation. This repository has to produce a JAR file that maps
+one-to-one to the contents of the repository.</p>
+</div>
+<div class="paragraph">
+<p>The following example shows a <code>pom.xml</code> inside the <code>server</code> folder:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;project xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xmlns="http://maven.apache.org/POM/4.0.0"
+         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd"&gt;
+    &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
+
+    &lt;groupId&gt;com.example&lt;/groupId&gt;
+    &lt;artifactId&gt;server&lt;/artifactId&gt;
+    &lt;version&gt;0.0.1&lt;/version&gt;
+
+    &lt;name&gt;Server Stubs&lt;/name&gt;
+    &lt;description&gt;POM used to install locally stubs for consumer side&lt;/description&gt;
+
+    &lt;parent&gt;
+        &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
+        &lt;artifactId&gt;spring-boot-starter-parent&lt;/artifactId&gt;
+        &lt;version&gt;2.3.0.M4&lt;/version&gt;
+        &lt;relativePath/&gt;
+    &lt;/parent&gt;
+
+    &lt;properties&gt;
+        &lt;project.build.sourceEncoding&gt;UTF-8&lt;/project.build.sourceEncoding&gt;
+        &lt;java.version&gt;1.8&lt;/java.version&gt;
+        &lt;spring-cloud-contract.version&gt;3.0.0-SNAPSHOT&lt;/spring-cloud-contract.version&gt;
+        &lt;spring-cloud-release.version&gt;2020.0.0-SNAPSHOT&lt;/spring-cloud-release.version&gt;
+        &lt;excludeBuildFolders&gt;true&lt;/excludeBuildFolders&gt;
+    &lt;/properties&gt;
+
+    &lt;dependencyManagement&gt;
+        &lt;dependencies&gt;
+            &lt;dependency&gt;
+                &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+                &lt;artifactId&gt;spring-cloud-dependencies&lt;/artifactId&gt;
+                &lt;version&gt;${spring-cloud-release.version}&lt;/version&gt;
+                &lt;type&gt;pom&lt;/type&gt;
+                &lt;scope&gt;import&lt;/scope&gt;
+            &lt;/dependency&gt;
+        &lt;/dependencies&gt;
+    &lt;/dependencyManagement&gt;
+
+    &lt;build&gt;
+        &lt;plugins&gt;
+            &lt;plugin&gt;
+                &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+                &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+                &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+                &lt;extensions&gt;true&lt;/extensions&gt;
+                &lt;configuration&gt;
+                    &lt;!-- By default it would search under src/test/resources/ --&gt;
+                    &lt;contractsDirectory&gt;${project.basedir}&lt;/contractsDirectory&gt;
+                &lt;/configuration&gt;
+            &lt;/plugin&gt;
+        &lt;/plugins&gt;
+    &lt;/build&gt;
+
+    &lt;repositories&gt;
+        &lt;repository&gt;
+            &lt;id&gt;spring-snapshots&lt;/id&gt;
+            &lt;name&gt;Spring Snapshots&lt;/name&gt;
+            &lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
+            &lt;snapshots&gt;
+                &lt;enabled&gt;true&lt;/enabled&gt;
+            &lt;/snapshots&gt;
+        &lt;/repository&gt;
+        &lt;repository&gt;
+            &lt;id&gt;spring-milestones&lt;/id&gt;
+            &lt;name&gt;Spring Milestones&lt;/name&gt;
+            &lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
+            &lt;snapshots&gt;
+                &lt;enabled&gt;false&lt;/enabled&gt;
+            &lt;/snapshots&gt;
+        &lt;/repository&gt;
+        &lt;repository&gt;
+            &lt;id&gt;spring-releases&lt;/id&gt;
+            &lt;name&gt;Spring Releases&lt;/name&gt;
+            &lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
+            &lt;snapshots&gt;
+                &lt;enabled&gt;false&lt;/enabled&gt;
+            &lt;/snapshots&gt;
+        &lt;/repository&gt;
+    &lt;/repositories&gt;
+    &lt;pluginRepositories&gt;
+        &lt;pluginRepository&gt;
+            &lt;id&gt;spring-snapshots&lt;/id&gt;
+            &lt;name&gt;Spring Snapshots&lt;/name&gt;
+            &lt;url&gt;https://repo.spring.io/snapshot&lt;/url&gt;
+            &lt;snapshots&gt;
+                &lt;enabled&gt;true&lt;/enabled&gt;
+            &lt;/snapshots&gt;
+        &lt;/pluginRepository&gt;
+        &lt;pluginRepository&gt;
+            &lt;id&gt;spring-milestones&lt;/id&gt;
+            &lt;name&gt;Spring Milestones&lt;/name&gt;
+            &lt;url&gt;https://repo.spring.io/milestone&lt;/url&gt;
+            &lt;snapshots&gt;
+                &lt;enabled&gt;false&lt;/enabled&gt;
+            &lt;/snapshots&gt;
+        &lt;/pluginRepository&gt;
+        &lt;pluginRepository&gt;
+            &lt;id&gt;spring-releases&lt;/id&gt;
+            &lt;name&gt;Spring Releases&lt;/name&gt;
+            &lt;url&gt;https://repo.spring.io/release&lt;/url&gt;
+            &lt;snapshots&gt;
+                &lt;enabled&gt;false&lt;/enabled&gt;
+            &lt;/snapshots&gt;
+        &lt;/pluginRepository&gt;
+    &lt;/pluginRepositories&gt;
+
+&lt;/project&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>There are no dependencies other than the Spring Cloud Contract Maven Plugin.
+Those pom files are necessary for the consumer side to run <code>mvn clean install -DskipTests</code> to locally install
+the stubs of the producer project.</p>
+</div>
+<div class="paragraph">
+<p>The <code>pom.xml</code> in the root folder can look like the following:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;project xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xmlns="http://maven.apache.org/POM/4.0.0"
+         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd"&gt;
+    &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
+
+    &lt;groupId&gt;com.example.standalone&lt;/groupId&gt;
+    &lt;artifactId&gt;contracts&lt;/artifactId&gt;
+    &lt;version&gt;0.0.1&lt;/version&gt;
+
+    &lt;name&gt;Contracts&lt;/name&gt;
+    &lt;description&gt;Contains all the Spring Cloud Contracts, well, contracts. JAR used by the
+        producers to generate tests and stubs
+    &lt;/description&gt;
+
+    &lt;properties&gt;
+        &lt;project.build.sourceEncoding&gt;UTF-8&lt;/project.build.sourceEncoding&gt;
+    &lt;/properties&gt;
+
+    &lt;build&gt;
+        &lt;plugins&gt;
+            &lt;plugin&gt;
+                &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
+                &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
+                &lt;executions&gt;
+                    &lt;execution&gt;
+                        &lt;id&gt;contracts&lt;/id&gt;
+                        &lt;phase&gt;prepare-package&lt;/phase&gt;
+                        &lt;goals&gt;
+                            &lt;goal&gt;single&lt;/goal&gt;
+                        &lt;/goals&gt;
+                        &lt;configuration&gt;
+                            &lt;attach&gt;true&lt;/attach&gt;
+                            &lt;descriptor&gt;${basedir}/src/assembly/contracts.xml&lt;/descriptor&gt;
+                            &lt;!-- If you want an explicit classifier remove the following line --&gt;
+                            &lt;appendAssemblyId&gt;false&lt;/appendAssemblyId&gt;
+                        &lt;/configuration&gt;
+                    &lt;/execution&gt;
+                &lt;/executions&gt;
+            &lt;/plugin&gt;
+        &lt;/plugins&gt;
+    &lt;/build&gt;
+
+&lt;/project&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>It uses the assembly plugin to build the JAR with all the contracts. The following example
+shows such a setup:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;assembly xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+          xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3"
+          xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3 https://maven.apache.org/xsd/assembly-1.1.3.xsd"&gt;
+    &lt;id&gt;project&lt;/id&gt;
+    &lt;formats&gt;
+        &lt;format&gt;jar&lt;/format&gt;
+    &lt;/formats&gt;
+    &lt;includeBaseDirectory&gt;false&lt;/includeBaseDirectory&gt;
+    &lt;fileSets&gt;
+        &lt;fileSet&gt;
+            &lt;directory&gt;${project.basedir}&lt;/directory&gt;
+            &lt;outputDirectory&gt;/&lt;/outputDirectory&gt;
+            &lt;useDefaultExcludes&gt;true&lt;/useDefaultExcludes&gt;
+            &lt;excludes&gt;
+                &lt;exclude&gt;**/${project.build.directory}/**&lt;/exclude&gt;
+                &lt;exclude&gt;mvnw&lt;/exclude&gt;
+                &lt;exclude&gt;mvnw.cmd&lt;/exclude&gt;
+                &lt;exclude&gt;.mvn/**&lt;/exclude&gt;
+                &lt;exclude&gt;src/**&lt;/exclude&gt;
+            &lt;/excludes&gt;
+        &lt;/fileSet&gt;
+    &lt;/fileSets&gt;
+&lt;/assembly&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-workflow"><a class="anchor" href="#how-to-workflow"></a><a class="link" href="#how-to-workflow">8.5.2. Workflow</a></h4>
+<div class="paragraph">
+<p>The workflow assumes that Spring Cloud Contract is set up both on the consumer and on the
+producer side. There is also the proper plugin setup in the common repository with
+contracts. The CI jobs are set for a common repository to build an artifact of all
+contracts and upload it to Nexus/Artifactory. The following image shows the UML for this
+workflow:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/how-to-common-repo.png" alt="how to common repo" width="1588" height="1421">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-workflow-consumer"><a class="anchor" href="#how-to-workflow-consumer"></a><a class="link" href="#how-to-workflow-consumer">8.5.3. Consumer</a></h4>
+<div class="paragraph">
+<p>When the consumer wants to work on the contracts offline, instead of cloning the producer
+code, the consumer team clones the common repository, goes to the required producer&#8217;s
+folder (for example, <code>com/example/server</code>) and runs <code>mvn clean install -DskipTests</code> to
+locally install the stubs converted from the contracts.</p>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+You need to have <a href="https://maven.apache.org/download.cgi">Maven installed locally</a>
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-workflow-producer"><a class="anchor" href="#how-to-workflow-producer"></a><a class="link" href="#how-to-workflow-producer">8.5.4. Producer</a></h4>
+<div class="paragraph">
+<p>As a producer, you can to alter the Spring Cloud Contract Verifier to provide the URL and
+the dependency of the JAR that contains the contracts, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;configuration&gt;
+        &lt;contractsMode&gt;REMOTE&lt;/contractsMode&gt;
+        &lt;contractsRepositoryUrl&gt;
+            https://link/to/your/nexus/or/artifactory/or/sth
+        &lt;/contractsRepositoryUrl&gt;
+        &lt;contractDependency&gt;
+            &lt;groupId&gt;com.example.standalone&lt;/groupId&gt;
+            &lt;artifactId&gt;contracts&lt;/artifactId&gt;
+        &lt;/contractDependency&gt;
+    &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>With this setup, the JAR with a groupid of <code>com.example.standalone</code> and artifactid
+<code>contracts</code> is downloaded from <code><a href="https://link/to/your/nexus/or/artifactory/or/sth" class="bare">link/to/your/nexus/or/artifactory/or/sth</a></code>. It is
+then unpacked in a local temporary folder, and the contracts present in
+<code>com/example/server</code> are picked as the ones used to generate the tests and the stubs. Due
+to this convention, the producer team can know which consumer teams will be broken when
+some incompatible changes are made.</p>
+</div>
+<div class="paragraph">
+<p>The rest of the flow looks the same.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-define-messaging-contracts-per-topic"><a class="anchor" href="#how-to-define-messaging-contracts-per-topic"></a><a class="link" href="#how-to-define-messaging-contracts-per-topic">8.5.5. How Can I Define Messaging Contracts per Topic Rather than per Producer?</a></h4>
+<div class="paragraph">
+<p>To avoid messaging contracts duplication in the common repository, when a few producers write messages to one topic,
+we could create a structure in which the REST contracts are placed in a folder per producer and messaging
+contracts are placed in the folder per topic.</p>
+</div>
+<div class="sect4">
+<h5 id="how-to-define-messaging-contracts-per-topic-maven"><a class="anchor" href="#how-to-define-messaging-contracts-per-topic-maven"></a><a class="link" href="#how-to-define-messaging-contracts-per-topic-maven">For Maven Projects</a></h5>
+<div class="paragraph">
+<p>To make it possible to work on the producer side, we should specify an inclusion pattern for
+filtering common repository jar files by messaging topics we are interested in. The
+<code>includedFiles</code> property of the Maven Spring Cloud Contract plugin
+lets us do so. Also, <code>contractsPath</code> need to be specified, since the default path would be
+the common repository <code>groupid/artifactid</code>. The following example shows a Maven
+plugin for Spring Cloud Contract:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+   &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+   &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+   &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+   &lt;configuration&gt;
+      &lt;contractsMode&gt;REMOTE&lt;/contractsMode&gt;
+      &lt;contractsRepositoryUrl&gt;https://link/to/your/nexus/or/artifactory/or/sth&lt;/contractsRepositoryUrl&gt;
+      &lt;contractDependency&gt;
+         &lt;groupId&gt;com.example&lt;/groupId&gt;
+         &lt;artifactId&gt;common-repo-with-contracts&lt;/artifactId&gt;
+         &lt;version&gt;+&lt;/version&gt;
+      &lt;/contractDependency&gt;
+      &lt;contractsPath&gt;/&lt;/contractsPath&gt;
+      &lt;baseClassMappings&gt;
+         &lt;baseClassMapping&gt;
+            &lt;contractPackageRegex&gt;.*messaging.*&lt;/contractPackageRegex&gt;
+            &lt;baseClassFQN&gt;com.example.services.MessagingBase&lt;/baseClassFQN&gt;
+         &lt;/baseClassMapping&gt;
+         &lt;baseClassMapping&gt;
+            &lt;contractPackageRegex&gt;.*rest.*&lt;/contractPackageRegex&gt;
+            &lt;baseClassFQN&gt;com.example.services.TestBase&lt;/baseClassFQN&gt;
+         &lt;/baseClassMapping&gt;
+      &lt;/baseClassMappings&gt;
+      &lt;includedFiles&gt;
+         &lt;includedFile&gt;**/${project.artifactId}/**&lt;/includedFile&gt;
+         &lt;includedFile&gt;**/${first-topic}/**&lt;/includedFile&gt;
+         &lt;includedFile&gt;**/${second-topic}/**&lt;/includedFile&gt;
+      &lt;/includedFiles&gt;
+   &lt;/configuration&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+Many of the values in the preceding Maven plugin can be changed. We included it for
+illustration purposes rather than trying to provide a &#8220;typical&#8221; example.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect4">
+<h5 id="how-to-define-messaging-contracts-per-topic-gradle"><a class="anchor" href="#how-to-define-messaging-contracts-per-topic-gradle"></a><a class="link" href="#how-to-define-messaging-contracts-per-topic-gradle">For Gradle Projects</a></h5>
+<div class="paragraph">
+<p>To work with a Gradle project:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Add a custom configuration for the common repository dependency, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">ext {
+    contractsGroupId = "com.example"
+    contractsArtifactId = "common-repo"
+    contractsVersion = "1.2.3"
+}
+
+configurations {
+    contracts {
+        transitive = false
+    }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Add the common repository dependency to your classpath, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">dependencies {
+    contracts "${contractsGroupId}:${contractsArtifactId}:${contractsVersion}"
+    testCompile "${contractsGroupId}:${contractsArtifactId}:${contractsVersion}"
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Download the dependency to an appropriate folder, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">task getContracts(type: Copy) {
+    from configurations.contracts
+    into new File(project.buildDir, "downloadedContracts")
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Unzip the JAR, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">task unzipContracts(type: Copy) {
+    def zipFile = new File(project.buildDir, "downloadedContracts/${contractsArtifactId}-${contractsVersion}.jar")
+    def outputDir = file("${buildDir}/unpackedContracts")
+
+    from zipTree(zipFile)
+    into outputDir
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Cleanup unused contracts, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">task deleteUnwantedContracts(type: Delete) {
+    delete fileTree(dir: "${buildDir}/unpackedContracts",
+        include: "**/*",
+        excludes: [
+            "**/${project.name}/**"",
+            "**/${first-topic}/**",
+            "**/${second-topic}/**"])
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Create task dependencies, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">unzipContracts.dependsOn("getContracts")
+deleteUnwantedContracts.dependsOn("unzipContracts")
+build.dependsOn("deleteUnwantedContracts")</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+<li>
+<p>Configure the plugin by specifying the directory that contains the contracts, by setting
+the <code>contractsDslDir</code> property, as follows:</p>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
+    contractsDslDir = new File("${buildDir}/unpackedContracts")
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</li>
+</ol>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-use-git-as-storage"><a class="anchor" href="#how-to-use-git-as-storage"></a><a class="link" href="#how-to-use-git-as-storage">8.6. How Can I Use Git as the Storage for Contracts and Stubs?</a></h3>
+<div class="paragraph">
+<p>In the polyglot world, there are languages that do not use binary storages, as
+Artifactory or Nexus do. Starting from Spring Cloud Contract version 2.0.0, we provide
+mechanisms to store contracts and stubs in a SCM (Source Control Management) repository. Currently, the
+only supported SCM is Git.</p>
+</div>
+<div class="paragraph">
+<p>The repository would have to have the following setup
+(which you can checkout from <a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x/contracts_git/">here</a>):</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code>.
+└── META-INF
+    └── com.example
+        └── beer-api-producer-git
+            └── 0.0.1-SNAPSHOT
+                ├── contracts
+                │   └── beer-api-consumer
+                │       ├── messaging
+                │       │   ├── shouldSendAcceptedVerification.groovy
+                │       │   └── shouldSendRejectedVerification.groovy
+                │       └── rest
+                │           ├── shouldGrantABeerIfOldEnough.groovy
+                │           └── shouldRejectABeerIfTooYoung.groovy
+                └── mappings
+                    └── beer-api-consumer
+                        └── rest
+                            ├── shouldGrantABeerIfOldEnough.json
+                            └── shouldRejectABeerIfTooYoung.json</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Under the <code>META-INF</code> folder:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>We group applications by <code>groupId</code> (such as <code>com.example</code>).</p>
+</li>
+<li>
+<p>Each application is represented by its <code>artifactId</code> (for example, <code>beer-api-producer-git</code>).</p>
+</li>
+<li>
+<p>Next, each application is organized by its version (such as <code>0.0.1-SNAPSHOT</code>). Starting
+from Spring Cloud Contract version <code>2.1.0</code>, you can specify the versions as follows
+(assuming that your versions follow semantic versioning):</p>
+<div class="ulist">
+<ul>
+<li>
+<p><code>+</code> or <code>latest</code>: To find the latest version of your stubs (assuming that the snapshots
+are always the latest artifact for a given revision number). That means:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>If you have <code>1.0.0.RELEASE</code>, <code>2.0.0.BUILD-SNAPSHOT</code>, and <code>2.0.0.RELEASE</code>, we assume
+that the latest is <code>2.0.0.BUILD-SNAPSHOT</code>.</p>
+</li>
+<li>
+<p>If you have <code>1.0.0.RELEASE</code> and <code>2.0.0.RELEASE</code>, we assume that the latest is <code>2.0.0.RELEASE</code>.</p>
+</li>
+<li>
+<p>If you have a version called <code>latest</code> or <code>+</code>, we will pick that folder.</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p><code>release</code>: To find the latest release version of your stubs. That means:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>If you have <code>1.0.0.RELEASE</code>, <code>2.0.0.BUILD-SNAPSHOT</code>, and <code>2.0.0.RELEASE</code> we assume
+that the latest is <code>2.0.0.RELEASE</code>.</p>
+</li>
+<li>
+<p>If you have a version called <code>release</code>, we pick that folder.</p>
+</li>
+</ul>
+</div>
+</li>
+</ul>
+</div>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Finally, there are two folders:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>contracts</code>: The good practice is to store the contracts required by each
+consumer in the folder with the consumer name (such as <code>beer-api-consumer</code>). That way, you
+can use the <code>stubs-per-consumer</code> feature. Further directory structure is arbitrary.</p>
+</li>
+<li>
+<p><code>mappings</code>: The Maven or Gradle Spring Cloud Contract plugins push
+the stub server mappings in this folder. On the consumer side, Stub Runner scans this folder
+to start stub servers with stub definitions. The folder structure is a copy
+of the one created in the <code>contracts</code> subfolder.</p>
+</li>
+</ul>
+</div>
+<div class="sect3">
+<h4 id="how-to-protocol-convention"><a class="anchor" href="#how-to-protocol-convention"></a><a class="link" href="#how-to-protocol-convention">8.6.1. Protocol Convention</a></h4>
+<div class="paragraph">
+<p>To control the type and location of the source of contracts (whether
+binary storage or an SCM repository), you can use the protocol in the URL of
+the repository. Spring Cloud Contract iterates over registered protocol resolvers
+and tries to fetch the contracts (by using a plugin) or stubs (from Stub Runner).</p>
+</div>
+<div class="paragraph">
+<p>For the SCM functionality, currently, we support the Git repository. To use it,
+in the property where the repository URL needs to be placed, you have to prefix
+the connection URL with <code>git://</code>. The following listing shows some examples:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code>git://file:///foo/bar
+git://https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git
+git://git@github.com:spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-protocol-convention-producer"><a class="anchor" href="#how-to-protocol-convention-producer"></a><a class="link" href="#how-to-protocol-convention-producer">8.6.2. Producer</a></h4>
+<div class="paragraph">
+<p>For the producer, to use the SCM (Source Control Management) approach, we can reuse the
+same mechanism we use for external contracts. We route Spring Cloud Contract
+to use the SCM implementation from the URL that starts with
+the <code>git://</code> protocol.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+You have to manually add the <code>pushStubsToScm</code>
+goal in Maven or execute (bind) the <code>pushStubsToScm</code> task in
+Gradle. We do not push stubs to the <code>origin</code> of your git
+repository.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The following listing includes the relevant parts both Maven and Gradle build files:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;!-- Base class mappings etc. --&gt;
+
+        &lt;!-- We want to pick contracts from a Git repository --&gt;
+        &lt;contractsRepositoryUrl&gt;git://https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git&lt;/contractsRepositoryUrl&gt;
+
+        &lt;!-- We reuse the contract dependency section to set up the path
+        to the folder that contains the contract definitions. In our case the
+        path will be /groupId/artifactId/version/contracts --&gt;
+        &lt;contractDependency&gt;
+            &lt;groupId&gt;${project.groupId}&lt;/groupId&gt;
+            &lt;artifactId&gt;${project.artifactId}&lt;/artifactId&gt;
+            &lt;version&gt;${project.version}&lt;/version&gt;
+        &lt;/contractDependency&gt;
+
+        &lt;!-- The contracts mode can't be classpath --&gt;
+        &lt;contractsMode&gt;REMOTE&lt;/contractsMode&gt;
+    &lt;/configuration&gt;
+    &lt;executions&gt;
+        &lt;execution&gt;
+            &lt;phase&gt;package&lt;/phase&gt;
+            &lt;goals&gt;
+                &lt;!-- By default we will not push the stubs back to SCM,
+                you have to explicitly add it as a goal --&gt;
+                &lt;goal&gt;pushStubsToScm&lt;/goal&gt;
+            &lt;/goals&gt;
+        &lt;/execution&gt;
+    &lt;/executions&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
+    // We want to pick contracts from a Git repository
+    contractDependency {
+        stringNotation = "${project.group}:${project.name}:${project.version}"
+    }
+    /*
+    We reuse the contract dependency section to set up the path
+    to the folder that contains the contract definitions. In our case the
+    path will be /groupId/artifactId/version/contracts
+     */
+    contractRepository {
+        repositoryUrl = "git://https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git"
+    }
+    // The mode can't be classpath
+    contractsMode = "REMOTE"
+    // Base class mappings etc.
+}
+
+/*
+In this scenario we want to publish stubs to SCM whenever
+the `publish` task is executed
+*/
+publish.dependsOn("publishStubsToScm")</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>It is also possible to further customise the <code>publishStubsToScm</code> gradle task. In the following example,
+the task is customised to pick contracts from a local git repository:</p>
+</div>
+<div class="listingblock secondary">
+<div class="title">gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">publishStubsToScm {
+    // We want to modify the default set up of the plugin when publish stubs to scm is called
+    // We want to pick contracts from a Git repository
+    contractDependency {
+        stringNotation = "${project.group}:${project.name}:${project.version}"
+    }
+    /*
+    We reuse the contract dependency section to set up the path
+    to the folder that contains the contract definitions. In our case the
+    path will be /groupId/artifactId/version/contracts
+     */
+    contractRepository {
+        repositoryUrl = "git://file://${new File(project.rootDir, "../target")}/contract_empty_git/"
+    }
+    // We set the contracts mode to `LOCAL`
+    contractsMode = "LOCAL"
+    }</code></pre>
+</div>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">IMPORTANT</dt>
+<dd>
+<p>Starting with <code>2.3.0.RELEASE</code> the <code>customize{}</code> closure previously used for the
+<code>publishStubsToScm</code> customization is no longer available. The settings should be applied directly
+within the <code>publishStubsToScm</code> closure as in the example above.</p>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>With such a setup:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>A git project is cloned to a temporary directory</p>
+</li>
+<li>
+<p>The SCM stub downloader goes to <code>META-INF/groupId/artifactId/version/contracts</code> folder
+to find contracts. For example, for <code>com.example:foo:1.0.0</code>, the path would be
+<code>META-INF/com.example/foo/1.0.0/contracts</code>.</p>
+</li>
+<li>
+<p>Tests are generated from the contracts.</p>
+</li>
+<li>
+<p>Stubs are created from the contracts.</p>
+</li>
+<li>
+<p>Once the tests pass, the stubs are committed in the cloned repository.</p>
+</li>
+<li>
+<p>Finally, a push is sent to that repo&#8217;s <code>origin</code>.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-protocol-convention-producer-with-contracts-stored-locally"><a class="anchor" href="#how-to-protocol-convention-producer-with-contracts-stored-locally"></a><a class="link" href="#how-to-protocol-convention-producer-with-contracts-stored-locally">8.6.3. Producer with Contracts Stored Locally</a></h4>
+<div class="paragraph">
+<p>Another option to use the SCM as the destination for stubs and contracts is to store the
+contracts locally, with the producer, and only push the contracts and the stubs to SCM.
+The following listing shows the setup required to achieve this with Maven and Gradle:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;!-- In the default configuration, we want to use the contracts stored locally --&gt;
+    &lt;configuration&gt;
+        &lt;baseClassMappings&gt;
+            &lt;baseClassMapping&gt;
+                &lt;contractPackageRegex&gt;.*messaging.*&lt;/contractPackageRegex&gt;
+                &lt;baseClassFQN&gt;com.example.BeerMessagingBase&lt;/baseClassFQN&gt;
+            &lt;/baseClassMapping&gt;
+            &lt;baseClassMapping&gt;
+                &lt;contractPackageRegex&gt;.*rest.*&lt;/contractPackageRegex&gt;
+                &lt;baseClassFQN&gt;com.example.BeerRestBase&lt;/baseClassFQN&gt;
+            &lt;/baseClassMapping&gt;
+        &lt;/baseClassMappings&gt;
+        &lt;basePackageForTests&gt;com.example&lt;/basePackageForTests&gt;
+    &lt;/configuration&gt;
+    &lt;executions&gt;
+        &lt;execution&gt;
+            &lt;phase&gt;package&lt;/phase&gt;
+            &lt;goals&gt;
+                &lt;!-- By default we will not push the stubs back to SCM,
+                you have to explicitly add it as a goal --&gt;
+                &lt;goal&gt;pushStubsToScm&lt;/goal&gt;
+            &lt;/goals&gt;
+            &lt;configuration&gt;
+                &lt;!-- We want to pick contracts from a Git repository --&gt;
+                &lt;contractsRepositoryUrl&gt;git://file://${env.ROOT}/target/contract_empty_git/
+                &lt;/contractsRepositoryUrl&gt;
+                &lt;!-- Example of URL via git protocol --&gt;
+                &lt;!--&lt;contractsRepositoryUrl&gt;git://git@github.com:spring-cloud-samples/spring-cloud-contract-samples.git&lt;/contractsRepositoryUrl&gt;--&gt;
+                &lt;!-- Example of URL via http protocol --&gt;
+                &lt;!--&lt;contractsRepositoryUrl&gt;git://https://github.com/spring-cloud-samples/spring-cloud-contract-samples.git&lt;/contractsRepositoryUrl&gt;--&gt;
+                &lt;!-- We reuse the contract dependency section to set up the path
+                to the folder that contains the contract definitions. In our case the
+                path will be /groupId/artifactId/version/contracts --&gt;
+                &lt;contractDependency&gt;
+                    &lt;groupId&gt;${project.groupId}&lt;/groupId&gt;
+                    &lt;artifactId&gt;${project.artifactId}&lt;/artifactId&gt;
+                    &lt;version&gt;${project.version}&lt;/version&gt;
+                &lt;/contractDependency&gt;
+                &lt;!-- The mode can't be classpath --&gt;
+                &lt;contractsMode&gt;LOCAL&lt;/contractsMode&gt;
+            &lt;/configuration&gt;
+        &lt;/execution&gt;
+    &lt;/executions&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">contracts {
+        // Base package for generated tests
+    basePackageForTests = "com.example"
+    baseClassMappings {
+        baseClassMapping(".*messaging.*", "com.example.BeerMessagingBase")
+        baseClassMapping(".*rest.*", "com.example.BeerRestBase")
+    }
+}
+
+/*
+In this scenario we want to publish stubs to SCM whenever
+the `publish` task is executed
+*/
+publishStubsToScm {
+    // We want to modify the default set up of the plugin when publish stubs to scm is called
+    customize {
+        // We want to pick contracts from a Git repository
+        contractDependency {
+            stringNotation = "${project.group}:${project.name}:${project.version}"
+        }
+        /*
+        We reuse the contract dependency section to set up the path
+        to the folder that contains the contract definitions. In our case the
+        path will be /groupId/artifactId/version/contracts
+         */
+        contractRepository {
+            repositoryUrl = "git://file://${new File(project.rootDir, "../target")}/contract_empty_git/"
+        }
+        // The mode can't be classpath
+        contractsMode = "LOCAL"
+    }
+}
+
+publish.dependsOn("publishStubsToScm")
+publishToMavenLocal.dependsOn("publishStubsToScm")</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>With such a setup:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Contracts from the default <code>src/test/resources/contracts</code> directory are picked.</p>
+</li>
+<li>
+<p>Tests are generated from the contracts.</p>
+</li>
+<li>
+<p>Stubs are created from the contracts.</p>
+</li>
+<li>
+<p>Once the tests pass:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>The git project is cloned to a temporary directory.</p>
+</li>
+<li>
+<p>The stubs and contracts are committed in the cloned repository.</p>
+</li>
+</ul>
+</div>
+</li>
+<li>
+<p>Finally, a push is done to that repository&#8217;s <code>origin</code>.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-protocol-convention-contracts-producer-stubs-external"><a class="anchor" href="#how-to-protocol-convention-contracts-producer-stubs-external"></a><a class="link" href="#how-to-protocol-convention-contracts-producer-stubs-external">8.6.4. Keeping Contracts with the Producer and Stubs in an External Repository</a></h4>
+<div class="paragraph">
+<p>You can also keep the contracts in the producer repository but keep the stubs in an external git repository.
+This is most useful when you want to use the base consumer-producer collaboration flow but cannot
+use an artifact repository to store the stubs.</p>
+</div>
+<div class="paragraph">
+<p>To do so, use the usual producer setup and then add the <code>pushStubsToScm</code> goal and set
+<code>contractsRepositoryUrl</code> to the repository where you want to keep the stubs.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-protocol-convention-contracts-producer-stubs-external-consumer"><a class="anchor" href="#how-to-protocol-convention-contracts-producer-stubs-external-consumer"></a><a class="link" href="#how-to-protocol-convention-contracts-producer-stubs-external-consumer">8.6.5. Consumer</a></h4>
+<div class="paragraph">
+<p>On the consumer side, when passing the <code>repositoryRoot</code> parameter,
+either from the <code>@AutoConfigureStubRunner</code> annotation, the
+JUnit rule, JUnit 5 extension, or properties, you can pass the URL of the
+SCM repository, prefixed with the <code>git://</code> protocol. The following example shows how to do so:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@AutoConfigureStubRunner(
+    stubsMode="REMOTE",
+    repositoryRoot="git://https://github.com/spring-cloud-samples/spring-cloud-contract-nodejs-contracts-git.git",
+    ids="com.example:bookstore:0.0.1.RELEASE"
+)</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>With such a setup:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>The git project is cloned to a temporary directory.</p>
+</li>
+<li>
+<p>The SCM stub downloader goes to thje <code>META-INF/groupId/artifactId/version/</code> folder
+to find stub definitions and contracts. For example, for <code>com.example:foo:1.0.0</code>, the path would be
+<code>META-INF/com.example/foo/1.0.0/</code>.</p>
+</li>
+<li>
+<p>Stub servers are started and fed with mappings.</p>
+</li>
+<li>
+<p>Messaging definitions are read and used in the messaging tests.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-use-pact-broker"><a class="anchor" href="#how-to-use-pact-broker"></a><a class="link" href="#how-to-use-pact-broker">8.7. How Can I Use the Pact Broker?</a></h3>
+<div class="paragraph">
+<p>When using <a href="https://pact.io/">Pact</a>, you can use the <a href="https://github.com/pact-foundation/pact_broker">Pact Broker</a>
+to store and share Pact definitions. Starting from Spring Cloud Contract
+2.0.0, you can fetch Pact files from the Pact Broker to generate
+tests and stubs.</p>
+</div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+Pact follows the consumer contract convention. That means
+that the consumer creates the Pact definitions first and then
+shares the files with the Producer. Those expectations are generated
+from the Consumer&#8217;s code and can break the Producer if the expectations
+are not met.
+</td>
+</tr>
+</table>
+</div>
+<div class="sect3">
+<h4 id="how-to-use-pact-broker-pact"><a class="anchor" href="#how-to-use-pact-broker-pact"></a><a class="link" href="#how-to-use-pact-broker-pact">8.7.1. How to Work with Pact</a></h4>
+<div class="paragraph">
+<p>Spring Cloud Contract includes support for the <a href="https://docs.pact.io/">Pact</a> representation of
+contracts up until version 4. Instead of using the DSL, you can use Pact files. In this section, we
+show how to add Pact support for your project. Note, however, that not all functionality is supported.
+Starting with version 3, you can combine multiple matchers for the same element;
+you can use matchers for the body, headers, request and path; and you can use value generators.
+Spring Cloud Contract currently only supports multiple matchers that are combined by using the <code>AND</code> rule logic.
+Next to that, the request and path matchers are skipped during the conversion.
+When using a date, time, or datetime value generator with a given format,
+the given format is skipped and the ISO format is used.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-use-pact-broker-pact-converter"><a class="anchor" href="#how-to-use-pact-broker-pact-converter"></a><a class="link" href="#how-to-use-pact-broker-pact-converter">8.7.2. Pact Converter</a></h4>
+<div class="paragraph">
+<p>In order to properly support the Spring Cloud Contract way of doing messaging
+with Pact, you have to provide some additional meta data entries.</p>
+</div>
+<div class="paragraph">
+<p>To define the destination to which a message gets sent, you have to
+set a <code>metaData</code> entry in the Pact file with the <code>sentTo</code> key equal to the destination to
+ which a message is to be sent (for example, <code>"metaData": { "sentTo": "activemq:output" }</code>).</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-use-pact-broker-pact-contract"><a class="anchor" href="#how-to-use-pact-broker-pact-contract"></a><a class="link" href="#how-to-use-pact-broker-pact-contract">8.7.3. Pact Contract</a></h4>
+<div class="paragraph">
+<p>Spring Cloud Contract can read the Pact JSON definition. You can place the file in the
+<code>src/test/resources/contracts</code> folder. Remember to put the <code>spring-cloud-contract-pact</code> dependency to your classpath. The following example shows such a Pact contract:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-javascript hljs" data-lang="javascript">{
+  "provider": {
+    "name": "Provider"
+  },
+  "consumer": {
+    "name": "Consumer"
+  },
+  "interactions": [
+    {
+      "description": "",
+      "request": {
+        "method": "PUT",
+        "path": "/pactfraudcheck",
+        "headers": {
+          "Content-Type": "application/json"
+        },
+        "body": {
+          "clientId": "1234567890",
+          "loanAmount": 99999
+        },
+        "generators": {
+          "body": {
+            "$.clientId": {
+              "type": "Regex",
+              "regex": "[0-9]{10}"
+            }
+          }
+        },
+        "matchingRules": {
+          "header": {
+            "Content-Type": {
+              "matchers": [
+                {
+                  "match": "regex",
+                  "regex": "application/json.*"
+                }
+              ],
+              "combine": "AND"
+            }
+          },
+          "body": {
+            "$.clientId": {
+              "matchers": [
+                {
+                  "match": "regex",
+                  "regex": "[0-9]{10}"
+                }
+              ],
+              "combine": "AND"
+            }
+          }
+        }
+      },
+      "response": {
+        "status": 200,
+        "headers": {
+          "Content-Type": "application/json"
+        },
+        "body": {
+          "fraudCheckStatus": "FRAUD",
+          "rejection.reason": "Amount too high"
+        },
+        "matchingRules": {
+          "header": {
+            "Content-Type": {
+              "matchers": [
+                {
+                  "match": "regex",
+                  "regex": "application/json.*"
+                }
+              ],
+              "combine": "AND"
+            }
+          },
+          "body": {
+            "$.fraudCheckStatus": {
+              "matchers": [
+                {
+                  "match": "regex",
+                  "regex": "FRAUD"
+                }
+              ],
+              "combine": "AND"
+            }
+          }
+        }
+      }
+    }
+  ],
+  "metadata": {
+    "pact-specification": {
+      "version": "3.0.0"
+    },
+    "pact-jvm": {
+      "version": "3.5.13"
+    }
+  }
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-use-pact-broker-pact-for-producers"><a class="anchor" href="#how-to-use-pact-broker-pact-for-producers"></a><a class="link" href="#how-to-use-pact-broker-pact-for-producers">8.7.4. Pact for Producers</a></h4>
+<div class="paragraph">
+<p>On the producer side, you must add two additional dependencies to your plugin
+configuration. One is the Spring Cloud Contract Pact support, and the other represents
+the current Pact version that you use. The following listing shows how to do so for both
+Maven and Gradle:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml"></code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">// if additional dependencies are needed e.g. for Pact
+classpath "org.springframework.cloud:spring-cloud-contract-pact:${findProperty('verifierVersion') ?: verifierVersion}"</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>When you execute the build of your application, a test and stub is generated. The following
+example shows a test and stub that came from this process:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">test</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Test
+    public void validate_shouldMarkClientAsFraud() throws Exception {
+        // given:
+            MockMvcRequestSpecification request = given()
+                    .header("Content-Type", "application/vnd.fraud.v1+json")
+                    .body("{\"clientId\":\"1234567890\",\"loanAmount\":99999}");
+
+        // when:
+            ResponseOptions response = given().spec(request)
+                    .put("/fraudcheck");
+
+        // then:
+            assertThat(response.statusCode()).isEqualTo(200);
+            assertThat(response.header("Content-Type")).matches("application/vnd\\.fraud\\.v1\\+json.*");
+        // and:
+            DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
+            assertThatJson(parsedJson).field("['rejectionReason']").isEqualTo("Amount too high");
+        // and:
+            assertThat(parsedJson.read("$.fraudCheckStatus", String.class)).matches("FRAUD");
+    }</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">stub</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{
+  "id" : "996ae5ae-6834-4db6-8fac-358ca187ab62",
+  "uuid" : "996ae5ae-6834-4db6-8fac-358ca187ab62",
+  "request" : {
+    "url" : "/fraudcheck",
+    "method" : "PUT",
+    "headers" : {
+      "Content-Type" : {
+        "matches" : "application/vnd\\.fraud\\.v1\\+json.*"
+      }
+    },
+    "bodyPatterns" : [ {
+      "matchesJsonPath" : "$[?(@.['loanAmount'] = 99999)]"
+    }, {
+      "matchesJsonPath" : "$[?(@.clientId =~ /([0-9]{10})/)]"
+    } ]
+  },
+  "response" : {
+    "status" : 200,
+    "body" : "{\"fraudCheckStatus\":\"FRAUD\",\"rejectionReason\":\"Amount too high\"}",
+    "headers" : {
+      "Content-Type" : "application/vnd.fraud.v1+json;charset=UTF-8"
+    },
+    "transformers" : [ "response-template" ]
+  },
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-use-pact-broker-pact-consumers"><a class="anchor" href="#how-to-use-pact-broker-pact-consumers"></a><a class="link" href="#how-to-use-pact-broker-pact-consumers">8.7.5. Pact for Consumers</a></h4>
+<div class="paragraph">
+<p>On the consumer side, you must add two additional dependencies to your project
+dependencies. One is the Spring Cloud Contract Pact support, and the other represents the
+current Pact version that you use. The following listing shows how to do so for both
+Maven and Gradle:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">Maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml"></code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy"></code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="pact-stub-downloader"><a class="anchor" href="#pact-stub-downloader"></a><a class="link" href="#pact-stub-downloader">8.7.6. Communicating with the Pact Broker</a></h4>
+<div class="paragraph">
+<p>Whenever the <code>repositoryRoot</code> property starts with a Pact protocol
+(starts with <code>pact://</code>), the stub downloader tries
+to fetch the Pact contract definitions from the Pact Broker.
+Whatever is set after <code>pact://</code> is parsed as the Pact Broker URL.</p>
+</div>
+<div class="paragraph">
+<p>By setting environment variables, system properties, or properties set
+inside the plugin or contracts repository configuration, you can
+tweak the downloader&#8217;s behavior. The following table describes the
+properties:</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 2. Pact Stub Downloader properties</caption>
+<colgroup>
+<col style="width: 33.3333%;">
+<col style="width: 33.3333%;">
+<col style="width: 33.3334%;">
+</colgroup>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Name of a property</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Default</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Description</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.host</code> (plugin prop)</p>
+<p class="tableblock">* <code>stubrunner.properties.pactbroker.host</code> (system prop)</p>
+<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_HOST</code> (env prop)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Host from URL passed to <code>repositoryRoot</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The URL of the Pact Broker.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.port</code> (plugin prop)</p>
+<p class="tableblock">* <code>stubrunner.properties.pactbroker.port</code> (system prop)</p>
+<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_PORT</code> (env prop)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Port from URL passed to <code>repositoryRoot</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The port of Pact Broker.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.protocol</code> (plugin prop)</p>
+<p class="tableblock">* <code>stubrunner.properties.pactbroker.protocol</code> (system prop)</p>
+<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_PROTOCOL</code> (env prop)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Protocol from URL passed to <code>repositoryRoot</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The protocol of Pact Broker.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.tags</code> (plugin prop)</p>
+<p class="tableblock">* <code>stubrunner.properties.pactbroker.tags</code> (system prop)</p>
+<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_TAGS</code> (env prop)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Version of the stub, or <code>latest</code> if version is <code>+</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The tags that should be used to fetch the stub.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.auth.scheme</code> (plugin prop)</p>
+<p class="tableblock">* <code>stubrunner.properties.pactbroker.auth.scheme</code> (system prop)</p>
+<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_AUTH_SCHEME</code> (env prop)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>Basic</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The kind of authentication that should be used to connect to the Pact Broker.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.auth.username</code> (plugin prop)</p>
+<p class="tableblock">* <code>stubrunner.properties.pactbroker.auth.username</code> (system prop)</p>
+<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_AUTH_USERNAME</code> (env prop)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The username passed to <code>contractsRepositoryUsername</code> (maven) or <code>contractRepository.username</code> (gradle)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The username to use when connecting to the Pact Broker.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.auth.password</code> (plugin prop)</p>
+<p class="tableblock">* <code>stubrunner.properties.pactbroker.auth.password</code> (system prop)</p>
+<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_AUTH_PASSWORD</code> (env prop)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The password passed to <code>contractsRepositoryPassword</code> (maven) or <code>contractRepository.password</code> (gradle)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The password to use when connecting to the Pact Broker.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">* <code>pactbroker.provider-name-with-group-id</code> (plugin prop)</p>
+<p class="tableblock">* <code>stubrunner.properties.pactbroker.provider-name-with-group-id</code> (system prop)</p>
+<p class="tableblock">* <code>STUBRUNNER_PROPERTIES_PACTBROKER_PROVIDER_NAME_WITH_GROUP_ID</code> (env prop)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When <code>true</code>, the provider name is a combination of <code>groupId:artifactId</code>. If <code>false</code>, only <code>artifactId</code> is used.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="how-to-pact-consumer"><a class="anchor" href="#how-to-pact-consumer"></a><a class="link" href="#how-to-pact-consumer">8.7.7. Flow: Consumer Contract approach with Pact Broker | Consumer Side</a></h4>
+<div class="paragraph">
+<p>The consumer uses the Pact framework to generate Pact files. The
+Pact files are sent to the Pact Broker. You can find an example of such a setup
+<a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x/consumer_pact">here</a>.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-pact-producer"><a class="anchor" href="#how-to-pact-producer"></a><a class="link" href="#how-to-pact-producer">8.7.8. Flow: Consumer Contract Approach with Pact Broker on the Producer Side</a></h4>
+<div class="paragraph">
+<p>For the producer to use the Pact files from the Pact Broker, we can reuse the
+same mechanism we use for external contracts. We route Spring Cloud Contract
+to use the Pact implementation with the URL that contains
+the <code>pact://</code> protocol. You can pass the URL to the
+Pact Broker. You can find an example of such a setup
+<a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x/producer_pact">here</a>.
+The following listing shows the configuration details for both Maven and Gradle:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-contract-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+    &lt;extensions&gt;true&lt;/extensions&gt;
+    &lt;configuration&gt;
+        &lt;!-- Base class mappings etc. --&gt;
+
+        &lt;!-- We want to pick contracts from a Git repository --&gt;
+        &lt;contractsRepositoryUrl&gt;pact://http://localhost:8085&lt;/contractsRepositoryUrl&gt;
+
+        &lt;!-- We reuse the contract dependency section to set up the path
+        to the folder that contains the contract definitions. In our case the
+        path will be /groupId/artifactId/version/contracts --&gt;
+        &lt;contractDependency&gt;
+            &lt;groupId&gt;${project.groupId}&lt;/groupId&gt;
+            &lt;artifactId&gt;${project.artifactId}&lt;/artifactId&gt;
+            &lt;!-- When + is passed, a latest tag will be applied when fetching pacts --&gt;
+            &lt;version&gt;+&lt;/version&gt;
+        &lt;/contractDependency&gt;
+
+        &lt;!-- The contracts mode can't be classpath --&gt;
+        &lt;contractsMode&gt;REMOTE&lt;/contractsMode&gt;
+    &lt;/configuration&gt;
+    &lt;!-- Don't forget to add spring-cloud-contract-pact to the classpath! --&gt;
+    &lt;dependencies&gt;
+        &lt;dependency&gt;
+            &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+            &lt;artifactId&gt;spring-cloud-contract-pact&lt;/artifactId&gt;
+            &lt;version&gt;${spring-cloud-contract.version}&lt;/version&gt;
+        &lt;/dependency&gt;
+    &lt;/dependencies&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">buildscript {
+    repositories {
+        //...
+    }
+
+    dependencies {
+        // ...
+        // Don't forget to add spring-cloud-contract-pact to the classpath!
+        classpath "org.springframework.cloud:spring-cloud-contract-pact:${contractVersion}"
+    }
+}
+
+contracts {
+    // When + is passed, a latest tag will be applied when fetching pacts
+    contractDependency {
+        stringNotation = "${project.group}:${project.name}:+"
+    }
+    contractRepository {
+        repositoryUrl = "pact://http://localhost:8085"
+    }
+    // The mode can't be classpath
+    contractsMode = "REMOTE"
+    // Base class mappings etc.
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>With such a setup:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Pact files are downloaded from the Pact Broker.</p>
+</li>
+<li>
+<p>Spring Cloud Contract converts the Pact files into tests and stubs.</p>
+</li>
+<li>
+<p>The JAR with the stubs gets automatically created, as usual.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-pact-consumer-producer-contract"><a class="anchor" href="#how-to-pact-consumer-producer-contract"></a><a class="link" href="#how-to-pact-consumer-producer-contract">8.7.9. Flow: Producer Contract approach with Pact on the Consumer Side</a></h4>
+<div class="paragraph">
+<p>In the scenario where you do not want to do the consumer contract approach
+(for every single consumer, define the expectations) but you prefer
+to do producer contracts (the producer provides the contracts and
+publishes stubs), you can use Spring Cloud Contract with the
+Stub Runner option. You can find an example of such a setup
+<a href="https://github.com/spring-cloud-samples/spring-cloud-contract-samples/tree/2.2.x/consumer_pact_stubrunner">here</a>.</p>
+</div>
+<div class="paragraph">
+<p>Remember to add the Stub Runner and Spring Cloud Contract Pact modules
+as test dependencies.</p>
+</div>
+<div class="paragraph">
+<p>The following listing shows the configuration details for both Maven and Gradle:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependencyManagement&gt;
+    &lt;dependencies&gt;
+        &lt;dependency&gt;
+            &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+            &lt;artifactId&gt;spring-cloud-dependencies&lt;/artifactId&gt;
+            &lt;version&gt;${spring-cloud.version}&lt;/version&gt;
+            &lt;type&gt;pom&lt;/type&gt;
+            &lt;scope&gt;import&lt;/scope&gt;
+        &lt;/dependency&gt;
+    &lt;/dependencies&gt;
+&lt;/dependencyManagement&gt;
+
+&lt;!-- Don't forget to add spring-cloud-contract-pact to the classpath! --&gt;
+&lt;dependencies&gt;
+    &lt;!-- ... --&gt;
+    &lt;dependency&gt;
+        &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+        &lt;artifactId&gt;spring-cloud-starter-contract-stub-runner&lt;/artifactId&gt;
+        &lt;scope&gt;test&lt;/scope&gt;
+    &lt;/dependency&gt;
+    &lt;dependency&gt;
+        &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+        &lt;artifactId&gt;spring-cloud-contract-pact&lt;/artifactId&gt;
+        &lt;scope&gt;test&lt;/scope&gt;
+    &lt;/dependency&gt;
+&lt;/dependencies&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">dependencyManagement {
+    imports {
+        mavenBom "org.springframework.cloud:spring-cloud-dependencies:${springCloudVersion}"
+    }
+}
+
+dependencies {
+    //...
+    testCompile("org.springframework.cloud:spring-cloud-starter-contract-stub-runner")
+    // Don't forget to add spring-cloud-contract-pact to the classpath!
+    testCompile("org.springframework.cloud:spring-cloud-contract-pact")
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Next, you can pass the URL of the Pact Broker to <code>repositoryRoot</code>, prefixed
+with <code>pact://</code> protocol (for example, <code>pact://http://localhost:8085</code>), as the following
+example shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@RunWith(SpringRunner.class)
+@SpringBootTest
+@AutoConfigureStubRunner(stubsMode = StubRunnerProperties.StubsMode.REMOTE,
+        ids = "com.example:beer-api-producer-pact",
+        repositoryRoot = "pact://http://localhost:8085")
+public class BeerControllerTest {
+    //Inject the port of the running stub
+    @StubRunnerPort("beer-api-producer-pact") int producerPort;
+    //...
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>With such a setup:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Pact files are downloaded from the Pact Broker.</p>
+</li>
+<li>
+<p>Spring Cloud Contract converts the Pact files into stub definitions.</p>
+</li>
+<li>
+<p>The stub servers are started and fed with stubs.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-debug"><a class="anchor" href="#how-to-debug"></a><a class="link" href="#how-to-debug">8.8. How Can I Debug the Request/Response Being Sent by the Generated Tests Client?</a></h3>
+<div class="paragraph">
+<p>The generated tests all boil down to RestAssured in some form or fashion. RestAssured
+relies on the <a href="https://hc.apache.org/httpcomponents-client-ga/">Apache HttpClient</a>.
+HttpClient has a facility called
+<a href="https://hc.apache.org/httpcomponents-client-ga/logging.html#Wire_Logging">wire logging</a>,
+which logs the entire request and response to HttpClient. Spring Boot has a logging
+<a href="https://docs.spring.io/spring-boot/docs/current/reference/html/common-application-properties.html">common application property</a>
+for doing this sort of thing. To use it, add this to your application properties, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-properties hljs" data-lang="properties">logging.level.org.apache.http.wire=DEBUG</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-debug-wiremock"><a class="anchor" href="#how-to-debug-wiremock"></a><a class="link" href="#how-to-debug-wiremock">8.9. How Can I Debug the Mapping, Request, or Response Being Sent by WireMock?</a></h3>
+<div class="paragraph">
+<p>Starting from version <code>1.2.0</code>, we turn on WireMock logging to
+<code>info</code> and set the WireMock notifier to being verbose. Now you can
+exactly know what request was received by the WireMock server and which
+matching response definition was picked.</p>
+</div>
+<div class="paragraph">
+<p>To turn off this feature, set WireMock logging to <code>ERROR</code>, as follows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-properties hljs" data-lang="properties">logging.level.com.github.tomakehurst.wiremock=ERROR</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-see-registered-stubs"><a class="anchor" href="#how-to-see-registered-stubs"></a><a class="link" href="#how-to-see-registered-stubs">8.10. How Can I See What Got Registered in the HTTP Server Stub?</a></h3>
+<div class="paragraph">
+<p>You can use the <code>mappingsOutputFolder</code> property on <code>@AutoConfigureStubRunner</code>, <code>StubRunnerRule</code>, or
+`StubRunnerExtension`to dump all mappings per artifact ID. Also the port at which the given stub server
+was started is attached.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-reference-text-from-file"><a class="anchor" href="#how-to-reference-text-from-file"></a><a class="link" href="#how-to-reference-text-from-file">8.11. How Can I Reference Text from File?</a></h3>
+<div class="paragraph">
+<p>In version 1.2.0, we added this ability. You can call a <code>file(&#8230;&#8203;)</code> method in the
+DSL and provide a path relative to where the contract lies.
+If you use YAML, you can use the <code>bodyFromFile</code> property.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-generate-pact-from-scc"><a class="anchor" href="#how-to-generate-pact-from-scc"></a><a class="link" href="#how-to-generate-pact-from-scc">8.12. How Can I Generate Pact, YAML, or X files from Spring Cloud Contract Contracts?</a></h3>
+<div class="paragraph">
+<p>Spring Cloud Contract comes with a <code>ToFileContractsTransformer</code> class that lets you dump
+contracts as files for the given <code>ContractConverter</code>. It contains a <code>static void main</code>
+method that lets you execute the transformer as an executable. It takes the following
+arguments:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>argument 1 : <code>FQN</code>: Fully qualified name of the <code>ContractConverter</code> (for example, <code>PactContractConverter</code>). <strong>REQUIRED</strong>.</p>
+</li>
+<li>
+<p>argument 2 : <code>path</code>: Path where the dumped files should be stored. <strong>OPTIONAL</strong>&#8201;&#8212;&#8201;defaults to <code>target/converted-contracts</code>.</p>
+</li>
+<li>
+<p>argument 3 : <code>path</code>: Path were the contracts should be searched for. <strong>OPTIONAL</strong>&#8201;&#8212;&#8201;defaults to <code>src/test/resources/contracts</code>.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>After executing the transformer, the Spring Cloud Contract files are processed and,
+depending on the provided FQN of the <code>ContractTransformer</code>, the contracts are transformed
+to the required format and dumped to the provided folder.</p>
+</div>
+<div class="paragraph">
+<p>The following example shows how to configure Pact integration for both Maven and Gradle:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;plugin&gt;
+    &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
+    &lt;artifactId&gt;exec-maven-plugin&lt;/artifactId&gt;
+    &lt;version&gt;1.6.0&lt;/version&gt;
+    &lt;executions&gt;
+        &lt;execution&gt;
+            &lt;id&gt;convert-dsl-to-pact&lt;/id&gt;
+            &lt;phase&gt;process-test-classes&lt;/phase&gt;
+            &lt;configuration&gt;
+                &lt;classpathScope&gt;test&lt;/classpathScope&gt;
+                &lt;mainClass&gt;
+                    org.springframework.cloud.contract.verifier.util.ToFileContractsTransformer
+                &lt;/mainClass&gt;
+                &lt;arguments&gt;
+                    &lt;argument&gt;
+                        org.springframework.cloud.contract.verifier.spec.pact.PactContractConverter
+                    &lt;/argument&gt;
+                    &lt;argument&gt;${project.basedir}/target/pacts&lt;/argument&gt;
+                    &lt;argument&gt;
+                        ${project.basedir}/src/test/resources/contracts
+                    &lt;/argument&gt;
+                &lt;/arguments&gt;
+            &lt;/configuration&gt;
+            &lt;goals&gt;
+                &lt;goal&gt;java&lt;/goal&gt;
+            &lt;/goals&gt;
+        &lt;/execution&gt;
+    &lt;/executions&gt;
+&lt;/plugin&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">task convertContracts(type: JavaExec) {
+    main = "org.springframework.cloud.contract.verifier.util.ToFileContractsTransformer"
+    classpath = sourceSets.test.compileClasspath
+    args("org.springframework.cloud.contract.verifier.spec.pact.PactContractConverter",
+            "${project.rootDir}/build/pacts", "${project.rootDir}/src/test/resources/contracts")
+}
+
+test.dependsOn("convertContracts")</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-work-with-transitivie"><a class="anchor" href="#how-to-work-with-transitivie"></a><a class="link" href="#how-to-work-with-transitivie">8.13. How Can I Work with Transitive Dependencies?</a></h3>
+<div class="paragraph">
+<p>The Spring Cloud Contract plugins add the tasks that create the stubs jar for you. One
+problem that arises is that, when reusing the stubs, you can mistakenly import all of
+that stub&#8217;s dependencies. When building a Maven artifact, even though you have a couple
+of different jars, all of them share one pom, as the following listing shows:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock">
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">├── producer-0.0.1.BUILD-20160903.075506-1-stubs.jar
+├── producer-0.0.1.BUILD-20160903.075506-1-stubs.jar.sha1
+├── producer-0.0.1.BUILD-20160903.075655-2-stubs.jar
+├── producer-0.0.1.BUILD-20160903.075655-2-stubs.jar.sha1
+├── producer-0.0.1.BUILD-SNAPSHOT.jar
+├── producer-0.0.1.BUILD-SNAPSHOT.pom
+├── producer-0.0.1.BUILD-SNAPSHOT-stubs.jar
+├── ...
+└── ...</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>There are three possibilities of working with those dependencies so as not to have any
+issues with transitive dependencies:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Mark all application dependencies as optional</p>
+</li>
+<li>
+<p>Create a separate artifactid for the stubs</p>
+</li>
+<li>
+<p>Exclude dependencies on the consumer side</p>
+</li>
+</ul>
+</div>
+<div class="sect3">
+<h4 id="how-to-work-with-transitivie-optional"><a class="anchor" href="#how-to-work-with-transitivie-optional"></a><a class="link" href="#how-to-work-with-transitivie-optional">8.13.1. How Can I Mark All Application Dependencies as Optional?</a></h4>
+<div class="paragraph">
+<p>If, in the <code>producer</code> application, you mark all of your dependencies as optional,
+when you include the <code>producer</code> stubs in another application (or when that
+dependency gets downloaded by Stub Runner) then, since all of the dependencies are
+optional, they do not get downloaded.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-work-with-transitivie-separate"><a class="anchor" href="#how-to-work-with-transitivie-separate"></a><a class="link" href="#how-to-work-with-transitivie-separate">8.13.2. How can I Create a Separate <code>artifactid</code> for the Stubs?</a></h4>
+<div class="paragraph">
+<p>If you create a separate <code>artifactid</code>, you can set it up in whatever way you wish.
+For example, you might decide to have no dependencies at all.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="how-to-work-with-transitivie-exclude"><a class="anchor" href="#how-to-work-with-transitivie-exclude"></a><a class="link" href="#how-to-work-with-transitivie-exclude">8.13.3. How can I Exclude Dependencies on the Consumer Side?</a></h4>
+<div class="paragraph">
+<p>As a consumer, if you add the stub dependency to your classpath, you can explicitly exclude the unwanted dependencies.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="contract-dsl-rest-docs"><a class="anchor" href="#contract-dsl-rest-docs"></a><a class="link" href="#contract-dsl-rest-docs">8.14. How can I Generate Spring REST Docs Snippets from the Contracts?</a></h3>
+<div class="paragraph">
+<p>When you want to include the requests and responses of your API by using Spring REST Docs,
+you only need to make some minor changes to your setup if you are using MockMvc and RestAssuredMockMvc.
+To do so, include the following dependencies (if you have not already done so):</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">maven</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;
+    &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-cloud-starter-contract-verifier&lt;/artifactId&gt;
+    &lt;scope&gt;test&lt;/scope&gt;
+&lt;/dependency&gt;
+&lt;dependency&gt;
+    &lt;groupId&gt;org.springframework.restdocs&lt;/groupId&gt;
+    &lt;artifactId&gt;spring-restdocs-mockmvc&lt;/artifactId&gt;
+    &lt;optional&gt;true&lt;/optional&gt;
+&lt;/dependency&gt;</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">gradle</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-groovy hljs" data-lang="groovy">testImplementation 'org.springframework.cloud:spring-cloud-starter-contract-verifier'
+testImplementation 'org.springframework.restdocs:spring-restdocs-mockmvc'</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Next, you need to make some changes to your base class. The following examples use
+<code>WebAppContext</code> and the standalone option with RestAssured:</p>
+</div>
+<div class="exampleblock">
+<div class="content">
+<div class="listingblock primary">
+<div class="title">WebAppContext</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package com.example.fraud;
+
+import io.restassured.module.mockmvc.RestAssuredMockMvc;
+import org.junit.Before;
+import org.junit.Rule;
+import org.junit.rules.TestName;
+import org.junit.runner.RunWith;
+
+
+import org.springframework.beans.factory.annotation.Autowired;
+import org.springframework.boot.test.context.SpringBootTest;
+import org.springframework.restdocs.JUnitRestDocumentation;
+import org.springframework.test.context.junit4.SpringRunner;
+import org.springframework.test.web.servlet.setup.MockMvcBuilders;
+import org.springframework.web.context.WebApplicationContext;
+
+import static org.springframework.restdocs.mockmvc.MockMvcRestDocumentation.document;
+import static org.springframework.restdocs.mockmvc.MockMvcRestDocumentation.documentationConfiguration;
+
+@RunWith(SpringRunner.class)
+@SpringBootTest(classes = Application.class)
+public abstract class FraudBaseWithWebAppSetup {
+
+    private static final String OUTPUT = "target/generated-snippets";
+
+    @Rule
+    public JUnitRestDocumentation restDocumentation = new JUnitRestDocumentation(OUTPUT);
+
+    @Rule
+    public TestName testName = new TestName();
+
+    @Autowired
+    private WebApplicationContext context;
+
+    @Before
+    public void setup() {
+        RestAssuredMockMvc.mockMvc(MockMvcBuilders.webAppContextSetup(this.context)
+                .apply(documentationConfiguration(this.restDocumentation))
+                .alwaysDo(document(
+                        getClass().getSimpleName() + "_" + testName.getMethodName()))
+                .build());
+    }
+
+    protected void assertThatRejectionReasonIsNull(Object rejectionReason) {
+        assert rejectionReason == null;
+    }
+
+}</code></pre>
+</div>
+</div>
+<div class="listingblock secondary">
+<div class="title">Standalone</div>
+<div class="content">
+<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">package com.example.fraud;
+
+import io.restassured.module.mockmvc.RestAssuredMockMvc;
+import org.junit.Before;
+import org.junit.Rule;
+import org.junit.rules.TestName;
+
+import org.springframework.restdocs.JUnitRestDocumentation;
+import org.springframework.test.web.servlet.setup.MockMvcBuilders;
+
+import static org.springframework.restdocs.mockmvc.MockMvcRestDocumentation.document;
+import static org.springframework.restdocs.mockmvc.MockMvcRestDocumentation.documentationConfiguration;
+
+public abstract class FraudBaseWithStandaloneSetup {
+
+    private static final String OUTPUT = "target/generated-snippets";
+
+    @Rule
+    public JUnitRestDocumentation restDocumentation = new JUnitRestDocumentation(OUTPUT);
+
+    @Rule
+    public TestName testName = new TestName();
+
+    @Before
+    public void setup() {
+        RestAssuredMockMvc.standaloneSetup(MockMvcBuilders
+                .standaloneSetup(new FraudDetectionController())
+                .apply(documentationConfiguration(this.restDocumentation))
+                .alwaysDo(document(
+                        getClass().getSimpleName() + "_" + testName.getMethodName())));
+    }
+
+}</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+You need not specify the output directory for the generated snippets (since version 1.2.0.RELEASE of Spring REST Docs).
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-use-stubs-from-a-location"><a class="anchor" href="#how-to-use-stubs-from-a-location"></a><a class="link" href="#how-to-use-stubs-from-a-location">8.15. How can I Use Stubs from a Location</a></h3>
+<div class="paragraph">
+<p>If you want to fetch contracts or stubs from a given location without cloning a repo or fetching a JAR, just use the <code>stubs://</code> protocol when providing the repository root argument for Stub Runner or the Spring Cloud Contract plugin. You can read more about this in <a href="#features-stub-runner-stubs-protocol">this section</a> of the documentation.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-generate-stubs-at-runtime"><a class="anchor" href="#how-to-generate-stubs-at-runtime"></a><a class="link" href="#how-to-generate-stubs-at-runtime">8.16. How can I Generate Stubs at Runtime</a></h3>
+<div class="paragraph">
+<p>If you want to generate stubs at runtime for contracts, it&#8217;s enough to switch the <code>generateStubs</code> property in the <code>@AutoConfigureStubRunner</code> annotation, or call the <code>withGenerateStubs(true)</code> method on the JUnit Rule or Extension. You can read more about this in <a href="#features-stub-runner-generate-stubs-at-runtime">this section</a> of the documentation.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-use-the-failonnostubs-feature"><a class="anchor" href="#how-to-use-the-failonnostubs-feature"></a><a class="link" href="#how-to-use-the-failonnostubs-feature">8.17. How can I Make The Build Pass if There Are No Contracts or Stubs</a></h3>
+<div class="paragraph">
+<p>If you want Stub Runner not to fail if no stubs were found, it&#8217;s enough to switch the <code>generateStubs</code> property in the <code>@AutoConfigureStubRunner</code> annotation, or call the <code>withFailOnNoStubs(false)</code> method on the JUnit Rule or Extension. You can read more about this in <a href="#features-stub-runner-fail-on-no-stubs">this section</a> of the documentation.</p>
+</div>
+<div class="paragraph">
+<p>If you want the plugins not to fail the build when no contracts were found, you can set the <code>failOnNoStubs</code> flag in Maven or call the <code>contractRepository { failOnNoStubs(false) }</code> Closure in Gradle.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="how-to-mark-contract-in-progress"><a class="anchor" href="#how-to-mark-contract-in-progress"></a><a class="link" href="#how-to-mark-contract-in-progress">8.18. How can I Mark that a Contract Is in Progress</a></h3>
+<div class="paragraph">
+<p>If a contract is in progress, it means that the on the producer side tests will not be generated, but the stub will be. You can read more about this in <a href="#contract-dsl-in-progress">this section</a> of the documentation.</p>
+</div>
+<div class="paragraph">
+<p>In a CI build, before going to production, you would like to ensure that no in progress contracts are there on the classpath. That&#8217;s because you may lead to false positives. That&#8217;s why, by default, in the Spring Cloud Contract plugin, we set the value of <code>failOnInProgress</code> to <code>true</code>. If you want to allow such contracts when tests are to be generated, just set the flag to <code>false</code>.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="common-application-properties"><a class="anchor" href="#common-application-properties"></a><a class="link" href="#common-application-properties">Appendix A: Common application properties</a></h3>
+<div class="paragraph">
+<p>Various properties can be specified inside your <code>application.properties</code> file, inside your <code>application.yml</code> file, or as command line switches.
+This appendix provides a list of common Spring Cloud Contract properties and references to the underlying classes that consume them.</p>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+Property contributions can come from additional jar files on your classpath, so you should not consider this an exhaustive list.
+Also, you can define your own properties.
+</td>
+</tr>
+</table>
+</div>
+<div class="sect3">
+<h4 id="default-application-properties"><a class="anchor" href="#default-application-properties"></a><a class="link" href="#default-application-properties">8.A.1. Default application properties</a></h4>
+<table class="tableblock frame-all grid-all stretch">
+<colgroup>
+<col style="width: 33.3333%;">
+<col style="width: 33.3333%;">
+<col style="width: 33.3334%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.amqp.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to enable support for Stub Runner and AMQP.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.amqp.mockCOnnection</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to enable support for Stub Runner and AMQP mocked connection factory.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.classifier</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubs</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The classifier to use by default in ivy co-ordinates for a stub.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.cloud.consul.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to enable stubs registration in Consul.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.cloud.delegate.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to enable DiscoveryClient&#8217;s Stub Runner implementation.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.cloud.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to enable Spring Cloud support for Stub Runner.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.cloud.eureka.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to enable stubs registration in Eureka.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.cloud.loadbalancer.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to enable Stub Runner&#8217;s Spring Cloud Load Balancer integration.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.cloud.stubbed.discovery.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether Service Discovery should be stubbed for Stub Runner. If set to false, stubs will get registered in real service discovery.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.cloud.zookeeper.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to enable stubs registration in Zookeeper.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.consumer-name</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">You can override the default {@code spring.application.name} of this field by setting a value to this parameter.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.delete-stubs-after-test</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If set to {@code false} will NOT delete stubs from a temporary folder after running tests.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.fail-on-no-stubs</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When enabled, this flag will tell stub runner to throw an exception when no stubs / contracts were found.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.generate-stubs</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When enabled, this flag will tell stub runner to not load the generated stubs, but convert the found contracts at runtime to a stub format and run those stubs.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.http-server-stub-configurer</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Configuration for an HTTP server stub.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.ids</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">[]</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The ids of the stubs to run in "ivy" notation ([groupId]:artifactId:[version]:[classifier][:port]). {@code groupId}, {@code classifier}, {@code version} and {@code port} can be optional.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.ids-to-service-ids</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Mapping of Ivy notation based ids to serviceIds inside your application. Example "a:b" &#8594; "myService" "artifactId" &#8594; "myOtherService"</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.integration.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to enable Stub Runner integration with Spring Integration.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.jms.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to enable Stub Runner integration with Spring JMS.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.kafka.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to enable Stub Runner integration with Spring Kafka.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.kafka.initializer.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to allow Stub Runner to take care of polling for messages instead of the KafkaStubMessages component. The latter should be used only on the producer side.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.mappings-output-folder</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Dumps the mappings of each HTTP server to the selected folder.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.max-port</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">15000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Max value of a port for the automatically started WireMock server.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.min-port</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">10000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Min value of a port for the automatically started WireMock server.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.password</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Repository password.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.properties</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map of properties that can be passed to custom {@link org.springframework.cloud.contract.stubrunner.StubDownloaderBuilder}.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.proxy-host</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Repository proxy host.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.proxy-port</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Repository proxy port.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.server-id</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.stream.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to enable Stub Runner integration with Spring Cloud Stream.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.stubs-mode</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Pick where the stubs should come from.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.stubs-per-consumer</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Should only stubs for this particular consumer get registered in HTTP server stub.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.username</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Repository username.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">wiremock.placeholders.enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Flag to indicate that http URLs in generated wiremock stubs should be filtered to add or resolve a placeholder for a dynamic port.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">wiremock.reset-mappings-after-each-test</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">wiremock.rest-template-ssl-enabled</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">wiremock.server.files</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">[]</p></td>
+<td class="tableblock halign-left valign-top"></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">wiremock.server.https-port</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">-1</p></td>
+<td class="tableblock halign-left valign-top"></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">wiremock.server.https-port-dynamic</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">wiremock.server.port</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">8080</p></td>
+<td class="tableblock halign-left valign-top"></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">wiremock.server.port-dynamic</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">wiremock.server.stubs</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">[]</p></td>
+<td class="tableblock halign-left valign-top"></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="additional-application-properties"><a class="anchor" href="#additional-application-properties"></a><a class="link" href="#additional-application-properties">8.A.2. Additional application properties</a></h4>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-important" title="Important"></i>
+</td>
+<td class="content">
+The following properties can be passed as a system property (e.g. <code>stubrunner.properties.git.branch</code>) or via an environment variable (e.g. <code>STUBRUNNER_PROPERTIES_GIT_BRANCH</code>) or as a property inside stub runner&#8217;s annotation or a JUnit Rule / Extension. In the latter case you can pass <code>git.branch</code> property name instead of the <code>stubrunner.properties.git.branch</code> one.
+</td>
+</tr>
+</table>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 3. Stubrunner Properties Options</caption>
+<colgroup>
+<col style="width: 33.3333%;">
+<col style="width: 33.3333%;">
+<col style="width: 33.3334%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.properties.pactbroker.provider-name-with-group-id</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When using the Pact Broker based approach, you can automatically group id to the provider name.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.properties.git.branch</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When using the SCM based approach, you can customize the branch name to check out.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.properties.git.commit-message</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Updating project [$project] with stubs</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When using the SCM based approach, you can customize the commit message for created stubs. The <code>$project</code> text will be replaced with the project name.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.properties.git.no-of-attempts</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">10</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When using the SCM based approach, you can customize number of retries to push the stubs to Git.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.properties.git.username</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When using the SCM based approach, you can pass the username to connect to the Git repository.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.properties.git.password</p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When using the SCM based approach, you can pass the password to connect to the Git repository.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.properties.git.wait-between-attempts</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">1000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When using the SCM based approach, you can customize waiting time in ms between trying to push the stubs to Git.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">stubrunner.properties.stubs.find-producer</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When using the Stubs protocol, you can toggle this flag to search for contracts via the <code>group id / artifact id</code> instead of taking the stubs directly from the provided folder.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+</div>
+</div>
+<script type="text/javascript" src="js/tocbot/tocbot.min.js"></script>
+<script type="text/javascript" src="js/toc.js"></script>
+<link rel="stylesheet" href="js/highlight/styles/github.min.css">
+<script src="js/highlight/highlight.min.js"></script>
+<script>hljs.initHighlighting()</script>
+</body>
+</html>
\ No newline at end of file
diff --git a/reference/pdf/spring-cloud-contract.pdf b/reference/pdf/spring-cloud-contract.pdf
index 5bf75920a5..e8b3cc39b6 100644
--- a/reference/pdf/spring-cloud-contract.pdf
+++ b/reference/pdf/spring-cloud-contract.pdf
@@ -5,8 +5,8 @@
 /Author <feff004100640061006d00200044007500640063007a0061006b002c0020004d0061007400680069006100730020004400fc0073007400650072006800f600660074002c0020004d0061007200630069006e002000470072007a0065006a0073007a0063007a0061006b002c002000440065006e006e006900730020004b0069006500730065006c0068006f007200730074002c0020004a0061006b007500620020004b007500620072007901440073006b0069002c0020004b00610072006f006c0020004c0061007300730061006b002c0020004f006c006700610020004d00610063006900610073007a0065006b002d0053006800610072006d0061002c0020004d00610072006900750073007a00200053006d0079006b007501420061002c0020004400610076006500200053007900650072002c0020004a0061007900200042007200790061006e0074>
 /Creator (Asciidoctor PDF 1.5.0.alpha.18, based on Prawn 2.2.2)
 /Producer <feff004100640061006d00200044007500640063007a0061006b002c0020004d0061007400680069006100730020004400fc0073007400650072006800f600660074002c0020004d0061007200630069006e002000470072007a0065006a0073007a0063007a0061006b002c002000440065006e006e006900730020004b0069006500730065006c0068006f007200730074002c0020004a0061006b007500620020004b007500620072007901440073006b0069002c0020004b00610072006f006c0020004c0061007300730061006b002c0020004f006c006700610020004d00610063006900610073007a0065006b002d0053006800610072006d0061002c0020004d00610072006900750073007a00200053006d0079006b007501420061002c0020004400610076006500200053007900650072002c0020004a0061007900200042007200790061006e0074>
-/ModDate (D:20200609125156+00'00')
-/CreationDate (D:20200609125227+00'00')
+/ModDate (D:20200609143147+00'00')
+/CreationDate (D:20200609143222+00'00')
 >>
 endobj
 2 0 obj
diff --git a/spring-cloud-contract-maven-plugin/apidocs/allclasses-frame.html b/spring-cloud-contract-maven-plugin/apidocs/allclasses-frame.html
index bee8085705..e3e7712586 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/allclasses-frame.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/allclasses-frame.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>All Classes (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/allclasses-noframe.html b/spring-cloud-contract-maven-plugin/apidocs/allclasses-noframe.html
index 037786cc08..b424d8619c 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/allclasses-noframe.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/allclasses-noframe.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>All Classes (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/constant-values.html b/spring-cloud-contract-maven-plugin/apidocs/constant-values.html
index 151132fd59..64902992f9 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/constant-values.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/constant-values.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Constant Field Values (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/deprecated-list.html b/spring-cloud-contract-maven-plugin/apidocs/deprecated-list.html
index dc4ca0a259..60b90657f0 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/deprecated-list.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/deprecated-list.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Deprecated List (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/help-doc.html b/spring-cloud-contract-maven-plugin/apidocs/help-doc.html
index ddc0e6271b..f6d957e496 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/help-doc.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/help-doc.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>API Help (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/index-all.html b/spring-cloud-contract-maven-plugin/apidocs/index-all.html
index a27163c791..d171a762b1 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/index-all.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/index-all.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Index (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/index.html b/spring-cloud-contract-maven-plugin/apidocs/index.html
index 473dc6ab4b..46309586d4 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/index.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/index.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API</title>
 <script type="text/javascript">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/BaseClassMapping.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/BaseClassMapping.html
index fc045de3b5..be6536716f 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/BaseClassMapping.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/BaseClassMapping.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>BaseClassMapping (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/ConvertMojo.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/ConvertMojo.html
index dc725582ce..14124de264 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/ConvertMojo.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/ConvertMojo.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>ConvertMojo (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/GenerateStubsMojo.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/GenerateStubsMojo.html
index eb79aebd49..8b9a1c2a71 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/GenerateStubsMojo.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/GenerateStubsMojo.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>GenerateStubsMojo (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/GenerateTestsMojo.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/GenerateTestsMojo.html
index fb547de850..2255c87468 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/GenerateTestsMojo.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/GenerateTestsMojo.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>GenerateTestsMojo (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/HelpMojo.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/HelpMojo.html
index 33b5a89c17..140a1aa201 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/HelpMojo.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/HelpMojo.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>HelpMojo (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/PushStubsToScmMojo.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/PushStubsToScmMojo.html
index d22f189d2f..977735aa15 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/PushStubsToScmMojo.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/PushStubsToScmMojo.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>PushStubsToScmMojo (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/RunMojo.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/RunMojo.html
index f2fbb8b0c5..069bd1ae76 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/RunMojo.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/RunMojo.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>RunMojo (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/BaseClassMapping.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/BaseClassMapping.html
index 902ab619f0..471d2e2d85 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/BaseClassMapping.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/BaseClassMapping.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Uses of Class org.springframework.cloud.contract.maven.verifier.BaseClassMapping (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/ConvertMojo.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/ConvertMojo.html
index d5dfe1db8e..2c3bd9874c 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/ConvertMojo.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/ConvertMojo.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Uses of Class org.springframework.cloud.contract.maven.verifier.ConvertMojo (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/GenerateStubsMojo.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/GenerateStubsMojo.html
index b5ab3ca04e..3691ce1045 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/GenerateStubsMojo.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/GenerateStubsMojo.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Uses of Class org.springframework.cloud.contract.maven.verifier.GenerateStubsMojo (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/GenerateTestsMojo.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/GenerateTestsMojo.html
index edbc9ad8c5..e047dafbb2 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/GenerateTestsMojo.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/GenerateTestsMojo.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Uses of Class org.springframework.cloud.contract.maven.verifier.GenerateTestsMojo (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/HelpMojo.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/HelpMojo.html
index dd8a750971..b6032727af 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/HelpMojo.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/HelpMojo.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Uses of Class org.springframework.cloud.contract.maven.verifier.HelpMojo (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/PushStubsToScmMojo.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/PushStubsToScmMojo.html
index 72aafaf66f..cf34561cb2 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/PushStubsToScmMojo.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/PushStubsToScmMojo.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Uses of Class org.springframework.cloud.contract.maven.verifier.PushStubsToScmMojo (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/RunMojo.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/RunMojo.html
index 38a58dd357..0c420897e4 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/RunMojo.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/class-use/RunMojo.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Uses of Class org.springframework.cloud.contract.maven.verifier.RunMojo (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-frame.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-frame.html
index ef98d1ce91..12aa3a50e4 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-frame.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-frame.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>org.springframework.cloud.contract.maven.verifier (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-summary.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-summary.html
index 45d35d1624..155ce17ce5 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-summary.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-summary.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>org.springframework.cloud.contract.maven.verifier (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-tree.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-tree.html
index 32e336b072..d63bfc45a5 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-tree.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-tree.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>org.springframework.cloud.contract.maven.verifier Class Hierarchy (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-use.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-use.html
index 69482517c8..d0db4fa10e 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-use.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/package-use.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Uses of Package org.springframework.cloud.contract.maven.verifier (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/AetherStubDownloaderFactory.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/AetherStubDownloaderFactory.html
index 8ed4417c58..3c0c620d97 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/AetherStubDownloaderFactory.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/AetherStubDownloaderFactory.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>AetherStubDownloaderFactory (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/LocalStubRunner.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/LocalStubRunner.html
index 0e8dc54ca9..2e1b3f414f 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/LocalStubRunner.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/LocalStubRunner.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>LocalStubRunner (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/RemoteStubRunner.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/RemoteStubRunner.html
index 4a3ff7df62..f3511cb2ca 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/RemoteStubRunner.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/RemoteStubRunner.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>RemoteStubRunner (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/class-use/AetherStubDownloaderFactory.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/class-use/AetherStubDownloaderFactory.html
index bcb74cd1ff..93a4565887 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/class-use/AetherStubDownloaderFactory.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/class-use/AetherStubDownloaderFactory.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Uses of Class org.springframework.cloud.contract.maven.verifier.stubrunner.AetherStubDownloaderFactory (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/class-use/LocalStubRunner.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/class-use/LocalStubRunner.html
index 10f4f5e52c..dfce6bb908 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/class-use/LocalStubRunner.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/class-use/LocalStubRunner.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Uses of Class org.springframework.cloud.contract.maven.verifier.stubrunner.LocalStubRunner (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/class-use/RemoteStubRunner.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/class-use/RemoteStubRunner.html
index bb13afec6d..f6c04a6c2f 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/class-use/RemoteStubRunner.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/class-use/RemoteStubRunner.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Uses of Class org.springframework.cloud.contract.maven.verifier.stubrunner.RemoteStubRunner (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-frame.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-frame.html
index ca1d20ae85..f66f3d3aff 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-frame.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-frame.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>org.springframework.cloud.contract.maven.verifier.stubrunner (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-summary.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-summary.html
index c42181c54d..4fca2b2197 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-summary.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-summary.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>org.springframework.cloud.contract.maven.verifier.stubrunner (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-tree.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-tree.html
index dfc554fa40..f33cd3d712 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-tree.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-tree.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>org.springframework.cloud.contract.maven.verifier.stubrunner Class Hierarchy (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-use.html b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-use.html
index bbc298b3e9..93a596f71c 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-use.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/org/springframework/cloud/contract/maven/verifier/stubrunner/package-use.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Uses of Package org.springframework.cloud.contract.maven.verifier.stubrunner (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/overview-frame.html b/spring-cloud-contract-maven-plugin/apidocs/overview-frame.html
index 833d4813eb..32f39161c8 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/overview-frame.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/overview-frame.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Overview List (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/overview-summary.html b/spring-cloud-contract-maven-plugin/apidocs/overview-summary.html
index 1664cf64a3..a10f77dfc9 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/overview-summary.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/overview-summary.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Overview (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">
diff --git a/spring-cloud-contract-maven-plugin/apidocs/overview-tree.html b/spring-cloud-contract-maven-plugin/apidocs/overview-tree.html
index cb947eacb6..ffac9b8ee0 100644
--- a/spring-cloud-contract-maven-plugin/apidocs/overview-tree.html
+++ b/spring-cloud-contract-maven-plugin/apidocs/overview-tree.html
@@ -2,7 +2,7 @@
 <!-- NewPage -->
 <html lang="en">
 <head>
-<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 12:54:31 UTC 2020 -->
+<!-- Generated by javadoc (1.8.0_242) on Tue Jun 09 14:34:32 UTC 2020 -->
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Class Hierarchy (Spring Cloud Contract Maven Plugin 3.0.0-SNAPSHOT API)</title>
 <meta name="date" content="2020-06-09">