Changing baseline of JGroups from JDK 11 to 17?

[Bela Ban]

Hi everybody

JGroups has been baselined on JDK 11 for a long time, and (before that) even longer on JDK 8.

I myself am running/deploying JGroups on JDK 24-open these days, with virtual threads enabled by default.

Infinispan 16 is now baselined on JDK 17, so I'm wondering if it is time to move to 17, too (records would eliminate a lot of boilerplate code). As a matter of fact, I'd prefer JDK 21, as it is the first JDK to include virtual threads.

Of course I understand those that cannot baseline their SW including JGroups to anything higher than 11.

But since I'm soon going to release 5.5, with some cool new features/improvements, I was wondering if it was time to move to a new JDK with 5.5. 5.4.x would still be baselined on JDK 11 and buf fixes would be backported.

Opinions?

[1] Move to JDK 11?
[2] Move to JDK 21?
[3] Stick with JDK 11?

-- 
Bela Ban | http://www.jgroups.org

[Neo]

Hi,

I vote [2] Move to JDK 21, and jGroup is awesome!

Bela Ban 在 2025年7月22日 星期二晚上11:41:58 [UTC+8] 的信中寫道：

[Christian Fredriksson]

Given that Infinispan is an important user of JGroups, it would make sense to move to Java 17 now and to Java 21 when Infinispan upgrades.

Java 17 brings a lot of things, Java 21 adds mostly just virtual threads.

Regards, 

Christian 

[Christian Fredriksson]

Spring also argues for staying with Java 17 for the time being:

https://spring.io/blog/2024/10/01/from-spring-framework-6-2-to-7-0#comment-6561562403

"...we see the industry and in particular the open source ecosystem rebalancing on JDK 17 at the moment"

Regards, 

Christian