java stack is dead, long live the javastack (was "500 packages FTBFS in rawhide with java-11-openjdk as system JDK")

[Jiri Vanek]

Current stats from my testing samples:
408 failing
263 passing

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 that)?

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....

J.

[Aleksandar Kurtakov]

On Mon, Jun 29, 2020 at 2:39 PM Jiri Vanek  wrote:
> Current stats from my testing samples:
> 408 failing
> 263 passing

Are these numbers reversed ^^^ ? Looking at
https://copr.fedorainfracloud.org/coprs/g/java-maint-sig/java-11-default/mon...
I see a bit more than 200 ftbfs.
> 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
> that)?
>
> 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....
>
> J.
>
> --
> Jiri Vanek
> Senior QE engineer, OpenJDK QE lead, Mgr.
> Red Hat Czech
> [e-mail]    M: [phone]
> _______________________________________________
> java-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]...

[Jiri Vanek]

On 6/29/20 1:59 PM, Aleksandar Kurtakov wrote:
> On Mon, Jun 29, 2020 at 2:39 PM Jiri Vanek <[e-mail] > wrote:
> Current stats from my testing samples:
> 408 failing
> 263 passing
>
>
> Are these numbers reversed ^^^ ? Looking at
> https://copr.fedorainfracloud.org/coprs/g/java-maint-sig/java-11-default/mon... I see a bit more
> than 200 ftbfs.

I'm afraid not. But if you are right, then maybe I'm doing something wrong, and it is all a bit more
positive then I think.

Thanx!
> 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 that)?
>
> 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....
>
>
> J.
>
>
>
> -- 
> Jiri Vanek
> Senior QE engineer, OpenJDK QE lead, Mgr.
> Red Hat Czech
> [e-mail] <mailto:[e-mail]>    M: [phone]
> _______________________________________________
> java-devel mailing list -- [e-mail]
> <mailto:[e-mail]>
> To unsubscribe send an email to [e-mail]
> <mailto:[e-mail]>
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
>
>
>
> -- 
> Alexander Kurtakov
> Red Hat Eclipse Team
>
> java-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]...

[Aleksandar Kurtakov]

On Mon, Jun 29, 2020 at 2:39 PM Jiri Vanek  wrote:
> Current stats from my testing samples:
> 408 failing
> 263 passing
>
> 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
> that)?
>
> 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
reasons:
* 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.
> J.
>
> --
> Jiri Vanek
> Senior QE engineer, OpenJDK QE lead, Mgr.
> Red Hat Czech
> [e-mail]    M: [phone]
> _______________________________________________
> java-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]...