Skip to content

[MNG-7532] Revert MNG-6931 deprecation since list shows no consensus on that #8918

@jira-importer

Description

@jira-importer

Romain Manni-Bucau opened MNG-7532 and commented

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


Issue Links:

  • MNG-6931 Deprecate custom logging approach
    ("fixes")

  • MNG-7827 Fix org.apache.maven.plugin.logging.Log deprecation message and AbstractMojo#getLog fallback
    ("is duplicated by")

  • MNG-7827 Fix org.apache.maven.plugin.logging.Log deprecation message and AbstractMojo#getLog fallback

  • MNG-7839 Plugin v4 API should ensure class realm are fully isolated from maven.core/extensions realms (classes+resources)

Remote Links:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions