diff --git a/spring-cloud-contract.html b/spring-cloud-contract.html index 5d4972e3e9..27331e9f11 100644 --- a/spring-cloud-contract.html +++ b/spring-cloud-contract.html @@ -1563,13 +1563,7 @@ all the contract are present in the producer’s repository
Gradle
-
repositories {
-	mavenCentral()
-	mavenLocal()
-	maven { url "http://repo.spring.io/snapshot" }
-	maven { url "http://repo.spring.io/milestone" }
-	maven { url "http://repo.spring.io/release" }
-}
+
Unresolved directive in verifier/introduction.adoc - include::https://raw.githubusercontent.com/spring-cloud/spring-cloud-contract/1.0.x/samples/standalone/dsl/http-server/build.gradle[tags=deps_repos,indent=0]
@@ -4236,7 +4230,24 @@ For both Maven and Gradle the setup comes out of the box. But you can customize <spring.cloud.contract.verifier.skip>true</spring.cloud.contract.verifier.skip> <!-- Next add the assembly plugin to your build --> -Unresolved directive in verifier/stubrunner.adoc - include::https://raw.githubusercontent.com/spring-cloud-samples/spring-cloud-contract-samples/master/producer_with_restdocs/pom.xml[tags=assembly,indent=0] +<plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-assembly-plugin</artifactId> + <executions> + <execution> + <id>stub</id> + <phase>prepare-package</phase> + <goals> + <goal>single</goal> + </goals> + <inherited>false</inherited> + <configuration> + <attach>true</attach> + <descriptor>${basedir}/src/assembly/stub.xml</descriptor> + </configuration> + </execution> + </executions> +</plugin> <!-- Finally setup your assembly. Below you can find the contents of src/main/assembly/stub.xml --> <assembly @@ -5102,6 +5113,43 @@ the Stub Runner Boot.

Where port means the port of the WireMock server.

+
+ + + + + +
+
Important
+		 +Starting from version 1.0.4 as a version you can provide a range of versions that you would like +the Stub Runner to take into consideration. You can read more about the Aether versioning ranges here. +
+
+
+

Taken from Aether Docs:

+
+
+
+
+

This scheme accepts versions of any form, interpreting a version as a sequence of numeric and alphabetic segments. The characters '-', '_', and '.' as well as the mere +transitions from digit to letter and vice versa delimit the version segments. Delimiters are treated as equivalent.

+
+
+

Numeric segments are compared mathematically, alphabetic segments are compared lexicographically and case-insensitively. However, the following qualifier strings are +recognized and treated specially: "alpha" = "a" < "beta" = "b" < "milestone" = "m" < "cr" = "rc" < "snapshot" < "final" = "ga" < "sp". All of those well-known qualifiers +are considered smaller/older than other strings. An empty segment/string is equivalent to 0.

+
+
+

In addition to the above mentioned qualifiers, the tokens "min" and "max" may be used as final version segment to denote the smallest/greatest version having a given prefix. +For example, "1.2.min" denotes the smallest version in the 1.2 line, "1.2.max" denotes the greatest version in the 1.2 line. A version range of the form "[M.N.*]" is short for "[M.N.min, M.N.max]".

+
+
+

Numbers and strings are considered incomparable against each other. Where version segments of different kind would collide, comparison will instead assume that the previous +segments are padded with trailing 0 or "ga" segments, respectively, until the kind mismatch is resolved, e.g. "1-alpha" = "1.0.0-alpha" < "1.0.1-ga" = "1.0.1".

+
+
+