Red Hat
Jul 17, 2018
by Guillaume Smet

We just released Hibernate Validator 6.0.11.Final which comes with an improved compatibility with JDK 11 and a couple of bugfixes.

This is a recommended upgrade for everyone using Hibernate Validator and it is a drop-in replacement for 6.0.10.Final in most cases (see our migration guide).

What’s new

JDK 11 support

JDK 11 does not include JAXB anymore. Instead of relying on an external dependency and because our XML descriptors are quite simple, we decided to update our XML parsing layer to use StAX directly.

Thus, you can now use Hibernate Validator with JDK 11 without adding a dependency to a JAXB implementation.

A big thanks to Marko Bekhta for his work on this task.

All our tests (except OSGi tests for which we are waiting for a Karaf update) are now run regularly with the latest JDK 11 build.

Bug fixes

The main issue we fixed is HV-1637, which caused an exception when using @DecimalMax with our German and Dutch translations.

Full changelog

The complete list of fixed issues can be found on our JIRA.

Getting 6.0.11.Final

To get the release with Maven, Gradle etc. use the GAV coordinates org.hibernate.validator:{hibernate-validator|hibernate-validator-cdi|hibernate-validator-annotation-processor}:6.0.11.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 11 and WildFly 12. You can read about how to apply such patches here.

What’s next?

Our efforts are now directed towards the new 6.1, which will introduce some structuring changes such as allowing getters with non standard names (name() instead of getName() for instance) and JSON validation support.

Feedback, issues, ideas?

To get in touch, use the usual channels:

Original Post