[
https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738902#comment-17738902
]
ASF GitHub Bot commented on MNG-7532:
-------------------------------------
rmannibucau commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1614186284
@slachiewicz if we switch we should just go to JUL IMHO (see the list for
details) but not sure it would be for v4, hopefully v5. Anyway, does not change
anything to the fact we don't want to show our impl to end users since one
feature we provide is the hability to integrator to handle it as they want. All
log libs have pitfalls and we can't make everything working (typically there
are some cases with some bridge which will fail), so let's stay simple and 1.
drop slf4j from consumers view in code, 2. if we need to change current impl
move to JUL which enables to be dep free, abstract any impl (several asf
projects do like cxf) and work in all integrator env without hacks.
> 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)
