#1107 - Javadoc warning cleanup & Fix for JDK 11 Javadoc NPE - #1118
Conversation
|
Did you check the NPE against bugs.java.com? |
|
I think this PR is okay to integrate, but I'd like to leave it open for a week in case someone else will review it. While the purpose of this PR is to cleanup javadoc diagnostic messages, it should be noted that (unlike previous javadoc PRs) this one changes more than just comments; it deprecates classes and methods that weren't actually deprecated before. |
Actually I did do some poking around a few weeks ago when I saw this, and I found something that looked like a match. Apparently it's fixed in JDK 12, that's how I was able to pinpoint the source of the crash/warnings. Probably this is what I found: https://bugs.openjdk.java.net/browse/JDK-8181854 Yeah, the deprecated annotations were added based on the @ deprecated in the comments (which were of course the source of the warnings here), so I agree it's a good idea to take a closer look to make sure the comments were correct. If not the fix will just be inverted to avoid the warnings, no big deal. |
|
On 2nd thought, perhaps we should avoid deprecating methods in dot-dot releases. |
Fixes 100+ Javadoc warnings in JDK 11 and this Javadoc NPE: