[
https://issues.apache.org/jira/browse/MNG-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703783#comment-17703783
]
ASF GitHub Bot commented on MNG-7724:
-------------------------------------
rmannibucau commented on PR #1051:
URL: https://github.com/apache/maven/pull/1051#issuecomment-1480213176
@slachiewicz not differently than today, keep in mind it was already not
working since it was using the broken logger setup to log, only actual useful
logging was the printstacktrace on stderr (without logger) when the integration
was not working which can't happen here since this init is done before the init
so tempted to say we support your case dropping the code ;).
> 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
> Assignee: Elliotte Rusty Harold
> Priority: Minor
> Fix For: 4.0.0-alpha-5
>
>
> 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)
