Drop Java 11 about quarkus-super-heroes HOT 10 CLOSED

+1 - most of my demos are using java 17 or 20 (and one using my own build of 21)

from quarkus-super-heroes.

Yes, please!
I see no value in showcasing Java 11.

from quarkus-super-heroes.

Makes sense. I think there's value in Quarkus itself supporting Java 11, but that support doesn't need to extend to demos.

from quarkus-super-heroes.

I'm going to take on this issue and drop java 11 from the project. I'll leave the automation in place to support building multiple java versions in case in the future we want to build java 17 & java 21 for example.

from quarkus-super-heroes.

You know Java 21 is coming, and you know Java 17 won't be going away ... The window when we build just one Java version may be a small one. :)

from quarkus-super-heroes.

I thought about introducing Java 20 right now (& then upgrading to 21 once its out), but the problem is there are no openjdk-20 images on registry.access.redhat.com, so I think I'll just wait until 21 is out and there is an "official" image for it.

from quarkus-super-heroes.

from quarkus-super-heroes.

Can’t we try the EA version of 21?

But there isn't an image available on registry.access.redhat.com. We'd have to have a completely different Dockerfile for 21, plus we'd have to make sure the GitHub action workflows properly knew how to pull down EA versions.

And then what about native? We'd be using 21 for jvm but 17 for native?

I think I'd rather just keep everything at 17 until 21 is "official"?

from quarkus-super-heroes.

from quarkus-super-heroes.

So using 20 might be a good idea until 21 gets released.

That has the same problem. There is no image on registry.access.redhat.com for openjdk-20.

from quarkus-super-heroes.