While Hibernate ORM applies some more polish before releasing the final version,
so did the Hibernate Search team.
Hibernate Search version 5.4.0.CR2 is now available!
It was built and tested with Hibernate ORM 5.0.0.CR3, again we’re just waiting for that to be final but decided
to release another Candidate Release as some fixes and improvements were recently applied.
Hibernate Search sends the indexing requests in the post transaction phase.
The JMS backend can now send its indexing requests transactionally with the database changes.
Why is that useful? Read on.
When creating a bug report for any project within the Hibernate family, it’s extremely helpful (and, frankly, required)
to have an adequate test case available. This is obviously important to make reproducing the issue as easy as possible.
But it’s also vital longer-term. Nearly every bug fix should include a regression test, which is frequently based on the
original reproducer (sometimes, it’s the reproducer, verbatim).
To help create useful test cases, we’re opening up a repo with various templates. Please see the READMEs in each
project’s subdir for more info: Hibernate Test Case Templates
As a starting point, the repo contains two templates for ORM: