From 34d4eecd91bffd1aecf1c6c835eb8005548090d1 Mon Sep 17 00:00:00 2001 From: Andrzej Jarmoniuk <1554729+ajarmoniuk@users.noreply.github.com> Date: Mon, 10 Oct 2022 14:38:11 +0200 Subject: [PATCH] Add a link to the actual Maven versioning specification --- src/site/markdown/version-rules.md.vm | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/src/site/markdown/version-rules.md.vm b/src/site/markdown/version-rules.md.vm index 2c7c8fb13b..e6a058128d 100644 --- a/src/site/markdown/version-rules.md.vm +++ b/src/site/markdown/version-rules.md.vm @@ -20,21 +20,19 @@ under the License. --> ## Velocity uses # as a prefix for macros and ## as a prefix for comments -#set($h1 = '#') -#set($h2 = '##') #set($h3 = '###') -#set($h4 = '####') -$h1 Version number rules +Version number rules +==================== -$h2 Introduction +Introduction +------------ **Notice:** The limitations explained in this paragraph were true in Maven 2.x, but have been **fixed** in Maven 3.x (see [Maven Versioning Wiki page](https://cwiki.apache.org/confluence/display/MAVENOLD/Versioning) for more details) -The current implementation of -[DefaultArtifactVersion](https://maven.apache.org/ref/current/maven-artifact/xref/org/apache/maven/artifact/versioning/DefaultArtifactVersion.html) -in the core of Maven expects that version numbers will have a very specific format: +The current implementation of the +[Maven Version Order Specification](https://maven.apache.org/pom.html#version-order-specification) will have a very specific format: ` . . - ` @@ -57,7 +55,8 @@ The `versions-maven-plugin` knows three rules for comparing version numbers: The `versions-maven-plugin` will assume that all version numbers follow the `maven` scheme unless you tell it otherwise. -$h2 Rules.xml +Rules.xml +--------- To specify the version schemes to use, you may define a [rule-set xml file](./rule.html), use the `ruleSet` element in the `versions-maven-plugin` plugin configuration, or specify ignored versions via