[
https://issues.apache.org/jira/browse/MNG-7531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583690#comment-17583690
]
ASF GitHub Bot commented on MNG-7531:
-------------------------------------
rmannibucau commented on PR #791:
URL: https://github.com/apache/maven/pull/791#issuecomment-1224239819
@slachiewicz a lot of plugins can - and do - rely on the provided slf4j-api
at maven level (since most of the API is sadly exported and available using
`ClassRealm` hierarchy). Upgrading to 2.x is not a transparent upgrade, in
particular when the mojo overrides the binding (for good or bad reasons). This
implies that functional logging will end up in something different (`No SLF4J
providers were found.` for ex. Since for v4 `org.slf4j` must not be exposed
(replaced by actual logging api and mojo related api) I think we should skip
slf4j upgrade until we cleaned up our api leaks.
> 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)
