[
https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738719#comment-17738719
]
ASF GitHub Bot commented on MNG-7532:
-------------------------------------
slawekjaranowski commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1613588496
For Maven plugins we can provide own API or abstraction ... but users can
use third party library for implementing plugin code.
We can not expect that all code in plugins only use Maven and JDK API, thirt
party library used in plugins code can uses any logging framework.
It should not be important what logging framework is used in Maven core.
Technically we can forward logging message from one framework to another and
it can be transparent for plugins code.
So I'm for not providing next abstraction but allow users use some of
commonly available frameworks, like spring-boot does:
https://docs.spring.io/spring-boot/docs/current/reference/html/features.html#features.logging
> 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)
