[
https://issues.apache.org/jira/browse/MNG-7531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583707#comment-17583707
]
ASF GitHub Bot commented on MNG-7531:
-------------------------------------
slachiewicz commented on PR #791:
URL: https://github.com/apache/maven/pull/791#issuecomment-1224259865
Yes, we export only API, so if plugins wants own implementation - they can
use it, why not. Here we change implementation for output and that can be
changed globally (we support logback, Log4j2, slf4j and out impl) in maven
installation directory (or command line). So if plugin use slf4j simpe v 1.7 it
still should work oob i think.
> Upgrade to SLF4J 2.0.0
> ----------------------
>
> Key: MNG-7531
> URL: https://issues.apache.org/jira/browse/MNG-7531
> Project: Maven
> Issue Type: Dependency upgrade
> Reporter: Sylwester Lachiewicz
> Assignee: Sylwester Lachiewicz
> Priority: Minor
> Fix For: 3.9.0-candidate
>
>
> [https://www.slf4j.org/faq.html#changesInVersion200]
>
> Instead of "bindings" now {{org.slf4j.LoggerFactory}} searches for
> "providers". These ship for example with {_}slf4j-nop-2.0.x.jar{_},
> _slf4j-simple-2.0.x.jar_ or {_}slf4j-jdk14-2.0.x.jar{_}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
