Updates build documentation to not mention explicit Java version #16674
Conversation
This file contains 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
…t was out of sync with the dedicated Java page. This means there is one less place to keep information in sync.
cryptoe
approved these changes
Jul 3, 2024
|
Thanks for the contribution. |
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.
Description
Updates build documentation to not mention explicit Java version as it was out of sync with the dedicated Java page.
This means there is one less place to keep information in sync.
I removed almost all of the PR template things as this is a trivial docs-only patch.
I assume that the list of supported runtime Java versions is the same that is also supported for building and it was an oversight that JDK 17 was not added here.
If it is indeed the case that JDK 17 cannot be built but only used to run then this PR is invalid.