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.



-- 
Jiri Vanek
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jvanek(a)redhat.com    M: [phone]

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

[Aleksandar Kurtakov]

On Mon, Jun 29, 2020 at 2:39 PM Jiri Vanek <jvanek(a)redhat.com&gt; 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/...
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
>  jvanek(a)redhat.com    M: [phone]
>  _______________________________________________
>  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:
>  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

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

[Jiri Vanek]

On 6/29/20 1:59 PM, Aleksandar Kurtakov wrote:
>  
>  
>  On Mon, Jun 29, 2020 at 2:39 PM Jiri Vanek <jvanek(a)redhat.com
> <mailto:[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/... 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
>      jvanek(a)redhat.com <mailto:[e-mail]>    M: [phone]
>      _______________________________________________
>      java-devel mailing list -- java-devel(a)lists.fedoraproject.org
>      <mailto:[e-mail]>
>      To unsubscribe send an email to java-devel-leave(a)lists.fedoraproject.org
>      <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 -- java-devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to java-devel-leave(a)lists.fedoraproject.org
>  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
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jvanek(a)redhat.com    M: [phone]

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

[Fabio Valentini]

On Tue, Jun 30, 2020 at 9:52 AM Jiri Vanek <jvanek(a)redhat.com&gt; wrote:
>  On 6/29/20 1:59 PM, Aleksandar Kurtakov wrote:
>  >
>  >
>  > On Mon, Jun 29, 2020 at 2:39 PM Jiri Vanek <jvanek(a)redhat.com
> <mailto:[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/... 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! 
I don't know if I've set up the Java SIG COPR for Java 11 rebuilds
differently than you set up yours. Maybe you haven't incorporated the
xmvn-javadoc change yet? It could explain the ~200 additional build
failures.

Looking at the latest state in our COPR test repo, I see 202 failing
packages and 461 building packages, which isn't looking too bad
considering how the numbers looked at the start.

>      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.... 
Why? If nobody needs those packages and nobody wants to maintain them,
then they should stay dead.

Right now, the core Java stack (including everything that's necessary
to build itself) amounts to about 200 packages, which is already a lot
of packages for limited manpower (Stewardship SIG / Java SIG). Unless
somebody wants to step up (or Red Hat actually wants its Java projects
packaged for fedora again), this is not going to change, I'm afraid.

Fabio

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

[Aleksandar Kurtakov]

Fabio, does it mean that the Java SIG agrees with progressing with the
Change to Java 11 as a default?

On Wed, Jul 1, 2020 at 4:02 PM Fabio Valentini <decathorpe(a)gmail.com&gt; wrote:

>  On Tue, Jun 30, 2020 at 9:52 AM Jiri Vanek <jvanek(a)redhat.com&gt;
> wrote:
>  >
>  > On 6/29/20 1:59 PM, Aleksandar Kurtakov wrote:
>  > >
>  > >
>  > > On Mon, Jun 29, 2020 at 2:39 PM Jiri Vanek <jvanek(a)redhat.com <mailto:
>  jvanek(a)redhat.com&gt;&gt; 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/...
>  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!
>
>  I don't know if I've set up the Java SIG COPR for Java 11 rebuilds
>  differently than you set up yours. Maybe you haven't incorporated the
>  xmvn-javadoc change yet? It could explain the ~200 additional build
>  failures.
>
>  Looking at the latest state in our COPR test repo, I see 202 failing
>  packages and 461 building packages, which isn't looking too bad
>  considering how the numbers looked at the start.
>
>  >     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....
>
>  Why? If nobody needs those packages and nobody wants to maintain them,
>  then they should stay dead.
>
>  Right now, the core Java stack (including everything that's necessary
>  to build itself) amounts to about 200 packages, which is already a lot
>  of packages for limited manpower (Stewardship SIG / Java SIG). Unless
>  somebody wants to step up (or Red Hat actually wants its Java projects
>  packaged for fedora again), this is not going to change, I'm afraid.
>
>  Fabio
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  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

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

[Fabio Valentini]

On Wed, Jul 1, 2020 at 3:09 PM Aleksandar Kurtakov <akurtako(a)redhat.com&gt; wrote:
>  Fabio, does it mean that the Java SIG agrees with progressing with the Change to Java 11
> as a default? 
Speaking for myself, yes.

I can't speak for all other SIG members (we haven't formally voted on
this or something like that), but from conversations we've had I
gather that all active package maintainers are looking forward to
finally getting Java 11 by default.

Fabio

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

[Alex Scheel]

----- Original Message -----
>  From: "Fabio Valentini" <decathorpe(a)gmail.com&gt;
>  To: "Development discussions related to Fedora"
> <devel(a)lists.fedoraproject.org&gt;
>  Sent: Wednesday, July 1, 2020 9:21:31 AM
>  Subject: Re: [fedora-java] Re: java stack is dead, long live the javastack (was "500
> packages FTBFS in rawhide with
>  java-11-openjdk as system JDK")
>  
>  On Wed, Jul 1, 2020 at 3:09 PM Aleksandar Kurtakov <akurtako(a)redhat.com&gt;
>  wrote:
>  >
>  > Fabio, does it mean that the Java SIG agrees with progressing with the
>  > Change to Java 11 as a default?
>  
>  Speaking for myself, yes.
>  
>  I can't speak for all other SIG members (we haven't formally voted on
>  this or something like that), but from conversations we've had I
>  gather that all active package maintainers are looking forward to
>  finally getting Java 11 by default. 
Speaking on behalf of the Dogtag team, we too are fine with Java 11 change.

(Technically we're the next most active members of the Stewardship SIG,
 and I guess we're part of Java Maint SIG but we've not yet contributed
 in that capacity).

We're mostly there, but still need upstream CI in place to prevent
regressions and ensure we fix problems before they get started.

Plus, Debian has already made this change so we're going to need this
eventually. RHEL will get there too.


My personal preference is to get the Stewardship SIG's top-level packages
building (iirc, Eclipse, Dogtag, and Libreoffice) on Java 11 and then we'll
let the rest drop. IIRC most of the 200 packages not building in our COPR
aren't pulled in by Dogtag so we're mostly fine once we fix our top-level
Dogtag package.



- Alex



>  
>  Fabio
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  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]
>

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

