Help

Hibernate Core 4.0.0.CR2 has just been released. The complete list of its changes can be found in the JIRA release notes.

  • HHH-6586 As Steve said in this post, we will continue new metamodel development after 4.0.0 release, we think the deprecation of Configuration may confuse the community, so in this issue, we removed the deprecation tag from this class, and we will continue to support this API until we get new metamodel ready, at which point this class will become deprecated and scheduled for removal in 5.0.
  • HHH-6622 Upgrade to Hibernate Commons Annotations 4.0.0.CR2, now, we have fully moved to jboss logging, no slf4j-api dependency required anymore.

The release is available from SourceForge in bundle form as well as from the JBoss Nexus repository under the org.hibernate groupId.

Enjoy!

8 comments:
 
02. Sep 2011, 07:24 CET | Link
Grzegorz Grzybek | gr.grzybek(AT)gmail.com
Please excuse if that's obvious for you/JBoss/RedHat, but why the SLF4J->jboss-logging migration?
Hibernate was (at least for me) the reason to move from JCL to SLF4J. Are you going to release some slf4j-jboss-logging-bridge?

regards
Grzegorz Grzybek
ReplyQuote
 
02. Sep 2011, 17:13 CET | Link
Bobo

I am confused as well...

 
03. Sep 2011, 19:38 CET | Link

There are a few reasons for us to go JBoss Logging. We have been working into improving log and error reports for all JBoss related projects. With JBoss logging we gain a few things:

  • log and error reports can be internationalized
  • each log / error has a unique identifier that can easily be Googled
  • each log / error is type-safe (ie log.failToLoadHibernateProperties() instead of log.fatal("Fail to load Hibernate.properties file");)
  • I have not followed closely but I think they kept a close watch on performance for JBoss Logging.

You can use the JBoss Logging -> Slf4J bridge.

 
03. Sep 2011, 19:56 CET | Link
log and error reports can be internationalized

Oh great. Was there ever a time when English log messages were an issue? I mean, did someone really complain about this? Next, localize programming language keywords.

each log / error has a unique identifier that can easily be Googled

I remember how well that worked for IBM errors in the past decades. Those who don't know history are doomed to repeat it. Also, you really are going to need that poorly maintained error database from now onto understand a colleagues problems, what with those messages being localized to Chinese.

each log / error is type-safe (ie log.failToLoadHibernateProperties() instead of log.fatal("Fail to load Hibernate.properties file");)

Sugar.

I have not followed closely but I think they kept a close watch on performance for JBoss Logging.

Which is completely irrelevant for 99% of all projects. Stop making everyone else suffer just because you think you have special requirements.

You can use the JBoss Logging -> Slf4J bridge.

Hurray! I already have four (4) dependency blocks in a regular simple web project's pom.xml only dealing with other people's broken logging dependencies. I guess five are better. (Until the next genius has a minor issue with the JDK logging API and we have six.)

 
03. Sep 2011, 20:21 CET | Link
Grzegorz Grzybek | gr.grzybek(AT)gmail.com
no slf4j-api dependency required anymore

That sounds like you've got rid of some serious disease... Now regular Hibernate users, who may use other app servers or no app servers at all have to do something about unexpected JARs in their classpaths, and learn and maintain another logging configuration... Great.

At least you've released a bridge... (is it really for SLF4J 1.5.x?) now (performance!) there will be: JBoss-Logging -> SLF4J -> Logback.

regards Grzegorz Grzybek

 
03. Sep 2011, 23:59 CET | Link
Reto Urfer
Can not find Hibernate Commons Annotations 4.0.0.CR2 in the JBoss Nexus repository under the org.hibernate groupId. WHere is it?
 
06. Sep 2011, 18:33 CET | Link
Marco Gonçalves

Great. Now I can receive a log in chinese. Should I learn chinese or try to memorize all the error codes to be efficiente in problem/bug solving?

 
14. Sep 2011, 07:55 CET | Link
ez e

Sigh.

Is there a community process? This seems, off hand, like something that would be voted down.

Post Comment