It’s my pleasure to announce the release of Hibernate Validator 5.2.3.Final!
Wait, didn’t we already do another Hibernate Validator release earlier this month?
That’s right, indeed we pushed out the first Alpha of the 5.3 family a couple of days ago.
And normally, that’d mean that there would be no further releases of earlier version families.
But in this case we decided to do an exception from the rule as we noticed that Hibernate Validator couldn’t be used with Java 9
(check out issue HV-1048 if you are interested in the details).
As we don’t want to keep integrators and users of Hibernate Validator from testing their own software on Java 9, we decided to fix that issue on the current stable release line
(in fact we strongly encourage you to test your applications on Java 9 to learn as early as possible about any potential changes you might need to make).
I’m glad to announce the first release of the Eclipse plugin for Hibernate Search.
In this post I want to describe its features and ask you for any comments, positive or (even more important for me) negative.
It’s my pleasure to announce the first release of Hibernate Validator 5.3!
The overarching idea for the 5.3 timeline is to prototype several features which may potentially be standardized in the Bean Validation 2.0 specification.
For instance we’ll work on a solution for the long-standing request for sorting the constraints on single properties.
If you’d like to see any specific features addressed in that prototyping work (and eventually included in BV 2.0),
then please get in touch and let us know which are the most important things you are missing from the spec.
We’ve compiled a first list of issues we are considering for inclusion in BV 2.0.
For sure we cannot address all of them, so it’ll greatly help if you tell us what would be most helpful to you.
In the good spirit of open source, any Hibernate ORM issue should be accompanied by a replicating test case.
The test case is a proof that the issue really exists and is reproducible.
To simplify the test case writing procedure, Hibernate provides a series of templates that you can just grab from GitHub.
Thanks to these tests, the issue reporter can focus on the actual persistence-related problem since the templates take care of all the bootstrapping logic.
Previously, the test case templates were available only for the Hibernate native API,
which was fine as long as you’re familiar with it.
Because many projects use Hibernate as a JPA provider, it’s very convenient to offer a JPA bootstrap environment as well.
And that’s what we did.