You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Romain Manni-Bucau (Jira)" <ji...@apache.org> on 2022/08/24 06:54:00 UTC
[jira] [Updated] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that
[ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Romain Manni-Bucau updated MNG-7532:
------------------------------------
Description:
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
was:
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.
> 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)