From 820712ed2632ead4398b2cb7a269b3d018944f5d Mon Sep 17 00:00:00 2001 From: buildmaster Date: Fri, 3 Feb 2017 09:12:26 +0000 Subject: [PATCH] Sync docs from 1.0.x to gh-pages --- 1.0.x/spring-cloud-contract.html | 37 ++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) diff --git a/1.0.x/spring-cloud-contract.html b/1.0.x/spring-cloud-contract.html index 70d21e1f49..ab31d142de 100644 --- a/1.0.x/spring-cloud-contract.html +++ b/1.0.x/spring-cloud-contract.html @@ -5102,6 +5102,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".

+
+
+