[
https://issues.apache.org/jira/browse/LOG4J2-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733135#comment-15733135
]
Gary Gregory commented on LOG4J2-1302:
--------------------------------------
This feels wrong to me. I recognize the practical aspect of the proposed change
but it still feels like we would be working against our archtecture.
We worked hard to split API from implementation and the change would muddy the
waters again.
I wish we could come up with a different solution, from better docs to a new
module. Maybe a far jar would solve issues like this.
> 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
