[
https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793613#comment-17793613
]
ASF GitHub Bot commented on MNG-7532:
-------------------------------------
cstamas commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1842590373
> Very few use slf4j since it was done in a very recent maven release and
most of plugin still comply to older api too.
Not buying this: MANY of our plugins are under maintained, are even coded
against Maven2 principles (as I noted in Slack). So, the fact they use
something old, is nothing new :smile:
First mention of use of slf4j was around 2008 in dev list (regarding Wagon
implementations, shading and all), so unsure what "recent" thing we talk about.
Maybe deprecation was "recent" yes, like many other Maven internal issues there
were stuck for over 10+ years... but that is NOT a reason to not make them
through.
> 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/[email protected]/msg123452.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
