[
https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793612#comment-17793612
]
ASF GitHub Bot commented on MNG-7532:
-------------------------------------
rmannibucau commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1842577827
@cstamas
> bet 99.999 of our users use logger just for that
99.99% uses Log facade (most of plugins just wire the logs to this interface
since it is the only one in maven api today).
Just review github and our own mojo for ex.
Very few use slf4j since it was done in a very recent maven release and most
of plugin still comply to older api too.
> Take away simplicity and availability of SLF4J API only due someone
somewhere fiddles with logging implementations
Think you miss the fact SLF4J is an *implementation* for us and a detail we
don't want to support for years cause as explained in the related threads slf4J
is *not* stable and already bite several asf project so we must only promote
*as api* something we control, this is a pure design and experience perspective.
If I'm following your reasoning we should just expose maven/lib to mojo and
I agree it is trivial to agree this is bad but all libs are available and I
don't think we use anything hard to consume so I don't think this reasoning can
last very long.
> merge this PR to not encourage people to use slf4j since we agreed it was
wrong a long time ago now
Ok, let me rephrase: "since using slf4j was agreed to be wrong, let's not
deprecate the only API we have and control and we'll bridge to mvn4 api".
The "there was never consensus" was on "moving to slf4j as api", this was
never discussed nor agreed so revert is the minimum we can do.
> For me this PR is bicycle shedding at it's best.
As explained this deprecation is a bug and was *not* intended so we should
just fix it, after we can rediscuss what we do if you feel it was right but as
of today this merge shouldn't have happent.
Agreement was on maven core code which can use slf4j as primary API, never
ever on mojo - agreement was actually the opposite.
> 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/[email protected]/msg123452.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
