-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
-
False
-
-
Recent OpenJDK container images (UBI9 versions 1.15 and upwards; UBI8 version 1.16 and upwards, both released in 2023-06-06) upgraded the Maven component to 3.8, which disabled the use of (insecure) HTTP maven repositories by default. Some customers may rely on using HTTP repositories.
There is a workaround: one can specify a Maven Mirror that matches each maven repository using HTTP.
This can be achieved with the OpenJDK containers by specifying a set of environment variables, such as MAVEN_MIRRORS, and corresponding *_MAVEN_MIRROR_OF, *_MAVEN_MIRROR_URL
These variables are listed in the Reference tables in the existing document "Using OpenJDK ? source-to-image for OpenShift" (e.g. https://access.redhat.com/documentation/en-us/openjdk/11/html/using_openjdk_11_source-to-image_for_openshift/reference-s2i-openshift#s2i-openshift-config-env ) but they are quite complex and I think might need to be separately explained.
- blocks
-
OPENJDK-1954 Maven bump from 3.6.2 to 3.8.5 in S2I java builder image can lead to regression
- New