Hi Sanne & Yoann,
OpenJDK 16 Early Access build 26**is now available at
* These early-access , open-source builds are provided under the
o GNU General Public License, version 2, with the Classpath
* Schedule: *JDK 16 Rampdown Phase One Starts on 2020/12/10  *
* Features : Most recent Integrations:
o Integrated JEP 389: Foreign Linker API (Incubator)
<https://openjdk.java.net/jeps/389> with this release.
+ JEP 389 introduces an API that offers statically-typed,
pure-Java access to native code.
+ This API, together with the JEP 383
<https://openjdk.java.net/jeps/383>, will considerably
simplify the otherwise error-prone process of binding to a
* Release Notes 
* Changes in recent builds that maybe of interest:
o Build 26
+ JDK-8202343: *Disable TLS 1.0 and 1.1*
+ JDK-8251317:**Support for CLDR version 38**
+ JDK-8212879: Make JVMTI TagMap table concurrent
+ JDK-8236926: Concurrently uncommit memory in G1
+ JDK-8243559: Removed Root Certificates with 1024-bit Keys
+ JDK-8253459: Argument index of zero or unrepresentable by
int throws IllegalFormatException
+ JDK-8256643: Terminally deprecate ThreadGroup stop, destroy,
isDestroyed, setDaemon and isDaemon
o Build 25
+ JDK-8247781: Day period support added to java.time formats
+ JDK-8202471: (ann) Cannot read type annotations on generic
receiver type's type variables *[**Reported by ByteBuddy]*
+ JDK-8255947: [macos] Signed macOS jpackage app doesn't
filter spurious '-psn' argument *[**Reported by JOSM]*
+ JDK-8256063: Module::getPackages returns the set of package
names in this module
* JDK 16 - topics of interest
o Inside Java Episode 7 “The Vector API” with John Rose and Paul
o Biased locking Obsoletion update
* Project Loom with Ron Pressler
* Update on 64-bit ARM Support for Oracle OpenJDK and Oracle JDK
Project Lanai Early-Access: EA 7 Build 16-lanai+3-278
* These early-access builds are provided under the GNU General Public
License, version 2, with the Classpath Exception
* These EA builds are produced for the purpose of gathering feedback.
Use for any other purpose is at your own risk.
* Please send feedback via e-mail to lanai-dev(a)openjdk.java.net
<mailto:email@example.com>. To send e-mail to this address
you must first subscribe to the mailing list
The Java Cryptographic Roadmap has been updated :
* Distrust TLS 1.0 and TLS 1.1 by default
o TLS protocol versions 1.0 and 1.1 are no longer considered
secure and have been superseded by more secure and modern
versions (TLS 1.2 and 1.3). This change has been integrated with
JDK 16 Early Access build 26.
* Upgrade of default algorithms used to encrypt PKCS12 keystores
o The new algorithms are based on AES-256 and SHA-256 and are
stronger than the old algorithms which were based on RC2,
DESede, and SHA-1.This change is already included in JDK 16
Early Access build 23.
Rgds, Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin, Ireland
We just published a second candidate release for Hibernate Search 6.0:
This release mainly brings a workaround for applications hanging on startup
with Spring Boot 2.3+, type parameters for type bridges and property
bridges, and an alternative, URI-based configuration for target
It also includes an upgrade to Lucene 8.7.0, Elasticsearch 7.10.0 and
Hibernate ORM 5.4.24.Final.
For more information, see our blog:
I just noticed that visiting http://hibernate.org/ (i.e. not http*s*) will
not automatically upgrade you to HTTPS, but leave you with that ugly
unsecure icon in the browser address bar. It's also what you get when
simply typing hibernate.org (i.e. 99% of users).
As search engines tend to penalize non-HTTPS these days, I'd suggest to
look into automatically upgrading if possible.
We just published two bugfix releases for Hibernate Search: 5.11.7.Final
The only significant change in these versions is the upgrade to Hibernate
ORM version 5.4.24.Final and 5.3.20.Final, respectively, in order to fix
See our blog for more information:
We just published a bugfix release for Hibernate Search: 5.11.6.Final.
This release mainly upgrades Hibernate Search to the latest compatible
Hibernate ORM version and fixes one issue with Spring 2.4.0.
See our blog for more information:
We just published the first candidate release for Hibernate Search 6.0:
Compared to Hibernate Search 5, changes are extensive, due to the API
overhaul, but with plenty of improvements: upgrades to Lucene 8 and
Elasticsearch 7 of course, but also a more concise Search DSL with typed
result types, full control on field declaration in Bridges, easier to
configure and more efficient automatic indexing, runtime joins with nested
No more changes are planned before the final release, so *this is the
perfect time to test your applications based on Hibernate Search*, and
report problems as soon as possible so that everything works perfectly as
soon as 6.0.0.Final is released.
For more information (in particular regarding migration to the new API),
see our blog: