You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Florian Schmaus (JIRA)" <ji...@apache.org> on 2019/02/24 20:37:00 UTC
[jira] [Comment Edited] (MNG-6232) Version range is not resolved
correctly
[ https://issues.apache.org/jira/browse/MNG-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16776395#comment-16776395 ]
Florian Schmaus edited comment on MNG-6232 at 2/24/19 8:36 PM:
---------------------------------------------------------------
I also run into this [1]. The issue is especially bad since this behavior is different between Maven and Gradle [2].
I am not sure if Maven's behavior has to be changed, but it is clear to me that there is a method missing to specify all version within a version series (without pulling in alpha/beta/… releases for the following major/minor version). And the implication that using [1.0, 2.0) also includes 2.0-alpha1 should be mentioned everywhere this format is shown in the documentation.
1: And posted to users@maven.apache.org: [https://lists.apache.org/thread.html/888730bd2479a9ae247e12b1f7ae6a85285feb395bdfe99c2e435a46@%3Cusers.maven.apache.org%3E]
2: As can be seen here: [https://github.com/Flowdalic/maven-transitive-dynamic-dependency]
was (Author: flowdalic):
I also run into this (and posted to [users@maven.apache.org|https://lists.apache.org/thread.html/888730bd2479a9ae247e12b1f7ae6a85285feb395bdfe99c2e435a46@%3Cusers.maven.apache.org%3E[]).|http://example.com]%29./] The issue is especially bad since this behavior is different between Maven and Gradle, [as can be seen here|[https://github.com/Flowdalic/maven-transitive-dynamic-dependency].]
I am not sure if Maven's behavior has to be changed, but it is clear to me that there is a method missing to specify all version within a version series (without pulling in alpha/beta/… releases for the following major/minor version). And the implication that using [1.0, 2.0) also includes 2.0-alpha1 should be mentioned everywhere this format is shown in the documentation.
> Version range is not resolved correctly
> ---------------------------------------
>
> Key: MNG-6232
> URL: https://issues.apache.org/jira/browse/MNG-6232
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.3.3
> Reporter: Marek Budyn
> Priority: Major
> Attachments: pom.xml
>
>
> When dependency is specified as range, e.g slf4j-api version [1.7, 1.8) as in provided pom.xml, one would expect to resolver to version 1.7.X (e.g. 1.7.25). Instead maven resolves version 1.8.0-alpha 2.
> Output of command 'mvn dependenct:tree' on provided pom.xml:
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building project 1.0.0-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ project ---
> [INFO] test:project:jar:1.0.0-SNAPSHOT
> [INFO] \- org.slf4j:slf4j-api:jar:1.8.0-alpha2:compile
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1.273 s
> [INFO] Finished at: 2017-05-12T23:37:02+02:00
> [INFO] Final Memory: 13M/225M
> [INFO] ------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)