You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/02/27 19:04:00 UTC
[jira] [Commented] (MNG-6211) Improve relocation message
[ https://issues.apache.org/jira/browse/MNG-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498649#comment-17498649 ]
Michael Osipov commented on MNG-6211:
-------------------------------------
There was a recent change in MAven that only direct dependency relocations will be logged. I assume this has been overcome by events. [~gnodet], WDYT?
> Improve relocation message
> --------------------------
>
> Key: MNG-6211
> URL: https://issues.apache.org/jira/browse/MNG-6211
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Robert Scholte
> Priority: Major
> Fix For: 4.x / Backlog
>
>
> Consider the following setup:
> {noformat}
> A:1.0 -> B:1.1
> C:1.1 -> B:1.0
> B:1.4 >>> D:1.4
> My -> A:1.0, B:1.3, C:1.1
> {noformat}
> When upgrading My B to 1.4, I'll get a warning about the relocation. But when I replace B:1.4 with D:1.4, B:1.1 will be pulled in because it is a transitive dependency of A and because D is not aware being the relocation of B.
> In this case the relocation should be INFO, because following the instruction will have an unpleasant surprise.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)