[
https://issues.apache.org/jira/browse/DIRMINA-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018199#comment-13018199
]
Zsolt Kúti commented on DIRMINA-821:
------------------------------------
The lib dir in the distribution made me think external dependencies are all
provided.
Since it is quite possible that not all of the MINA users are familiar with
slf4j (just as it happened me), including the binding (jcl-over-slf4j) and
leaving out an implementation (or whatever they are called) makes a false
impression and confusion for users.
Either include both, or leave out both and make a note in README or changelog
that for logging users need to refer to sl4j documentation from now on.
Thanks!
> Wrong binding jar for slf4j in distribution
> -------------------------------------------
>
> Key: DIRMINA-821
> URL: https://issues.apache.org/jira/browse/DIRMINA-821
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.2
> Reporter: Zsolt Kúti
> Labels: logging
>
> On startup my app this error pops up:
> java.lang.ClassNotFoundException: org.slf4j.impl.StaticLoggerBinder
> The classpath has the following jars from the distribution's lib dir:
> slf4j-api-1.5.11.jar
> jcl-over-slf4j-1.5.11.jar
> commons-logging-1.0.3.jar
>
> slf4j site claims this exception is thrown when no binding is
> available.
> It also calims that slf4j-jcl-xxx.jar is the binding for Jakarta
> Commons Logging. This binding will delegate all SLF4J logging to JCL.
> Having put this component on classpath resolves the issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
