[gentoo-dev] Java7 stabilization

[gentoo-dev] Java7 stabilization

[Pacho Ramos]

Hello

I would like to see if we could finally try to stabilize java7 on Gentoo
as some external tools start to require it. 

There is currently this tracker opened:
https://bugs.gentoo.org/show_bug.cgi?id=384609

I am unsure why:
https://bugs.gentoo.org/show_bug.cgi?id=483018

should block the stabilization as we can have multiple java versions
installed due slots

The tracker list two broken packages that would need either patching or
to be forced to use older slots and this one:
https://bugs.gentoo.org/show_bug.cgi?id=515830

That looks more important. Then, I also wonder about what
implementations are we meant to look for this stabilization. Should we
look for bugs affecting icedtea-bin and also oracle's implementation? (I
was wondering if the tracker was really collecting all the issues :/)

Thanks

Re: [gentoo-dev] Java7 stabilization

[Tom Wijsman]

On Mon, 10 Nov 2014 12:23:43 +0100
Pacho Ramos <pacho@gentoo.org> wrote:

> Hello

Hello, this is an individual response.
 
> I would like to see if we could finally try to stabilize java7 on
> Gentoo as some external tools start to require it. 
> 
> There is currently this tracker opened:
> https://bugs.gentoo.org/show_bug.cgi?id=384609
> 
> I am unsure why:
> https://bugs.gentoo.org/show_bug.cgi?id=483018
> 
> should block the stabilization as we can have multiple java versions
> installed due slots

Multiple stable Java versions means more work; so, you'll instead want
to bring incompatible packages forward to Java 7 or mask and lastrite
them as time goes by.

> The tracker list two broken packages that would need either patching
> or to be forced to use older slots and this one:

Under the work train of thoughts, an older slot is a temporary measure.

> https://bugs.gentoo.org/show_bug.cgi?id=515830
>
> That looks more important. Then, I also wonder about what
> implementations are we meant to look for this stabilization. Should we
> look for bugs affecting icedtea-bin and also oracle's implementation?

If you look at the history, multiple implementations are stabilized;
this means that bugs should indeed look at whether they affect both
versions. In general, fixing a bug for one implementation fixes it for
the other implementation or the other implement didn't even have the
bug to begin with; but that shouldn't fool us to check them both out.

> (I was wondering if the tracker was really collecting all the
> issues :/)

Doubtful. A tree wide check is necessary to confirm that all Java based
packages build with the to be stabilized Java 7 implementations.