[
https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823038#comment-15823038
]
Matt Sicker commented on LOG4J2-1776:
-
As mentioned on the mailing lists, log4j-boot-
I am not sure it's a good idea to promote log4j-api as a logging facade
like slf4j. I would rather promote log4j as a complete logging solution
(api and core together), that will make it possible to eventually get rid
of the silly concept of logging facade.
On Jan 12, 2017 5:03 PM, "Matt Sicker"
Jira is down today, so I'll respond here. The log4j-boot-logback module's
intention is to promote the use of log4j-api as a general logging facade
while providing a migration path for logback users. There is still
confusion in the community of whether or not log4j-api is a replacement for
slf4j-api
[
https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15819217#comment-15819217
]
Mikael Ståldal commented on LOG4J2-1776:
Why do we have logback here?
> log4j-bo
