[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epp-dev] Moving a package to Java 11 as requirement
|
Hi Mickael,
Frankly, as Ed pointed out, EPP doesn't really have a choice. If one of the projects drops its support for older versions of Java we can either live with it and update our minimum Java as well or drop/disallow the project from EPP.
I'm in favor of required Java 11 for all packages for 2020-06. I find 2020-03 a bit too short notice but one whole release cycle is sufficient IMO.
One thing we tried to maintain in the past is consistency, i.e. either raise the minimum required Java version for *all* package or *none*. I'm in favor of keeping that - although once we start shipping JREs with a package I would reduce my priority on this.
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/
> On Feb 27, 2020, at 21:00, Mickael Istria <mistria@xxxxxxxxxx> wrote:
>
> Hi all,
>
> Today I've faced a couple of issues where Java 8 is noticeable less productive that Java 11 and some of its sugar. I'm willing to start adopting Java 11 in some projects to write better code faster.
> The first "safe" example that comes to my mind is Corrosion.
> Let's imagine that a future (post-2020-03) release of Corrosion wants to switch to Java 11 as BREE, would it be fine for EPP to have the Rust package requiring Java 11 while others require Java 8? If not, what would be the possible alternatives that wouldn't block Corrosion from adopting Java 11?
>
> Also, I'm curious, are there any other package maintainers out there who are eager to move to a newer Java as BREE?
>
> Cheers,
> --
> Mickael Istria
> Eclipse IDE developer, for Red Hat Developers
> _______________________________________________
> epp-dev mailing list
> epp-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/epp-dev
