threetenbp: fix broken build#15895
Open
xingyaner wants to merge 1 commit into
Open
Conversation
|
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 |
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
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 original OSS-Fuzz integration downloads the OpenJDK 11.0.0.1 reference implementation from download.java.net and uses it as the Java runtime for Maven and the generated fuzzing launchers. Under the current OSS-Fuzz environment, the build fails during Maven dependency resolution with Received fatal alert: handshake_failure while downloading artifacts from Maven Central, preventing the project from being built. This patch replaces the outdated JDK with the current Temurin 11 distribution, updates the Java trust store to use the system CA certificates, and normalizes the extracted JDK directory to a stable $SRC/jdk11 path. Using a stable directory removes version-specific path assumptions while ensuring that the same JDK is consistently used by Maven, the copied runtime, and the generated launcher scripts.