We just released Hibernate Validator 6.1.3.Final which contains some fixes for our translations and a performance improvement for validation of executables (i.e. methods and constructors).
This is a recommended upgrade for everyone using Hibernate Validator and it is a drop-in replacement for 6.1.2.Final.
We also released 6.0.19.Final.
What’s new
Performance improvements
When validating an executable (i.e. a constructor or a method), we use its signature to retrieve the metadata of the executable in the metadata registry of Hibernate Validator.
The generation of this signature was far from optimal especially in terms of memory allocations and got greatly improved in 6.1.3.Final.
Full changelog
The complete list of fixed issues can be found on our JIRA.
Getting 6.1.3.Final
To get the release with Maven, Gradle etc. use the following GAV coordinates:
-
org.hibernate.validator:hibernate-validator:6.1.3.Final
-
org.hibernate.validator:hibernate-validator-cdi:6.1.3.Final
-
org.hibernate.validator:hibernate-validator-annotation-processor:6.1.3.Final
Note that the group id has changed from org.hibernate (Hibernate Validator 5 and earlier) to org.hibernate.validator (from Hibernate Validator 6 onwards).
Alternatively, a distribution bundle containing all the bits is provided on SourceForge (TAR.GZ, ZIP).
If you want to benefit from the new features of this version on WildFly, we also provide WildFly patches for WildFly 18 and WildFly 17.0.1. You can read about how to apply such patches here.
6.0.19.Final
We also released 6.0.19.Final with several translation fixes and the backport of the BeanMetaDataClassNormalizer introduced in 6.1 for Quarkus.
Feedback, issues, ideas?
To get in touch, use the usual channels:
-
hibernate-validator tag on Stack Overflow (usage questions)
-
User forum (usage questions, general feedback)
-
Issue tracker (bug reports, feature requests)
-
Mailing list (development-related discussions)
-
Bean Validation development mailing list (discussions about the Bean Validation specification)
