Add Basic Support for Semantic Versioning#56
Merged
Conversation
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.
As discussed in #45, we want built-in support for handling semantic version numbers within MARIN. Some major use-cases in large-scale analyses are:
This PR adds semver-compliant parsing of version numbers and (Maven-Specific) version ranges. Every Artifact Identifier now provides an accessor for (lazily) testing whether its version is semver-compliant, and for obtaining the parsed version representation. Maven version ranges can now also be parsed and checked for version containment. Version objects can be compared using the SemVer standard. All functionality is implemented from scratch without depending on external libraries.
This PR does not use the new version range parsing within the
PomResolverto compute effective dependency targets for ranges yet. This is left for the next release, as it requires an extensive redesign and exhaustive testing.Closes #45.