On Sat, Oct 26, 2019 at 1:07 PM Gerald Henriksen <ghenriks(a)gmail.com> wrote:
On Sat, 26 Oct 2019 15:59:27 +0200, you wrote:
>On Sat, Oct 26, 2019 at 03:53:28PM +0200, Jiri Vanek wrote:
>> any package can switch to jdk11, but sysem jdk should be jdk8, at least for some
more time...
>
> Any reasons? Defaulting to ancient software conflicts with our “First”
foundation.
Simple reason - while Oracle decided to move Java to a faster, time
based release cycle the Java community essentially shrugged the
proverbial shoulders and ignored Oracle.
Much of the Java ecosystem is still only supported on Java 8, and if
you go to
adoptopenjdk.net the default choice remains Java 8.
Kind of like perl, gcc, kernels, and python releases. Software updates
are an inevitable part of software development. Then some excited
people go "hey, I know, let's support multiple versions of critical
software with a web of technical requirements and invent modules".
Hilarity ensue, and many painful old lessons are being rehashed in
*that* thread. But let's keep this one away from the "modularity"
adventures.
I'm afraid that Oracle inherited a lot of Sun's practices on software
versioning when they bought Java. The version naming scheme, numbering
scheme, and the release schedule, are inconsistent, unpredictable, and
cannot be relied on from Oracle's announcements, Ergo, right now,
Oracle is deprecating Java 8, and encouraging the current LTS, Java
11. Make no prodictions for the schedule or the next LTS release, this
is *right now*.
Hadoop, Tomcat, etc. all still are only supported by their
communities
on Java 8.
So while it might be noble for Fedora to try and force the issue, the
likely result is that users needing Java will simply use a different
distribution while Fedora will get a bad repuation in the Java
community.
This is unnecessary. The current consistent layout of parallel
installed versions of Java releases in /usr/lib/jvm, with consistent
release numbering, allows a predictable use of JAVA_HOME and of binary
paths to permit the use of multiple Java releases on the same host.
It's been working well this way for years.