You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Mikael Ståldal (JIRA)" <ji...@apache.org> on 2017/01/01 11:25:58 UTC
[jira] [Commented] (LOG4J2-1302) log4j-slf4j-impl should provide a
runtime dependency on log4j-core
[ https://issues.apache.org/jira/browse/LOG4J2-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15790974#comment-15790974 ]
Mikael Ståldal commented on LOG4J2-1302:
----------------------------------------
Yes, that's a good (or rather bad) example of this. I use Spark, and I have spent a lot of time on excluding dependencies to get things to work. This becomes necessary when you depend on two or more projects with transitive dependencies which conflicts.
> 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
> Assignee: Remko Popma
> Fix For: 2.8
>
>
> 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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org