-
Notifications
You must be signed in to change notification settings - Fork 61
JDK25 images for UBI9 #618
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: ubi9
Are you sure you want to change the base?
Conversation
Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
Not for production use. Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
JDK25 as provided by EPEL Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
Builder test was running for runtime images. Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
|
The failing tests for JDK25 (as of 94a17b9) are The tests detect JDK21 -- this is pulled in by |
|
(note to self): I'm working on the non-EPEL version, and I've set up the JDK25 module in a similar way to the ubi10 approach: JDK25 depending upon JRE25 leaning on it to provide the common configuration, including the jvm-options file. I have not backported the same change for the other JDK versions. However this breaks because |
Top-level epic: https://issues.redhat.com/browse/OPENJDK-4185
These are WIP/dev images, using EPEL to get access to JDK25.