[
https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742052#comment-17742052
]
ASF GitHub Bot commented on MNG-7532:
-------------------------------------
gnodet commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1630988003
So the problem with exporting the slf4j unmodified is that things may break
if a plugin depends on a library which itself imposes constraints on the slf4j
binding used (by configuring it programmatically for example).
By exporting the maven logging api, we ensure plugins won't be affected,
whatever libraries they have in their classloader.
It would be nice to have a project that reproduce the issues, as it's not
yet clear what kind of failure would happen. @rmannibucau ?
> 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)
