[
https://issues.apache.org/jira/browse/MNG-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738274#comment-17738274
]
ASF GitHub Bot commented on MNG-7827:
-------------------------------------
rmannibucau commented on PR #1187:
URL: https://github.com/apache/maven/pull/1187#issuecomment-1612018723
@gnodet good for me too, I wondered about this point too and if true we
should delete SystemStreamLog and just fail instead probably. If useful it
means we must forward the fallback to the actual expected logging system behind
`Log` and now it is v4 mecanism thanks new `Log` API, this was the intent
behind this PR but happy to just drop it too cause I share your reasoning.
> 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)
