Replies: 1 comment 1 reply
-
Correct. Java 20 is basically EOL with the release of Java 21. We only ship what is supported upstream. Your solution is to use an LTS release which would be Java 17 or Java 21. If you can't do either of those, then what you're doing is the correct workaround. You can downgrade to the last buildpack which includes Java 20 support. You won't be missing any dependency updates because there will be no more upstream Java 20 updates. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello. I'm building a Java 20 Spring Boot 3.1.4 image with spring-boot-maven-plugin using paketo-buildpacks/java. It worked in the past, but today I got an error saying that no valid JRE was available.
I found out that the latest version of paketobuildpacks/bellsoft-liberica (10.3.0) drops support for JRE/JDK 20. Any reason you didn't include Java 20 support in the buildpack?
I managed to make it work downgrading the buildpack to version 10.2.9 in the pom.xml.
Is this the right approach to deal with this issue?
Unfortunately we won't be able to upgrade to Java 21 until Spring Boot supports it (maybe at the end of november).
Best regards,
Martin Medina
Beta Was this translation helpful? Give feedback.
All reactions