[
https://issues.apache.org/jira/browse/MNG-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739223#comment-17739223
]
ASF GitHub Bot commented on MNG-7827:
-------------------------------------
rmannibucau commented on PR #1187:
URL: https://github.com/apache/maven/pull/1187#issuecomment-1615094336
@cstamas this is only one of the 4-5 explaining why we must not leak our
default impl and where we didnt find an agreement in terms of api leak yes.
Note we dont want to change the logging, just keep the one we had and fix
the bug introduced in the javadoc which doesnt reflects discussion outcomes.
Technically, there are multiple cons leaking slf4j but community wise a vote
wouldnt pass but in force so both are bad.
Last is that maven didnt migrate its api to slf4j in plugin - never, we miss
several steps to say it is done so current absusive comment is even wrong - so
let's fix it, will impact nobody as of today and not mislead mojo dev.
> Fix org.apache.maven.plugin.logging.Log deprecation message and
> AbstractMojo#getLog fallback
> --------------------------------------------------------------------------------------------
>
> Key: MNG-7827
> URL: https://issues.apache.org/jira/browse/MNG-7827
> Project: Maven
> Issue Type: Improvement
> Components: Plugin API
> Affects Versions: 4.0.0-alpha-7
> Reporter: Romain Manni-Bucau
> Priority: Major
>
> In maven 4 an official Log API was created and using SLF4J as primary logging
> solution is not recommended nor the official way so javadoc and impl should
> be aligned to reflcet that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
