docs: clarify architecture-specific JDK requirements - #6909
Merged
lvs0075 merged 1 commit intoAug 6, 2026
Conversation
4 tasks
Document the required JDK per CPU architecture and replace ambiguous JVM option examples. Refs tronprotocol#6895
halibobo1205
force-pushed
the
codex/docs-jdk-architecture
branch
from
August 6, 2026 06:39
47af05a to
378f89e
Compare
Sunny6889
approved these changes
Aug 6, 2026
317787106
approved these changes
Aug 6, 2026
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
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.
What does this PR do?
x86_64/amd64requires JDK 8.ARM64/aarch64requires JDK 17.Why are these changes required?
The JDK mapping is not merely a build-toolchain recommendation. It is enforced at build time in
build.gradleand again when a FullNode starts throughArch.throwIfUnsupportedJavaVersion().The existing documentation could be interpreted as allowing either JDK 8 or JDK 17 regardless of CPU architecture. This led to a reasonable but incorrect assumption that a node could run with JDK 17 on
x86_64.This PR makes the currently supported build and runtime combinations explicit and helps prevents users from copying incompatible GC options between JDK 8 and JDK 17 deployments.
This PR has been tested by:
git -c core.whitespace=cr-at-eol diff --check.Follow up
x86_64remains planned for a future release.Extra details
ARM64/aarch64support is available starting with GreatVoyage-v4.8.1.Refs #6895