[
https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794079#comment-17794079
]
ASF GitHub Bot commented on MNG-7532:
-------------------------------------
gnodet commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1844895027
IIRC, the example that was given by @rmannibucau was when a library actually
requires a given implementation of slf4j. This happens sometimes when a
library is configuring the underlying implementation programmatically.
@rmannibucau you should really come up with an IT so that we can investigate
actual problems rather than never-ending discussions on principles.
Proposal for v4 plugins. In those case, I'm not sure what happens if we
expose even the slf4j implementation.
https://github.com/apache/maven/pull/1336/files#diff-9600f93ce04acabe017b026dc1ebbb445e8cb363bb2677a764a783ab85cf804aR105-R116
I've also hit some problems with plexus logger which is now hidden, so it
needs to be configured manually:
https://github.com/apache/maven-compiler-plugin/pull/147/files#diff-d4bac42d8f4c68d397ddbaa05c1cbbed7984ef6dc0bb9ea60739df78997e99eeR597-R598
> 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)
