Version scheme used by project
See original GitHub issueUnfortunately version scheme used by this project makes tools to recognize version 2.10.0 as not higher than 2.10.0.pr3 (for example snyk classifies this just-released 2.10.0 as not solving 467015, and maven-enforcer also considers .pr3 release as higher version, and versions-maven-plugin suggests:
[INFO] --- versions-maven-plugin:2.7:display-dependency-updates (default-cli) @ ... ---
[INFO] artifact com.fasterxml.jackson.core:jackson-core: checking for updates ...
[INFO] The following dependencies in Dependency Management have newer versions:
[INFO] com.fasterxml.jackson.core:jackson-core ......... 2.10.0 -> 2.10.0.pr3
).
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Software versioning - Wikipedia
Software versioning is the process of assigning either unique version names or unique version numbers to unique states of computer software.
Read more >Semantic Versioning 2.0.0 | Semantic Versioning
We call this system “Semantic Versioning.” Under this scheme, version numbers and the way they change convey meaning about the underlying code and...
Read more >What is versioning and how does it work? - TechTarget
In software development, versioning allows development teams to keep track of changes they make to the project code. The changes may include new...
Read more >A Guide to Semantic Versioning - Baeldung
SemVer is a popular versioning scheme that is used by a vast amount of open-source projects to communicate the changes included in a...
Read more >When to use SemVer or CalVer: project type considerations
The two most common versioning schemes—SemVer (semantic versioning) and CalVer (calendar versioning)—can help you build the desired aggregated ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Created follow-up as: #2479
I saw a good document:
https://octopus.com/blog/maven-versioning-explained
that sheds some light here.
One note: I did use “2.7.0-rc1” at some point, but unfortunately OSGi does not work with such version numbers; this is why we changed to all-dot separation. But use of qualifier (I think that is the term) was based on incomplete understanding: use of “m” for “milestone” would have worked better.