Hey Nathan,
I like the idea in general and but you have to be careful with changing
this as I assume this was done to save memory by creating the list, only
when at least one element would be added to the list. I guess if we
always initialize the list, we'd have to do something like the follow
This is my first message posted here after I finally succeeded in
subscribing to Hibernate dev mail list.
As well known, we utilized the following 'lazy initialization' pattern
extensively in our codebase to save memory:
if ( activeFactoryNames == null ) {
activeFactoryNames = new ArrayList<
I can understand the argument "people who want to be on older versions of
Java can use older versions of Hibernate ORM/Search".
However, this strategy will only benefit the projects if we *actually* stop
working on much older versions... Experience taught me that's unlikely, and
it's even more unl
Hi Yoann,
Thanks for the update!
Rgds,Rory
On 17/08/2020 12:34, Yoann Rodiere wrote:
Hi Rory,
I confirm that Hibernate ORM and Hibernate Search build and run fine
on JDK15-ea+36.
Still no guarantee for JDK16, as Gradle is still unable to work
properly with JDK16 [1].
[1] https://github.
