jerboaa
commented
1 year ago If you have a multi-stage build, where the first stage was using the mandrel image 22.2-java11, and you want to update, you don't only need to update the mandrel image version but also the java version. It should be written somewhere in the documentation/release notes or a blog post.
@cescoffier Is there some documentation of how this multi-stage build you are referring to is being used in practise? This is a use-case I wasn't aware of. To me it seems weird to use the mandrel JDK 11 image to compile java source code as it doesn't even have maven installed. For multi-stage builds a plain OpenJDK 11 image would be more suitable, like registry.access.redhat.com/ubi8/openjdk-11.
cescoffier
galderz
zakkak
It's not a feature request \CC @galderz
When I produced the container images for Quarkus for Mandrel 22.3.0.1, I found out that there is no Java 11 image anymore. Using the Java 17 image should be fine, but there is one case where the migration should be explained.
If you have a multi-stage build, where the first stage was using the mandrel image 22.2-java11, and you want to update, you don't only need to update the mandrel image version but also the java version. It should be written somewhere in the documentation/release notes or a blog post.