[
https://issues.apache.org/jira/browse/MNG-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697954#comment-17697954
]
ASF GitHub Bot commented on MNG-7724:
-------------------------------------
rmannibucau commented on PR #1041:
URL: https://github.com/apache/maven/pull/1041#issuecomment-1460329789
@elharo jul is jdk14 one (the PR adds its support, was not there not sure
why), noop is kind of built-in but defeats the fact to log a warning on a
random logger (but this is another ticket/issue I guess). The root cause is
really the fact maven adds an integration layer with each slf4j implementation
so at the end can't reliably rely on the slf4j abstraction.
For maven - as of today - slf4j binding == slf4j-$impl + maven-slf4j-$impl
(in embedder module), this is what can need rework the future cause the
relationship of slf4j binding should be sufficient - fully agree with your
statement but not current state AFAIK.
> 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)
