It's also worth noting that from a security perspective continuing to support Java 8 is increasingly going to become a problem for end users. In my $dayjob we see a lot of concern about outdated software versions, even and especially so, as we move to a more containerised model. A lot of contracts are dictating security audits and mandating timelines for resolving any identified vulnerabilities. As I said previously on the discussion threads we already had to move all our runtime stuff to Java 11 because of this.
Yes any Java 8 bytecode should be forward compatible with Java 11, unless it utilises a JDK API that has changed, and users can obviously take Java 8 code and run them in Java 11 and newer. But as Aaron says it is increasingly going to prevent the project from introducing new functionality or limit our library choices. At some point we have to make the choice to move forward even if it is painful for end users. Rob On 11/01/2021, 19:54, "Aaron Coburn" <[email protected]> wrote: > > > Are you switching libs or did Titanium drop JDK 8? Titanium never supported JDK 8. It uses the java.net.http.HttpClient that is part of JDK 11. > So this is really a choice point - keep to long lived legacy > compatibility, which might be very long, or keep to some of up-to-date > rolling policy. > The central issue is that newer dependencies will begin supporting only newer Java runtimes. Titanium is just one example; others will appear in time. In this case, long-lived compatibility will be at odds with supporting JSON-LD 1.1 Aaron > > > > > 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 > > > > >
