You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2022/05/20 13:36:24 UTC

[GitHub] [maven-scm] michael-o commented on pull request #142: [SCM-979] ScmLogger nonsense dropped

michael-o commented on PR #142:
URL: https://github.com/apache/maven-scm/pull/142#issuecomment-1132910707

   > Curious: Why SLF4J instead of the Log4j2-api?
   
   Our entire ecosystem is build around SLF4J
   
   > Essentially the same (logging facade) with 2 advantages:
   > 
   >     * Better process (SLF4J has had a period of almost 2 years without any release).
   
   What better process? Full of features most peole don't need? More releases aren't better. SFL4J is just a facade while Log4J2 offery EVERYTHING. There is not much you need to do if the facade is done.
   
   >     * More features (also a formatted logger).
   
   Which we don't need, we barely manage to move off string concat.
   
   At the end, we prefer over simplily rather than busload of features.
   
   Log4J2, even as an API, is a no go for me.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org