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" <boa...@gmail.com> wrote: > 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 or if it's proprietary to log4j like in 1.x. > > On 11 January 2017 at 15:23, Mikael Ståldal (JIRA) <j...@apache.org> > wrote: > >> >> [ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com. >> atlassian.jira.plugin.system.issuetabpanels:comment-tabpane >> l&focusedCommentId=15819217#comment-15819217 ] >> >> Mikael Ståldal commented on LOG4J2-1776: >> ---------------------------------------- >> >> Why do we have logback here? >> >> > log4j-boot pom modules for dependency management >> > ------------------------------------------------ >> > >> > Key: LOG4J2-1776 >> > URL: https://issues.apache.org/jira/browse/LOG4J2-1776 >> > Project: Log4j 2 >> > Issue Type: New Feature >> > Components: Boot >> > Reporter: Matt Sicker >> > >> > This is the main feature for the Log4j Boot epic (LOG4J2-1775). >> > {code} >> > groupId: org.apache.logging.log4j.boot >> > artifactId: log4j-boot-* >> > {code} >> > * core: just log4j-core basically >> > * async (for AsyncLogger; brings in LMAX disruptor) >> > * log4j-spi: log4j-slf4j-impl, log4j-jul, log4j-jcl, log4j-1.2-api >> > * slf4j-spi: slf4j-impl, jcl-over-slf4j, jul-to-slf4j (same dependency >> set as spring-boot-starter-log4j2) >> > * logback (for log4j-to-slf4j, slf4j-spi, logback; this helps aid >> migration to log4j-api and promotes it as a general use logging API) >> > * advertiser-jmdns >> > * appender-async-conversant >> > * appender-async-jctools >> > * appender-cassandra >> > * appender-couchdb >> > * appender-jms >> > * appender-jpa >> > * appender-kafka >> > * appender-mongodb >> > * appender-smtp >> > * appender-zeromq >> > * config-json >> > * config-yaml >> > * layout-csv >> > * layout-jansi (for windows users and coloured log messages) >> > * layout-json (unless this has been ported to not require jackson >> anymore?) >> > * layout-xml >> > * layout-yaml >> > * script-groovy >> > I may have missed a few, but the base set of starters should at least >> correspond to all optional dependencies in log4j-core or the addon modules. >> For the jms, jpa, and smtp (log4j-core) appenders, we could either make add >> in a default provider (e.g., ActiveMQ, Hibernate, and Sun Mail >> respectively) or split those into provider-specific starters. >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v6.3.4#6332) >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org >> For additional commands, e-mail: log4j-dev-h...@logging.apache.org >> >> > > > -- > Matt Sicker <boa...@gmail.com> >
