+1 to bumping version number, it is clearly a breaking change.
Dave On 11/01/2021 12:59, Andrii Berezovskyi wrote:
Hello, Just noticed that the discussion went really fast. I am a maintainer for Eclipse Lyo and as an integration SDK, we ship JDK 8 library builds for wide compat (with Jena dependency). Our GH Actions build matrix succeeds on JDK 8, 11, 15, 16-ea, and 17-ea but this change will be breaking for us. To be clear, we build our libraries under JDK 8 and use them under JDK 11+ where possible, so we do take advantage of better Docker compat and TLS improvements. 1) Could you please consider bumping the Jena version to 4.0 as this is a breaking change? 2) Is it possible to designate some 3.x version to receive security fixes (I think Jackson is the biggest offender we see in our GH/Snyk reports) for some time after 4.0 release? I have seen reports that RDF* brings some problems to old users, so perhaps a version before that? Lyo 4.0 is on Jena 3.15 and Lyo 4.1.alpha is on 3.17 - for now without issues. I think JDK 8 support (non-Oracle) will generally stop around 2026 (https://aws.amazon.com/corretto/faqs/ and https://adoptopenjdk.net/support.html) and many integration projects are not eager to move (I just forwarded this thread to our mailing list and asked our users to begin testing their integration projects with JDK 11 but we will see). 3) How much trouble would it be to keep a JDK8 build of Jena without a new JSON-LD library? Are you switching libs or did Titanium drop JDK 8? Thank you. -- Best regards, Andrew Berezovskyi On 2021-01-08 , at 23:45, Andy Seaborne <[email protected]<mailto:[email protected]>> wrote: The Jena build has been switched to produce Java11 bytecode. Nothing else in the codebase has been changed so this is easily reversible at the moment. Using SNAPSHOT artifacts will get you Java11 bytecode. There is currently some problems producing javadoc One problem is [1] on early Java11 releases (11.0.1, 11.0.2, but not the GA release 11.0.0). Update-to-date Java11 is now 11.0.9 and works Another is overlapping packages across modules using automatic module naming. These do not affect the running of Jena. Andy [1] https://bugs.openjdk.java.net/browse/JDK-8212233
