[
https://issues.apache.org/jira/browse/MNG-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697798#comment-17697798
]
Romain Manni-Bucau commented on MNG-7724:
-----------------------------------------
No guys, this means maven does not allow to use slf4j bindings without maven
integration.
What is the rational then and the key feature we have in maven to justify it?
Only `fail-on-severity` flag which is almost never used (keep in mind this is
often a transversal feature instead of a maven specific one in the usage) so we
log warnings (which must be considered as error/something needing attention by
any user).
You can also note that in MavenCli this handling is specific and warning are
only issues if it is used.
So if you reject this use case you enforce any slf4j binding to integrate with
maven for a rare feature, I think this is wrong and going against the ecosystem
and the slf4j choice, minimum we can do is to reduce the logging level to say
"hey there a small toggle which will be ignored but your build is not at risk".
It has a lot of downside depending the log setup - we don't control by
contract, i put a few examples in the description but there are more.
So really think we should do something about that.
I will rework the PR to try to propose a few more precise options but closing
it is against users and usability of maven so please reopen the issue - i dont
have enough karma.
> Slf4jConfigurationFactory should use info level when there is no exception
> and the logger type is unknown
> ---------------------------------------------------------------------------------------------------------
>
> 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)
