On 05/01/2021 22:46, Steve Vestal wrote:
Support for JAXB was removed from Java11. For those using that and Jena
in osgi bundles (e.g., Eclipse plugins), my impression from some initial
experimenting and searching is that a bit of wizardry is needed to add
that on the side and get it working. I could not find a clean and
simple solution online. If anyone knows of one, let me know.
Steve,
JABX - and others - have been moved out into self-contained maven artifacts.
https://repo1.maven.org/maven2/javax/xml/jaxb-api/
jena-geosparql uses jaxb-api and compiles for Java11.
Is there something apache-jena-osgi needs to do?
I have been using Jena with JDK11 for sometime - not OSGi - and haven't
had problems or needsed to make adjustments that I recall. I don't
understand OSGi enough to see why it makes a difference.
Andy
On 1/5/2021 2:38 PM, 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
