[
https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584321#comment-17584321
]
ASF GitHub Bot commented on MNG-7532:
-------------------------------------
ceki commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1225892740
@rmannibucau Since you mention `LocationAwareLogger`, the person who has
been been publicly and loudly complaining about `LocationAwareLogger` for the
last 12 years is the same person who asked for that breaking change in the
first place. I am sure that is a bit hard to believe but please have a look at
[SLF4J-118](https://jira.qos.ch/browse/SLF4J-118). The ticket is rather short
and quite informative in its own right.
As for stability, perhaps Maven has a higher standard regarding API
compatibility than SLF4J, as Maven really shines in that regard.
> 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)
