-
Bug
-
Resolution: Fixed
-
P4
-
15
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8248275 | 16 | Jonathan Gibbons | P4 | Resolved | Fixed | b04 |
| JDK-8250087 | 15.0.2 | Jonathan Gibbons | P4 | Resolved | Fixed | b01 |
| JDK-8250386 | 15.0.1 | Jonathan Gibbons | P4 | Resolved | Fixed | b03 |
doclint says:
open/src/jdk.management/share/classes/com/sun/management/HotSpotDiagnosticMXBean.java:64: error: reference not found
* @throws IOException if the {@code outputFile} already exists,
^
1 error
The problem is that the method signature uses a fully-qualified name for `java.io.IOException` instead of importing it. meaning that the `@throws` cannot resolve the name. Although this could be fixed by using a fully-qualified name in `@throws` as well, a better, more conventional solution is to import that name and use the simple name in both places.
open/src/jdk.management/share/classes/com/sun/management/HotSpotDiagnosticMXBean.java:64: error: reference not found
* @throws IOException if the {@code outputFile} already exists,
^
1 error
The problem is that the method signature uses a fully-qualified name for `java.io.IOException` instead of importing it. meaning that the `@throws` cannot resolve the name. Although this could be fixed by using a fully-qualified name in `@throws` as well, a better, more conventional solution is to import that name and use the simple name in both places.
- backported by
-
JDK-8248275 bad reference in @throws in HotSpotDiagnosticMXBean
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-