The Hibernate team is proud to announce the release of ORM 5.1 which includes a number of new features and enhancements, including:
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.
The 7th bug-fix release for Hibernate ORM 5.0 has just been tagged and published.
5.5.2.Final is now available, our latest stable version sporting integration with Hibernate ORM 5 and Apache Lucene 5.3 - the state of the art.
Creating this version to be compatible with these two great OSS projects kept us busy for a good deal of this past year; I remember discussing this option with superstar OSS contributors Uwe Schindler (Apache Lucene developer) and Gustavo Nalle (Infinispan developer) at FOSDEM in January 2015! I am grateful to both for their guidance and suggestions, as driving progress forward is sometimes challenging when we strive to keep backwards compatibility as best as we can.
On top of that, our same small but amazing team as been working hard on Hibernate OGM 5, a bit of Hibernate Validator, incredible performance improvements on Hibernate ORM "classic" and is still tinkering on the internals of Hibernate Search to make an Elasticsearch backend an alternative to plain Lucene.
It’s 3 days from Christmas and as a present we decided to release the first Beta of Hibernate OGM 5!
This release also continue the process of aligning Hibernate OGM to the Hibernate 5 family. After the passage to Hibernate ORM 5 in the previous release, we updated Hibernate Search to the 5.5 version that also includes the power of Apache Lucene 5.
In the previous release post we described the improvements about storing map-typed properties on MongoDB and Redis. We have now applied the same natural mapping on CouchDB.
Check out the Hibernate OGM migration notes to learn more about migrating from earlier versions of Hibernate OGM to 5.x.
Hibernate ORM 5.0.6.Final has just been tagged and published. This release has been done on an accelerated timebox of 2 weeks (from the normal 4 weeks for bugfix releases) due to US holidays.
The 5th bug-fix release for Hibernate ORM 5.0 has just been tagged and published. This release and the upcoming 5.0.6 release have been done on an accelerated timebox of 2 weeks (from the normal 4 weeks for bugfix releases) due to US holidays.
Hibernate Search 5.5.1.Final is now available!
Feedback about our recent
5.5.0.Final release has been great, and while the good news is that nobody reported significant issues,
some people also pointed out that the new sorting system was a bit limited.
So we’ve been working on enhancing the
FieldBridge API to make sure that those more expert users who implement their
own bridging would have a better control on how sorting works as well.
We’ve also started some work to push the performance higher, and overall I’m proud to state that this
is including some small internal polish, but results in measurable improvements.