threetenbp: fix broken build #14718
Open
threetenbp: fix broken build #14718
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
xingyaner is a new contributor to projects/threetenbp. The PR must be approved by known contributors before it can be merged. The past contributors are: arthurscchan |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The fundamental reason for the fuzzing build error is that the OpenJDK version 11.0.0.1 used in the Dockerfile is too outdated. Its built-in TLS protocol and root certificate do not support the current mandatory security standards of Maven Central. This led to an SSL handshake failure when Maven was downloading dependencies.
This problem was successfully solved by upgrading the Java version in the Dockerfile to Adoptium Temurin JDK 11.0.22+7 that supports the modern TLS standard.