svn commit: r1872320 - in /maven/website/content: maven-site-1.0-site.jar pom.html

[sv...@apache.org]

Author: svn-site-role
Date: Sat Jan  4 14:48:01 2020
New Revision: 1872320

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/maven-site-1.0-site.jar
    maven/website/content/pom.html

Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.

Modified: maven/website/content/pom.html
==============================================================================
--- maven/website/content/pom.html (original)
+++ maven/website/content/pom.html Sat Jan  4 14:48:01 2020
@@ -349,11 +349,11 @@ Karl Heinz Marbaise" />
 <li><code>(,1.1),(1.1,)</code>: Hard requirement for any version except 1.1; for example because 1.1 has a critical vulnerability.
 <p>Maven picks the highest version of each project that satisfies all the hard requirements of the dependencies on that project. If no version satisfies all the hard requirements, the build fails.</p></li></ul></section><section>
 <h5><a name="Version_Order_Specification:"></a><a name="Version_Order_Specification">Version Order Specification</a>:</h5>
-<p>If version strings are syntactically correct [Semantic Versioning 1.0.0](https://semver.org/spec/v1.0.0.html), version numbers, then in almost all cases version comparison follows the precedence rules outlined in that specification. These versions are the commonly encountered alphanumeric ASCII strings such as 2.15.2-alpha. More precisely, this is true if both version numbers to be compared match the &quot;valid semver&quot; production in the BNF grammar in the semantic versioning specification. Maven does not consider any semantics implied by that specification.</p>
-<ul>
-<li>Important**: This is only true for Semantic Versioning *1.0.0*. The Maven version order algorithm is not compatible with Semantic Versioning *2.0.0*. In particular, Maven does not special case the plus sign or consider build identifiers.
+<p>If version strings are syntactically correct <a class="externalLink" href="https://semver.org/spec/v1.0.0.html">Semantic Versioning 1.0.0</a>, version numbers, then in almost all cases version comparison follows the precedence rules outlined in that specification. These versions are the commonly encountered alphanumeric ASCII strings such as 2.15.2-alpha. More precisely, this is true if both version numbers to be compared match the &quot;valid semver&quot; production in the BNF grammar in the semantic versioning specification. Maven does not consider any semantics implied by that specification.</p>
+<p><b>Important</b>: This is only true for Semantic Versioning <i>1.0.0</i>. The Maven version order algorithm is not compatible with Semantic Versioning <i>2.0.0</i>. In particular, Maven does not special case the plus sign or consider build identifiers.</p>
 <p>When version strings do not follow semantic versioning, a more complex set of rules is required. The Maven coordinate is split in tokens between dots ('<code>.</code>'), hyphens ('<code>-</code>') and transitions between digits and characters. The separator is recorded and will have effect on the order. A transition between digits and characters is equivalent to a hyphen. Empty tokens are replaced with &quot;<code>0</code>&quot;. This gives a sequence of version numbers (numeric tokens) and version qualifiers (non-numeric tokens) with &quot;<code>.</code>&quot; or &quot;<code>-</code>&quot; prefixes.</p>
-<p>Splitting and Replacing Examples:</p></li>
+<p>Splitting and Replacing Examples:</p>
+<ul>
 <li><code>1-1.foo-bar1baz-.1</code> -&gt; <code>1-1.foo-bar-1-baz-0.1</code></li></ul>
 <p>Then, starting from the end of the version, the trailing &quot;null&quot; values (<code>0</code>, <code>&quot;&quot;</code>, &quot;<code>final</code>&quot;, &quot;<code>ga</code>&quot;) are trimmed. This process is repeated at each remaining hyphen from end to start.</p>
 <p>Trimming Examples:</p>