Re: [epp-dev] Moving a package to Java 11 as requirement

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

> But
for the IDE itself it should be possible to run on higher Java versions
than the product, so I personally don't have any objections if some packages
would move.

> OK

No, it is not
OK for the same arguments mentioned before. However, once we have to move
to Jetty 10.x there's most likely no way around it since it requires Java
11.

Dani



From:
       Mickael
Istria <mistria@xxxxxxxxxx>
To:
       Andrey
Loskutov <loskutov@xxxxxx>
Cc:
       Eclipse
Packaging Project <epp-dev@xxxxxxxxxxx>
Date:
       27.02.2020
23:09
Subject:
       [EXTERNAL]
Re: [epp-dev] Moving a package to Java 11 as requirement
Sent
by:        epp-dev-bounces@xxxxxxxxxxx

---

On Thu, Feb 27, 2020 at 10:56 PM Andrey
Loskutov <loskutov@xxxxxx>
wrote:

Would you share your experience so far? I'm looking for concrete examples that could improve productivity with 11.

Some things like ProcessHandle, some
methods in NIO or Collectors are the first one that come to my mind. But
I face more and more frequently the wish to use a method that Java 8 doesn't
provide and spend some time building workarounds instead.

I'm not a package maintainer, but we have some customers that insist on compatibility because they won't touch a line of code just because they fear too loose their job if something breaks.

Well for Corrosion, I think it's relatively
safe as it's already a community that seems to like "fresh" stuff.

But for the IDE itself it should be possible to run on higher Java versions than the product, so I personally don't have any objections if some packages would move.

OK

There are old package versions around for people with Java 8.

2020-03 will forever be Java 8 compatible
;)_______________________________________________
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