Repository navigation
Use canonical Javadoc toolchain for release catalogs - #50
Merged
Merged
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
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 release catalog check fails after building with Java 17 because its Javadoc parser preserves extra spaces in comment text. The committed catalogs, browser, Studio, and validation job use Java 25's normalized Javadoc output.
Use Java 25 for the release job too, and retain read-only compatibility/catalog checks. The Maven compiler still targets Java 17 through
maven.compiler.release=17.Validation: reproduced the stale API catalog after a Java 17 build. Rebuilt with Java 25 and confirmed compatibility and catalog freshness, plus class-file major version 61 (Java 17).