-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8297984: Turn on warnings as errors for javadoc #11468
Conversation
👋 Welcome back ihse! A progress list of the required criteria for merging this PR into |
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@magicus This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 20 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
If you would like to exercise the full-docs build in GHA, you could make that build depend on the linux-x64 build and set |
Good point. I don't think it's worth it, though. Since the output is not saved but thrown away, we will just be wasting CPU cycles. The full docs graph generation is unlikely to start failing as a result of general changes in the code, only if some of the code that generates the graphs were to be changed, and such PRs can test this separately. |
Since we do not do "apt install graphviz", configure will automatically determine that full docs is impossible. My intent were to keep it that way, since if for some reason "dot" were to be installed on the GHA image, then suddenly the build time would jump from 3 minutes to 60, so I wanted to make it clear that we never want this to happen. However, I realize my comment might be misunderstood as if full docs is impossible to do without the cost of rebuilding everything. I'll see if I can clarify it without turning it into an essay about the reasoning. |
/integrate |
Going to push as commit df07255.
Your commit was automatically rebased without conflicts. |
For some reason, we never turned on
-Werror
for javadoc. It is high time to do so.This PR also fixes a recent issue with the javadoc in JFR that caused a warning, and enables building of javadoc on GHA. (It takes about 3 minutes, as a separate build job.)
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11468/head:pull/11468
$ git checkout pull/11468
Update a local copy of the PR:
$ git checkout pull/11468
$ git pull https://git.openjdk.org/jdk pull/11468/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11468
View PR using the GUI difftool:
$ git pr show -t 11468
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11468.diff