[Aleksandar Kurtakov]

On Wed, Jul 1, 2020 at 4:50 PM Alex Scheel <ascheel(a)redhat.com&gt; wrote:

>  ----- Original Message -----
>  > From: "Fabio Valentini" <decathorpe(a)gmail.com&gt;
>  > To: "Development discussions related to Fedora" <
>  devel(a)lists.fedoraproject.org&gt;
>  > Sent: Wednesday, July 1, 2020 9:21:31 AM
>  > Subject: Re: [fedora-java] Re: java stack is dead, long live the
>  javastack (was "500 packages FTBFS in rawhide with
>  > java-11-openjdk as system JDK")
>  >
>  > On Wed, Jul 1, 2020 at 3:09 PM Aleksandar Kurtakov <akurtako(a)redhat.com&gt;
>  > wrote:
>  > >
>  > > Fabio, does it mean that the Java SIG agrees with progressing with the
>  > > Change to Java 11 as a default?
>  >
>  > Speaking for myself, yes.
>  >
>  > I can't speak for all other SIG members (we haven't formally voted on
>  > this or something like that), but from conversations we've had I
>  > gather that all active package maintainers are looking forward to
>  > finally getting Java 11 by default.
>
>  Speaking on behalf of the Dogtag team, we too are fine with Java 11 change.
>
>  (Technically we're the next most active members of the Stewardship SIG,
>   and I guess we're part of Java Maint SIG but we've not yet contributed
>   in that capacity).
>
>  We're mostly there, but still need upstream CI in place to prevent
>  regressions and ensure we fix problems before they get started.
>
>  Plus, Debian has already made this change so we're going to need this
>  eventually. RHEL will get there too.
>
>
>  My personal preference is to get the Stewardship SIG's top-level packages
>  building (iirc, Eclipse, Dogtag, and Libreoffice) on Java 11 and then we'll
>  let the rest drop. 

Eclipse stack (incl. build deps) should be Java 11 ready as we speak (minus
few dependencies in the work).
Furthermore Eclipse will require Java 11 in its September release upstream .


>  IIRC most of the 200 packages not building in our COPR
>  aren't pulled in by Dogtag so we're mostly fine once we fix our top-level
>  Dogtag package.
>
>
>
>  - Alex
>
>
>
>  >
>  > Fabio
>  > _______________________________________________
>  > devel mailing list -- devel(a)lists.fedoraproject.org
>  > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  > 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]
>  >
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  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

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

[Jiri Vanek]

