Re: (No longer) Compiling against Java 8

On Sat, Mar 9, 2024 at 10:53 AM Volker Lamp <[email protected]> wrote:

> Hello Tapestry developers,

Hello, Volker!

> As I see it, switching to Jakarta EE implies we need to give up
> compiling against Java 8 (whilst keep compiling against Java 11 and Java
> 17).

I've been thinking about that lately. I couldn't get Jakarta
EE-powered Tapestry's master build on Java 8 due to no Jetty or Tomcat
versions supporting both Jakarta EE and Java 8 (both require Java 11).
I had to disable the Jakarta EE-Java 8 Jenkins build job because of
that. On the other hand, Jakarta EE 9 doesn't require Java 11, just 8,
and at least one servlet container, WildFly, supports Jakarta EE and
Java 8.

> Unless anyone objects, I would go ahead and remove Java 8 from
> `tapestry-5/.github/workflows/build-pull-request.yaml`.

+1 from me. We can only enable it again if we implement a runner of a
servlet container that supports both Jakarta 11 9 and Java 8.

Cheers!

-- 
Thiago H. de Paula Figueiredo