[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Sicker updated LOG4J2-1776: -------------------------------- Description: 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) * 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. was: This is the main feature for the Log4j Starter epic (LOG4J2-1775). {code} groupId: org.apache.logging.log4j.starter artifactId: log4j-starter-* {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) * 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. > 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) > * 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