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
JDK-8223355: Redundant output by javadoc #2652
JDK-8223355: Redundant output by javadoc #2652
Conversation
|
@jonathan-gibbons The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
(primarily about generating files) Remove a redundant misleading "Generating" message: it only showed the base filename and if it had shown the full name, it would have been a duplicate
Just curious, does this bug affect users who specify all files individually or users who just specify a directory without detailing selection rules for classes or packages? |
Somewhat surprisingly, this happens in all the following cases:
It does not occur when specifying a package on the source path:
|
@@ -198,7 +198,6 @@ private void handleHtmlFile(DocFile srcfile, DocPath dstPath) throws DocFileIOEx | |||
PackageElement pkg = dfElement.getPackageElement(); | |||
|
|||
HtmlDocletWriter docletWriter = new DocFileWriter(configuration, dfilePath, element, pkg); | |||
configuration.messages.notice("doclet.Generating_0", docletWriter.filename.getPath()); |
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.
I guess this is to prevent duplicate output. It could probably have been solved by printing the HTML file's whole path (docletWriter.filename
just contains the base name), or including the destination path. But I'm not convinced we need to generate a message for each and every file we copy, so it's probably fine as it is.
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.
Please ignore that comment, I just saw there's already a message with the full path.
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.
FWIW, based on other recent experiences, I think there is the potential to have more versatile control of which messages to suppress. -quiet
just does everything. But this is another discussion.
@jonathan-gibbons This change now passes all automated pre-integration checks. 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 62 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.
|
/integrate |
@jonathan-gibbons Since your change was applied there have been 89 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 53b1545. |
This change addresses a bug that was observed while playing with small demo API: some files may be generated twice.
The fix is to build a single set of the files to be generated.
Note: this bug also affected the generation of the main JDK API docs. According to the log file, before the fix we were generating 14812 files; now, we are generating only 10146 files! That's a drop of 4466 files or over 30%!
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2652/head:pull/2652
$ git checkout pull/2652