[jira] [Comment Edited] (MRESOLVER-379) Problem when relocations and ranges are used in collection

["wei cai (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MRESOLVER-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739275#comment-17739275 ] 

wei cai edited comment on MRESOLVER-379 at 7/1/23 7:07 AM:
-----------------------------------------------------------

[~cstamas] 

If run mvn dependency:tree, both df & bf prints 
{code:java}
A1
+- C3 {code}
Not quite get the issue, but the above behavior makes sense, user declare a dependency with version range, it actually means it would depend on one specific version, print all available versions is not necessary.

Probably typo in the comment? You actually mean with maven-resolver code, the dirty tree differs as below (which is expected as you mentioned):

DF
{code:java}
A1 
+- C1
+- C2
+- C3{code}
BF
{code:java}
A1 
+- C3
+- C2
+- C1 {code}
MNG-3454 is a bit different, it says a dependency was relocated another dependency with different version like A 1.0 -> B 2.0


was (Author: wecai):
[~cstamas] 

If run mvn dependency:tree, both df & bf prints 
{code:java}
A1
+- C3 {code}
Not quite get the issue, but the above behavior makes sense, user declare a dependency with version range, it actually means it would depend on one specific version, print all available versions is not necessary.

MNG-3454 is a bit different, it says a dependency was relocated another dependency with different version like A 1.0 -> B 2.0

> Problem when relocations and ranges are used in collection
> ----------------------------------------------------------
>
>                 Key: MRESOLVER-379
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-379
>             Project: Maven Resolver
>          Issue Type: Bug
>          Components: Resolver
>            Reporter: Tamas Cservenak
>            Priority: Major
>
> Affects both old DF and new BF collectors.
> Example:
> * A1 -> B[1,3]
> * B1 relocated to C1
> * B2 relocated to C2
> * B3 relocated to C3
> In this example, as output of collection dirty tree (verbose) I'd expect:
> {noformat}
> A1
> +- C1
> +- C2
> +- C3
> {noformat}
> But none of the DF or BF produce this, moreover, they produce DIFFERENT outputs:
> DF does this:
> {noformat}
> A1
> +- C1
> {noformat}
> BF does this:
> {noformat}
> A1
> +- C3
> {noformat}
> Cause is probably as BF "reverse sort" versions, but none will return proper range.
> Real life example: MRESOLVER-376, where junit:junit-dep:[4.9,) range "maps itself" onto junit:junit versions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)