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

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

gnodet commented on PR #1187:
URL: https://github.com/apache/maven/pull/1187#issuecomment-1611893550

   > 2. Ensure the default is the actual maven logging system and not 
stdout/stderr directly for other cases if it is present
   
   I don't understand the actual use case.  All mojos called by maven are 
[injected with a proper 
log](https://github.com/apache/maven/blob/e08c95a6735a82c7abc25e2dc67ea4773ed9d05d/maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultMavenPluginManager.java#L557-L560)
 already.  The `SystemStreamLog` is really a fallback.  In which case would 
this new code actually be used ?




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

Reply via email to