[
https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584273#comment-17584273
]
ASF GitHub Bot commented on MNG-7532:
-------------------------------------
ceki commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1225793381
The client facing API of SLF4J is stable and has been stable since version
1.0. You can compile an application using the API in SLF4J 1.0 (released in
2005) and it will run just fine with SLF4J version 2.0 on the classpath.
As for Maven creating its own logging API, there is a [FAQ
entry](https://www.slf4j.org/faq.html#optional_dependency) treating this
question.
Anyway, thank you all for your awesome work on Maven.
> Revert MNG-6931 deprecation since list shows no consensus on that
> -----------------------------------------------------------------
>
> Key: MNG-7532
> URL: https://issues.apache.org/jira/browse/MNG-7532
> Project: Maven
> Issue Type: Task
> Reporter: Romain Manni-Bucau
> Priority: Major
>
> There are several threads on the dev list asking for the drop of slf4j and at
> least keeping a logging abstraction for not internal dev (= core can use
> slf4j but not mojo/extensions).
> Work is being done to abstract plugin api so let's keep the
> deprecation/replacement of our Log API in this track and keep it the official
> way for now.
> one of the multiple refs:
> https://www.mail-archive.com/dev@maven.apache.org/msg123452.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
