[
https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794174#comment-17794174
]
ASF GitHub Bot commented on MNG-7532:
-------------------------------------
rmannibucau commented on PR #793:
URL: https://github.com/apache/maven/pull/793#issuecomment-1845285830
@gnodet well yes and no, original export was partial and broken but makes
6-7 years it is bothering, but anyway does not change we don't want it to
surface as a maven provided API from the previous discussions so deprecated was
a missed 3 years ago IMHO. Until we get maven 4 "1.0.0" we should just
deprecate Log and then switch to the provider Log of mvn 4 API, looks quite
straight forward to me as path, no?
> 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)
