[hibernate-dev] [infinispan-dev] Possible error of dependency on infinispan-query pom

[Ceki Gülcü]

Galder Zamarreño wrote:

 > Hmmm, these looks like a problem in Hibernate Search since they're the
 > ones using slf4j.
 >
 > I don't see why Infinispan Query should explicitly declare a
 > dependency on slf4j.
 >

Hello Galder,

The issue reported by Israel Lacerra, that is the NoClassDefFoundError
for org.slf4j.impl.StaticLoggerBinder, no longer occurs in SLF4J 1.6
and later. Upgrading to SLF4J v1.6 will cause the problem to
disappear.

Quoting the SLF4J manual [1]:

  Libraries

  Authors of widely-distributed components and libraries may code
  against the SLF4J interface in order to avoid imposing an logging
  framework on the end-user of the component or library. He or she may
  choose the desired logging framework at deployment time by inserting
  the desired slf4j binding on the classpath, which may be changed later
  by replacing an existing binding with another on the class path and
  restarting the application. This approach has proven to be simple and
  very robust.

  As of SLF4J version 1.6.0, if no binding is found on the class path,
  then slf4j-api will default to a no-operation implementation
  discarding all log requests. Thus, instead of throwing an exception,
  SLF4J will emit a single warning message about the absence of a
  binding and proceed to discard all log requests without further
  protest. For example, let Wombat be some biology-related framework
  depending on SLF4J for logging. In order to avoid imposing a logging
  framework on the end-user, Wombat's distribution includes
  slf4j-api.jar but no binding. Even in the absence of any SLF4J binding
  on the class path, Wombat's distribution will still work
  out-of-the-box, and without requiring the end-user to download a
  binding from SLF4J's web-site. Only when the end-user wishes to enable
  logging will she need to install a binding.

I hope this sheds lights onto the  matter,

--
Ceki

[1] http://slf4j.org/manual.html#libraries