[
https://issues.apache.org/jira/browse/MNG-8712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17947906#comment-17947906
]
Hudson commented on MNG-8712:
-----------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-8712 #2
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-8712/2/
> improve dependency version explanation: it's a requirement, not always
> effective version
> ----------------------------------------------------------------------------------------
>
> Key: MNG-8712
> URL: https://issues.apache.org/jira/browse/MNG-8712
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies, Documentation: General, POM
> Affects Versions: 3.9.9, 4.0.0-rc-3
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Priority: Major
> Fix For: 3.9.10, 4.0.0-rc-4
>
>
> currently, POM documentation says for dependency version
> https://maven.apache.org/ref/3.9.9/maven-model/maven.html#class_dependency
> "The version of the dependency, e.g. 3.2.1. In Maven 2, this can also be
> specified as a range of versions."
> users don't get that it is a version requirement only: the effective version
> will be resolved based on usage context, as explained more in details in
> https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Transitive_Dependencies
> it's long overdue to clarify at POM level
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
