-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[MNG-8712] dependency version is a requirement, not effective #2279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
pzygielo
reviewed
Apr 28, 2025
elharo
previously requested changes
Apr 28, 2025
michael-o
requested changes
Apr 28, 2025
michael-o
approved these changes
Apr 29, 2025
slawekjaranowski
approved these changes
Apr 29, 2025
elharo
reviewed
Apr 29, 2025
cstamas
reviewed
Apr 30, 2025
maven-model/src/main/mdo/maven.mdo
Outdated
| The version of the dependency, e.g. <code>3.2.1</code>. In Maven 2, this can also be | ||
| specified as a range of versions. | ||
| The version requirement of the dependency, e.g. <code>3.2.1</code>. The actual version will be resolved based on the usage context. | ||
| Version requirement can also be specified as a range of versions, e.g. <code>[3.2.0,)</code>. This is discouraged as it breaks <i>predictability</i> of resolved version. |
Member
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
| Version requirement can also be specified as a range of versions, e.g. <code>[3.2.0,)</code>. This is discouraged as it breaks <i>predictability</i> of resolved version. | |
| Version requirement can also be specified as a range of versions, e.g. <code>[3.2.0,)</code>. User have to be aware that range versions may break <i>predictability</i> of resolved version in some cases. |
Member
Author
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
too long: going back to "as it may break predictability"
|
Resolve #9590 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
see https://issues.apache.org/jira/browse/MNG-8712
hoping this will help users discover how dependency version in
pom.xmlis completely different to every other versions like project or plugin