-
Notifications
You must be signed in to change notification settings - Fork 555
8271086: Block comments of form '/***' are treated as javadoc comments #585
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
8271086: Block comments of form '/***' are treated as javadoc comments #585
Conversation
|
👋 Welcome back kcr! A progress list of the required criteria for merging this PR into |
arapte
left a comment
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.
Looks good to me, verified javadoc build and doc. This is correcting plenty wrong docs.
|
@kevinrushforth 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 3 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
|
/integrate |
|
Going to push as commit 78a3721.
Your commit was automatically rebased without conflicts. |
|
@kevinrushforth Pushed as commit 78a3721. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This fix for JDK-8271086 is part of a larger cleanup effort to find and fix places where we have missing or redundant API comments. See JDK-8271083.
This fixes a long-standing problem dating back to (at least) JavaFX 2 where block comments of the following form are sometimes treated as javadoc comments:
There are several places where a block comment like this unintentionally shows up in our API documentation. For example, see the generated docs for Node::getNodeOrientation where the literal string
* Component Orientation Properties * *is presented in the docs.The best solution is to simply eliminate this style of block comment as an anti-pattern everywhere it occurs in our Java code.
There are a total of 982 such occurrences (in 185 different files). All but 7 of these follow the pattern shown above, where the trimmed first line of the block is a single
/followed by 4 or more*characters, and contains no other characters. Like this:The remaining 7 are comments with some variation, either being an inline comment (starting with
//) or having text in the middle, or in one case is intended to be a javadoc comment, but with an extra*--/***rather than/**. I fixed those 7 manually and then ran a script to fix the remaining 975 comments, by replacing the 2nd*with a space (thus preserving the line length).So:
becomes
Notes to Reviewers
gradle javadocand also visually inspected the docs (spot checked), and confirmed that it fixes the problem.jfx17.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jfx pull/585/head:pull/585$ git checkout pull/585Update a local copy of the PR:
$ git checkout pull/585$ git pull https://git.openjdk.java.net/jfx pull/585/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 585View PR using the GUI difftool:
$ git pr show -t 585Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jfx/pull/585.diff