[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3486) Include one ore more SLF4J "adapters"

[Ceki Gulcu (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34563#action_34563 ] 

Ceki Gulcu commented on HHH-3486:
---------------------------------

Please consider the fact that SLF4J version 1.4.0 and later output a
warning message in case the slf4j binding is missing. (SLF4J version
1.4.0 was released on May 16th 2007, i.e 30 months ago.)

The warning message states the following:

  Failed to load class "org.slf4j.impl.StaticLoggerBinder
  See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details

Visiting the aforementioned link, you will read:

  Failed to load class org.slf4j.impl.StaticLoggerBinder

  This error is reported when the org.slf4j.impl.StaticLoggerBinder
  class could not be loaded into memory. This happens when no
  appropriate SLF4J binding could be found on the class path. Placing
  one (and only one) of slf4j-nop.jar, slf4j-simple.jar,
  slf4j-log4j12.jar, slf4j-jdk14.jar or logback-classic.jar on the class
  path should solve the problem.

  You can download SLF4J bindings from the project download page
  (http://www.slf4j.org/download.html).

Thus, we have already put in place a runtime guide in order to help
the user tackle this issue. Instead of adding a build-time dependency
to hibernate (which would be quite detrimental), I believe that
improving this guide would be the most helpful approach going forward.


> Include one ore more SLF4J "adapters"
> -------------------------------------
>
>                 Key: HHH-3486
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3486
>             Project: Hibernate Core
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 3.3.0.GA, 3.3.0.SP1, 3.3.1
>            Reporter: Chris Bredesen
>            Assignee: Steve Ebersole
>
> Hibernate, as of 3.3, no longer distributes all jars needed to run the framework.  SLF4J requires the inclusion of the SLF4J library as well as either a native or a wrapped implementation.  The manual vaguely references such a need but it's never quite clear that the user must visit the SLF4J website and obtain these jars himself.  Maven users are of course unaffected since the additional SLF4J jars are published in the central repo.
> "Adapter" may be the wrong term here but I think the point has been made :)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira