So, today is my birthday which is in no way related to this blog post but is definitely worth knowing! This special day for me seems to be a good occasion to announce the second maintenance release of Hibernate Validator 5.3.
There has been a lot of release activity on the Hibernate front lately and it is my pleasure to announce that Hibernate Validator just joined the party with the release of Hibernate Validator 5.3.0.Final.
We are making good progress working on Bean Validation 2.0 and we decided to move the target version for BV 2.0 to Hibernate Validator 6 (see more at the end of this post!).
We did not want to leave 5.3 half backed so we are preparing a 5.3 release with bugfixes, additional translations… and a few new features. This Candidate Release 1 is the first step towards this process. Expect a quick 5.3.0.Final release after that so please test this version as thoroughly as possible and report any bugs you may find in it!
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).
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.