On Mon, Jun 29, 2020 at 2:39 PM Jiri Vanek <jvanek(a)redhat.com> wrote:
Current stats from my testing samples:
That is huge improvement. Thank you all.
I'm now running last rebuild n copr, and in week or two an mass rebuild
will be taken in koji.
There was an discussion what the border will be, when to force this
change, or when to step away.
50% of passed? 80%? But afaik no metric is valid here, because - sorry to
say it - there is no
longer any javastack...
Since f29, about 1000 java packages died or were orphaned. I was removing
packages where upstream is
dead and are orphaned (so no chance to make them reliable working with
jdk11), and I found that
wildfly, jenkins, jboss, half of maven plugins, elastic search,
apach-emina, infinispan, cassandra,
hibernate.... All are dead. What is javastack for now (no blame or evil in
So maybe the system jdk11 can be used as just last death-blow to java
stack, rethink it, and stat
rebuilding on pretty fresh field....
I think we can't delay switch to Java 11 as default any more for multiple
* Even if switch to Java 11 is delayed these packages are unlikely to be
fixed until it's inevitable
* Packages start to require Java 11 e.g. next Eclipse (Equinox OSGi, SWT,
etc.) will require Java 11 and rpm will ensure Java 11 is installed on the
user machines but as long as the system JVM is Java 8 - rpms that rely on
eclipse bits will have to ensure they set Java 11 in their startup scripts.
But even that would not ensure smooth user experience as growing part of
the java rpms will no longer be usable with the default JVM.
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jvanek(a)redhat.com M: +420775390109
java-devel mailing list -- java-devel(a)lists.fedoraproject.org
To unsubscribe send an email to java-devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
Red Hat Eclipse Team