[
https://issues.apache.org/jira/browse/LOG4J2-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15731131#comment-15731131
]
Matt Sicker commented on LOG4J2-1302:
-------------------------------------
The only reason that log4j-slf4j-impl doesn't require log4j-core is because it
only requires log4j-api. In theory, you can use any other provider that
implements log4j-api, and using log4j-slf4j-impl, you could essentially use
slf4j and have the logging framework be something other than log4j-core. I'm
not sure if there are any alternative implementations of log4j-api besides
log4j-core and log4j-to-slf4j, but it's essentially future-proofing.
> log4j-slf4j-impl should provide a runtime dependency on log4j-core
> ------------------------------------------------------------------
>
> Key: LOG4J2-1302
> URL: https://issues.apache.org/jira/browse/LOG4J2-1302
> Project: Log4j 2
> Issue Type: Improvement
> Components: SLF4J Bridge
> Reporter: Steve Davids
>
> After pulling in the log4j-slf4j-impl I was surprised to find out that I also
> needed to add the the log4j-core dependency myself instead of the dependency
> pulled in automatically from the log4j-slf4j-impl pom. I was expecting the
> behavior provided by slf4j-log4j12 which does pull in the appropriate
> implementation to get going immediately.
--
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
