tl;dr It'd be inconvenient but we could cope.
As you say, there is likely to remain a bimodal distribution.
We currently remain with the java 8 runtime (increasingly using AWS
Corretto). Mostly this is due to the time cost of qualifying and
updating an increasingly large number of different running systems. I
know of no technical barriers to moving to java11.
We do have at least one customer who, last we checked, was restricted
(organizationally rather than technically) to java8. To be fair, the
tool they use is not on the latest jena version anyway so we could move
to different JVM versions for that v.s. other components, but targetting
one platform is operationally easier hence sticking to java8 as the default.
Dave
On 05/01/2021 20:38, Andy Seaborne wrote:
Currently, Jena is compiled to run on any JVM from Java8 onwards.
Java8 was released March 2014.
Java11 (Sept 2018) is LTS (long term support)
Java17 (due Sept 2021) is probably going to be LTS.
Should Jena switch to Java11 going forward?
This message is to ask:
Are there deployments that do regularly upgrade can not for some reason
move to the Java11 LTS platform?
There are the usually issues of moving to a newer Java. There seems
likely to be an emerging bimodal distribution of systems remaining with
Java8 and systems moving to Java11 and Java 17 (likely an LTS -
September 2021).
The question is how many systems would upgrade their Jena version and
are restricted to Java8 (and why!).
Java is evolving to better fit in the new tech landscape (e.g. better
container usage), more compact strings (significant for Jena), and
JDK-provided HTTP/2.
Some dependences or potential dependencies are Java11:
Titanium - for JSON-LD 1.1 (JENA-1948 - titanium-json-ld )
Eclipse Jetty 10 and 11 now depend on Java11.
Andy
