[ 
https://issues.apache.org/jira/browse/LOG4J2-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176921#comment-15176921
 ] 

Matt Sicker edited comment on LOG4J2-1303 at 3/3/16 1:36 AM:
-------------------------------------------------------------

That's all covered in the [FAQ|http://logging.apache.org/log4j/2.x/faq.html] 
and again in [Runtime 
Dependencies|http://logging.apache.org/log4j/2.x/runtime-dependencies.html], 
but I agree, the component pages should have some better intros.


was (Author: jvz):
That's all covered in the [FAQ|http://logging.apache.org/log4j/2.x/faq.html], 
but I agree, the component pages should have some better intros.

> Please provide guidance on libraries necessary for slf4j bindings
> -----------------------------------------------------------------
>
>                 Key: LOG4J2-1303
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1303
>             Project: Log4j 2
>          Issue Type: Documentation
>            Reporter: Steve Davids
>            Assignee: Matt Sicker
>
> The documentation 
> (http://logging.apache.org/log4j/2.x/log4j-slf4j-impl/index.html) is minimal 
> on the details of what dependencies you should bring in for your SLF4j to 
> properly work. The spring-boot-starter-log4j2 
> (http://central.maven.org/maven2/org/springframework/boot/spring-boot-starter-log4j2/1.3.3.RELEASE/spring-boot-starter-log4j2-1.3.3.RELEASE.pom)
>  provides a decent starting point of what is needed, but it doesn't include 
> the log4j-over-slf4j dependency for the legacy log4j 1.x which makes me 
> wonder if some logging messages are getting dropped?
> Your guidance would be greatly appreciated as to a typical app that would 
> like to use the SLF4j API + bridge support for JCL, JUL, Log4j 1.x + Log4j 
> 2.x SLF4j implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to