[ 
https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793652#comment-17793652
 ] 

ASF GitHub Bot commented on MNG-7532:
-------------------------------------

rmannibucau commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1842680729

   @cstamas please just check out "slf4j plugin api" in your mailbox and check 
the related 5-6 threads, there is *NO* consensus in the community about using 
slf4j in the *api* so this is not something we can promote. Agree the community 
is split - also why we must not promote slf4j yet for plugins.
   So let's just drop the deprecation for now, and if you want we can reopen 
the debate but I kind of think maven 4 will close it by design, we all agreed 
maven 4 will abstract anything an user can rely on so there is no real point 
debating if slf4j is good or not post maven 4.
   I also understand you put slf4j everywhere but on my side of the fence, 
slf4j is almost nowhere, so status is simple:
   * yes slf4j works by a bug in extensions.xml for simple plugin
   * slf4j does not generally works as a state
   * we agreed to not aim at continuing slf4j (or any maven lib) support (by 
default - until the parent fist flag is configurable) in mojo
   
   So not sure what is really to discuss to be honest, look like you fight for 
an already finished battle :thinking: 




> 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)

Reply via email to