[
https://issues.apache.org/jira/browse/SCM-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540134#comment-17540134
]
ASF GitHub Bot commented on SCM-979:
------------------------------------
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.
> Replace Plexus Container Default with Sisu Plexus Shim, Java8
> -------------------------------------------------------------
>
> Key: SCM-979
> URL: https://issues.apache.org/jira/browse/SCM-979
> Project: Maven SCM
> Issue Type: Task
> Reporter: Michael Osipov
> Assignee: Tamás Cservenák
> Priority: Major
> Fix For: 2.0.0-M2
>
>
> Changes:
> * make project Java8
> * update dependencies accordingly
> * remove any uses of deprecated Plexus APIs
> * replace plexus-container-default with plexus-shim
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
