[
https://issues.apache.org/jira/browse/MNG-7531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583766#comment-17583766
]
ASF GitHub Bot commented on MNG-7531:
-------------------------------------
rmannibucau commented on PR #791:
URL: https://github.com/apache/maven/pull/791#issuecomment-1224382064
Where: it is a work in progress (pr available) but we know we dont promote
slf4j - already for 3.x - as a should be used api.
What breaks: plugins location slf4j from .class and creating a custom loader
from there. Severals in server area do that but also some forking cause default
classloading is not good enough, just test it.
Can be okish for v3 if you add a compat class for 1.7.x loading mecanism if
you really want this upgrade (but there is no new feature for users so really
think we can skip it).
> 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)
