docs: remove SemVer 2.0.0 build-metadata examples from naming conventions guide#1603
Open
imharjot wants to merge 1 commit into
Open
docs: remove SemVer 2.0.0 build-metadata examples from naming conventions guide#1603imharjot wants to merge 1 commit into
imharjot wants to merge 1 commit into
Conversation
…ions The version-identifier guide recommends Semantic Versioning 1.0.0 but showed `+build` metadata examples (1.2.3+dfc0c87, 2.3.4+15433). That `+` syntax is defined only in SemVer 2.0.0, and Maven explicitly does not special-case the plus sign or treat the trailing text as build metadata; it becomes an ordinary version qualifier. Remove the incorrect examples, drop the "build metadata" wording from the surrounding prose, and add a short note clarifying that `+` has no special meaning in Maven versions, linking to the version order specification in pom.html. Fixes apache#1595
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The naming-conventions guide recommends SemVer 1.0.0 but illustrated it with
+buildmetadata, which is SemVer 2.0.0-only syntax that Maven does not special-case. Removes the incorrect examples, fixes the prose, and adds a clarifying note linking to the version-order spec.Fixes #1595