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 "Remko Popma (JIRA)" <ji...@apache.org> on 2016/12/14 23:22:58 UTC
[jira] [Reopened] (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:all-tabpanel ]
Remko Popma reopened LOG4J2-1302:
---------------------------------
Assignee: Remko Popma
I find the argument
{quote}
I was expecting the behavior provided by slf4j-log4j12 which does pull in the appropriate implementation to get going immediately.
{quote}
actually quite convincing.
Making this change will facilitate migration to Log4j 2.
If no objection I will add the runtime dependency in the next day or so.
> 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
>
> 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