On 7/1/20 3:21 PM, Fabio Valentini wrote:
>  On Wed, Jul 1, 2020 at 3:09 PM Aleksandar Kurtakov
> <akurtako(a)redhat.com&gt; wrote:
> >
> > Fabio, does it mean that the Java SIG agrees with progressing with the Change to Java
> 11 as a default?
>  
>  Speaking for myself, yes.
>  
>  I can't speak for all other SIG members (we haven't formally voted on
>  this or something like that), but from conversations we've had I
>  gather that all active package maintainers are looking forward to
>  finally getting Java 11 by default. 
Yes, despite many soon FTBFS and thus soon orphaned pkgs, It looks taht active people wish
to
proceed with change, rather then doing the possibly clumsy step back.

I'm progressing toward the mass rebuild in side tag.

I'm aware about three packages needing  commits to change - java-11-openjdk,
java-1.8.0-openjdk and
javapackages-tools.

Fabio, saying "you have not got xmvn change", Is tere something I need to check
for?

Thanx!
 J.
>  
>  Fabio
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  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
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jvanek(a)redhat.com    M: [phone]

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

[Fabio Valentini]

On Wed, Jul 1, 2020 at 4:00 PM Jiri Vanek <jvanek(a)redhat.com&gt; wrote:
>  On 7/1/20 3:21 PM, Fabio Valentini wrote:
>  > On Wed, Jul 1, 2020 at 3:09 PM Aleksandar Kurtakov <akurtako(a)redhat.com&gt;
> wrote:
>  >>
>  >> Fabio, does it mean that the Java SIG agrees with progressing with the Change to
> Java 11 as a default?
>  >
>  > Speaking for myself, yes.
>  >
>  > I can't speak for all other SIG members (we haven't formally voted on
>  > this or something like that), but from conversations we've had I
>  > gather that all active package maintainers are looking forward to
>  > finally getting Java 11 by default.
>
>  Yes, despite many soon FTBFS and thus soon orphaned pkgs, It looks taht active people
> wish to
>  proceed with change, rather then doing the possibly clumsy step back.
>
>  I'm progressing toward the mass rebuild in side tag.
>
>  I'm aware about three packages needing  commits to change - java-11-openjdk,
> java-1.8.0-openjdk and
>  javapackages-tools.
>
>  Fabio, saying "you have not got xmvn change", Is tere something I need to check
> for? 
I was wondering whether you had included javapackages-tools in the
COPR with the second commit from the PR:
https://src.fedoraproject.org/rpms/javapackages-tools/pull-request/3#comm...

Fabio

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

[Jiri Vanek]

On 7/1/20 4:09 PM, Fabio Valentini wrote:
>  On Wed, Jul 1, 2020 at 4:00 PM Jiri Vanek <jvanek(a)redhat.com&gt;
> wrote:
> >
> > On 7/1/20 3:21 PM, Fabio Valentini wrote:
> >> On Wed, Jul 1, 2020 at 3:09 PM Aleksandar Kurtakov <akurtako(a)redhat.com&gt;
> wrote:
> >>>
> >>> Fabio, does it mean that the Java SIG agrees with progressing with the Change
> to Java 11 as a default?
> >>
> >> Speaking for myself, yes.
> >>
> >> I can't speak for all other SIG members (we haven't formally voted on
> >> this or something like that), but from conversations we've had I
> >> gather that all active package maintainers are looking forward to
> >> finally getting Java 11 by default.
> >
> > Yes, despite many soon FTBFS and thus soon orphaned pkgs, It looks taht active people
> wish to
> > proceed with change, rather then doing the possibly clumsy step back.
> >
> > I'm progressing toward the mass rebuild in side tag.
> >
> > I'm aware about three packages needing  commits to change - java-11-openjdk,
> java-1.8.0-openjdk and
> > javapackages-tools.
> >
> > Fabio, saying "you have not got xmvn change", Is tere something I need to
> check for?
>  
>  I was wondering whether you had included javapackages-tools in the
>  COPR with the second commit from the PR:
>  https://src.fedoraproject.org/rpms/javapackages-tools/pull-request/3#comm... 
The PR do not bump the release, so hard to say, but form:
https://copr.fedorainfracloud.org/coprs/jvanek/java11/package/javapackage...
I guess yes, becasue there wasautobuild 21days ago. Same age as commit landed to
javapackages-tools
ava11 branch, and autorebuild is enabled.

Thanx for heads up!

J.


>  
>  Fabio
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  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
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jvanek(a)redhat.com    M: [phone]

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

[Aleksandar Kurtakov]

On Mon, Jun 29, 2020 at 2:39 PM Jiri Vanek <jvanek(a)redhat.com&gt; 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
>  jvanek(a)redhat.com    M: [phone]
>  _______________________________________________
>  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:
>  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