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 <decatho...@gmail.com> wrote:

> On Tue, Jun 30, 2020 at 9:52 AM Jiri Vanek <jva...@redhat.com> wrote:
> >
> > On 6/29/20 1:59 PM, Aleksandar Kurtakov wrote:
> > >
> > >
> > > On Mon, Jun 29, 2020 at 2:39 PM Jiri Vanek <jva...@redhat.com <mailto:
> jva...@redhat.com>> 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/monitor/
> 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@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
>


-- 
Alexander Kurtakov
Red Hat Eclipse Team
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org

Reply via email to