[
https://issues.apache.org/jira/browse/LOG4J2-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746341#comment-15746341
]
Neon commented on LOG4J2-1302:
------------------------------
well, the current documentation is misleading. it should say that it is a
log4j-api-slf4j-impl
and it should probably have not to add log4j-core as runtime dependency. e.g.
The Log4j 2 SLF4J Binding description should be updated at
https://logging.apache.org/log4j/2.0/log4j-slf4j-impl/index.html
From:
The Log4j 2 SLF4J Binding allows applications coded to the SLF4J API to use
Log4j 2 as the implementation.
To:
The Log4j 2 SLF4J Binding allows applications coded to the SLF4J API to use
Log4j 2 API as the implementation.
and maybe under Usage section: put a note, that most user's will probably add
*log4j-core* as a *runtime* dependency.
> 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
