[
https://issues.apache.org/jira/browse/MNG-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787284#comment-17787284
]
ASF GitHub Bot commented on MNG-7854:
-------------------------------------
gnodet commented on PR #1211:
URL: https://github.com/apache/maven/pull/1211#issuecomment-1816684817
The idea looks good to me. There's one additional use case that needs to be
handled though is the following.
Let's say one or two BOMs are imported with a conflicting dependency. Maven
would print a warning that the second managed dependency is ignored. The
warning should include a way to fix the problem, which is to add an explicit
managed dependency before importing the BOMs. Once that's done, the build
should not emit a warning anymore imho, as warning with no way to fix is a bad
idea. So I think the warning should happen only if no explicit (first level)
managed dependency is registered yet. This should be the case if the BOM is
imported before the managed dep, or if there's a conflict with two BOMs.
> Imported entries that are ignored should be emitted as warning
> --------------------------------------------------------------
>
> Key: MNG-7854
> URL: https://issues.apache.org/jira/browse/MNG-7854
> Project: Maven
> Issue Type: Improvement
> Components: POM
> Reporter: Tamas Cservenak
> Priority: Major
>
> See https://github.com/cstamas/MNG-7852 for reproducer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
