Compatibility
| Java | 17, 21 or 22 |
| Jakarta Bean Validation | 3.1 |
| Jakarta EE | 11 |
Not compatible with your requirements? Have a look at the other series.
See also the Compatibility policy and Maintenance policy.
Documentation
Documentation for Hibernate Validator 9.0 can be accessed through the links below:
You can find more documentation for all series on the documentation page.
How to get it
More information about specific releases (announcements, download links) can be found here.
Getting started
If you want to start using Hibernate Validator 9.0, please refer to the getting started guide:
Migrating
If you need to upgrade from a previous series, please refer to the migration guide:
What's new
|
Hibernate Validator 9.0 is still in development:
We encourage you to give it a try and to let us know of any bugs or problems you encounter. |
Latest release announcement (2024-09-04): 9.0.0.Beta3.
A detailed list of new features, improvements and fixes in this series can be found on our issue tracker.
Jakarta EE 11
Hibernate Validator 9.0 is targeted to be the reference implementation for Jakarta Bean Validation 3.1 in Jakarta EE 11.
Upgrade to Hibernate Validator 9 is required if you are moving to Jakarta EE 11.
With Jakarta EE 11 upgrade the minimum required Java version is 17.
New constraints
This release also brings new constraints.
Country-specific South Korean RRN constraint
The new constraint @KorRRN was added to validate the Korean resident registration numbers.
Hibernate Validator BOM
Hibernate Validator now offers a BOM providing dependency management for all of its published artifacts. It can be imported as part of your dependency management to keep the versions of Hibernate Validator artifacts aligned.
Removal of the Security Manager integration
With the security manager being deprecated without an alternative for some time now, we took the opportunity provided by the specification requirement of the minimum Java version to remove the integration of the Security Manager from Hibernate Validator.
Removal of the deprecated constraints, configuration properties and methods
With the new major release of Hibernate Validator some of the constraints, configuration properties, and public API methods/classes that have been deprecated for a few major versions now are removed. For a detailed list of removed deprecated items see the migration guide.
OSGi integration
Starting with Hibernate Validator 9.0, the Hibernate team no longer tests nor maintains the OSGi integration. For users who would want to experiment with Hibernate Validator in an OSGi environment, we will keep the existing manifest entries in place as they were.
|
Even though we no longer maintain the Hibernate Validator OSGi integration, we do encourage the community members interested in it to come forward with pull requests if they encounter some issues. In such a case, we will try to guide the submitter through the contribution process and assess the suggested patch for inclusion in the build. |
Development versions (SNAPSHOTS)
The latest development versions of Maven artifacts for Hibernate Validator are published to the OSSRH snapshots repository.
You should only need those (unstable) versions for testing recently merged patches, and should never use them in production.
To consume these artifacts, you may need to configure your build tool to fetch artifacts
from
https://oss.sonatype.org/content/repositories/snapshots
and to enable snapshots:
Releases in this series
More removals of deprecated methods and constraints, clarification on stopping OSGi integration testing, a couple improvements and fixes identified while testing the previous beta release against downstream projects.
Maven artifacts Download Resolved issues Release announcement
This series targets Jakarta EE 11. It implements Jakarta Validation 3.1. New constraints: @KorRRN, @BitcoinAddress, removal of the Security Manager integration, BOM for simpler dependency management, dependency updates, improvements and bug fixes.
Maven artifacts Download Resolved issues Release announcement
