[
https://issues.apache.org/jira/browse/MNG-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697888#comment-17697888
]
Elliotte Rusty Harold commented on MNG-7724:
--------------------------------------------
One more time: if a project chooses to fail on *warnings* that's there issue,
not ours. We should not adjust our code to suit their idiosyncratic code
bureaucracy.
It sounds like maybe this shouldn't log at all. That is, this issue is simply
not a problem. The code runs fine. If so, turn it off completely. But if it is
a problem, then make it a warning, not info.
> Don't log warnings when runtime is not broken (slf4j integrations)
> ------------------------------------------------------------------
>
> Key: MNG-7724
> URL: https://issues.apache.org/jira/browse/MNG-7724
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 4.0.0-alpha-4
> Reporter: Romain Manni-Bucau
> Priority: Minor
>
> As of now if we change the SLF4J bindings maven will issue warnings because a
> few features are disabled but due to the nature of switching these bindings
> it is highly likely it is intended and therefore the warning are misleading
> more than helping.
> The solution can be to log a warning if a configured factory fails to load
> but just log info when it succeeds.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
