docs: correct Java API seed generator dispatch logic - #80
Merged
WilliamAGH merged 1 commit intoJul 17, 2026
Merged
Conversation
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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 pipeline-commands.md incorrectly stated that 'Oracle Javadoc uses a
deterministic Python seed generator'. The actual dispatch logic changed
from URL-host matching to identity-based matching: any manifest-governed
source with a non-empty javaRelease field uses the seed generator, not
just Oracle URLs.
A developer reading the old docs might add a non-Oracle Java API source
and wrongly assume it would use the generic mirror strategy instead of
the seed generator.
Introduced by commit e08ed9d (@WilliamAGH, #77)
Doc Drift PRs can be configured here.