At this point, Java8 is no longer supported by Oracle. (OpenJDK and AWS Corretto will both continue to support security updates), and from what I've been seeing, much of the Java ecosystem is moving in this direction, too.
Everything I work on uses Java 11, so I am generally +1 on moving in this direction. (The ability to use Titanium is compelling for me) The steps proposed sound very reasonable to me. Aaron On Fri, 1 Jan 2021 at 09:59, Martynas Jusevičius <marty...@atomgraph.com> wrote: > I recently upgraded AtomGraph components to Java 11 and took advantage > of the -XX:MaxRAMPercentage JVM setting in a Docker setup: > https://www.eclipse.org/openj9/docs/xxinitialrampercentage/ > > On Fri, Jan 1, 2021 at 1:13 PM Andy Seaborne <a...@apache.org> wrote: > > > > Should we switch to Java11? > > > > 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. > > > > (the difference between Jetty 10 and Jetty 11 is that Jetty 10 uses the > > package root name "javax..." whereas Jetty11 uses package route > > "jakarta...") > > > > Proposal: > > > > 1/ Ask on users@ -- what we need is "new information" such as "I am > > blocked from updating Java because ...", not "I haven't got round to it". > > > > 2/ Switch to Java11 for the next release but not make so many changes > > that we can't easily go back to Java8. > > > > Andy >
