[
https://issues.apache.org/jira/browse/LOG4J2-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732742#comment-15732742
]
Neon edited comment on LOG4J2-1302 at 12/8/16 5:07 PM:
-------------------------------------------------------
Generally, I don't think projects would route Slf4j logs to Log4j2 API then to
Log4j 2 core impl.
E.g. in my case I want to route Slf4j logs to Log4j 2 (impl - not API).
But I can see your point for "future-proofing" so how about a
log4j-core-slf4j-impl POM only module, that has dependency on log4j-core and
log4j-slf4j-impl ?
was (Author: neon):
I can see your point for "future-proofing" so how about a log4j-core-slf4j-impl
POM only module, that has dependency on log4j-core and log4j-slf4j-impl ?
> 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
