6.0 series - Hibernate ORM

Compatibility

Java	11, 17 or 18
Jakarta Persistence	3.1 and 3.0

Not compatible with your requirements? Have a look at the other series.

Documentation

Documentation for Hibernate ORM 6.0 can be accessed through the links below:

HTML API (JavaDoc)

You can find more documentation for all series on the documentation page.

How to get it

Hibernate ORM 6.0 has reached its end-of-life: we recommend that you upgrade to a newer series if possible.

Maven, Gradle...

Maven artifacts of Hibernate ORM are published to Maven Central. Most build tools fetch artifacts from Maven Central by default, but if that's not the case for you, see this page to configure your build tool.

You can find the Maven coordinates of all artifacts through the link below:

Maven artifacts

Below are the Maven coordinates of the main artifacts.

Core implementation

Spatial support

Envers audit support

HikariCP connection pooling

c3p0 connection pooling

Proxool connection pooling

JCache second-level caching

Direct download

Individual Maven artifacts may be downloaded directly from the Maven repository:

Maven Central subdirectory

See here for how to download all dependencies of your Maven project to a local directory on your filesystem.

See here for how to download an explicitly listed set of artifacts to a local directory on your filesystem.

More information about specific releases (announcements, download links) can be found here.

Getting started

Hibernate ORM 6.0 has reached its end-of-life: we recommend that you upgrade to a newer series if possible.

If you want to start using Hibernate ORM 6.0, please refer to the getting started guide:

HTML

Migrating

If you need to upgrade from a previous series, please refer to the migration guide:

HTML

What's new

Latest release announcement (2022-05-25): 6.0.2.Final.

A detailed list of new features, improvements and fixes in this series can be found on our issue tracker.

JDBC Performance

6.0 switches reading from JDBC ResultSet by name to reading by position. This required significant changes to the Hibernate type system.

HQL Translation Performance

6.0 switched from Antlr v2 to Antlr v4 for its HQL translation. Antlr v4 itself is more performant. Additionally we refactored the grammars to be more efficient

Criteria Translation Performance

In previous versions of Hibernate, JPA Criteria queries were translated by first rendering the Criteria as an HQL query. 6.0 changes this so that HQL and Criteria are both translated into the same form : the Semantic Query Model (SQM).