[
https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793599#comment-17793599
]
ASF GitHub Bot commented on MNG-7532:
-------------------------------------
gnodet commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1842540338
> > Up, seems we are still un a broken state where we say to use slf4j for
plugins and I didn't find the mvn4 API (pretty sure you did something @gnodet
but didnt see it in mvn4 branch).
>
>
https://github.com/apache/maven/blob/master/api/maven-api-core/src/main/java/org/apache/maven/api/plugin/Log.java
>
> I'm actually working on fixing some parts in the v4 plugins, including the
class loader which should only include the Maven 4 api, so basically
`org.apache.maven.api.*` and `jakarta.inject` packages.
However, not exposing slf4j would mean we should somehow provide a bridge
from slf4j to `org.apache.maven.api.plugin.Log` so that plugins can use other
libraries but still log to the maven infrastructure.
> 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)
