[jira] [Commented] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584036#comment-17584036 ] 

ASF GitHub Bot commented on MNG-7532:
-------------------------------------

rmannibucau opened a new pull request, #793:
URL: https://github.com/apache/maven/pull/793

   Follow up of dev discussions and to avoid to reduplicate the API in the new plugin API, restoring `Log` official status.
   
   Following this checklist to help us incorporate your
   contribution quickly and easily:
   
    - [X] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG) filed
          for the change (usually before you start working on it).  Trivial changes like typos do not
          require a JIRA issue. Your pull request should address just this issue, without
          pulling in other changes.
    - [X] Each commit in the pull request should have a meaningful subject line and body.
    - [X] Format the pull request title like `[MNG-XXX] SUMMARY`, where you replace `MNG-XXX`
          and `SUMMARY` with the appropriate JIRA issue. Best practice is to use the JIRA issue
          title in the pull request title and in the first line of the commit message.
    - [X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    - [X] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
          be performed on your pull request automatically.
    - [ ] You have run the [Core IT][core-its] successfully.
   
   [core-its]: https://maven.apache.org/core-its/core-it-suite/
   




> 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)