-
Bug
-
Resolution: Fixed
-
P4
-
18
-
b29
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8289405 | 20 | Jonathan Gibbons | P4 | Resolved | Fixed | b04 |
| JDK-8291170 | 19.0.2 | Jonathan Gibbons | P4 | Resolved | Fixed | b01 |
| JDK-8291075 | 19.0.1 | Jonathan Gibbons | P4 | Resolved | Fixed | b04 |
The specification does not seem to allow omission of # (hash sign) when referring to a method or a field of this class, interface, enum or record. Javadoc seems to be more forgiving and allows to do that.
On the one hand, this might be a sensible thing for javadoc to do. On the other hand, it results in situation when something that works in javadoc is invalid in third party tools, such as IDEs.
(The robustness principle is a design guideline for software that states: "be conservative in what you do, be liberal in what you accept from others". This principle has been criticized.)
On the one hand, this might be a sensible thing for javadoc to do. On the other hand, it results in situation when something that works in javadoc is invalid in third party tools, such as IDEs.
(The robustness principle is a design guideline for software that states: "be conservative in what you do, be liberal in what you accept from others". This principle has been criticized.)
- backported by
-
JDK-8289405 Reconcile specification and implementation of link parsing
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Closed
-
-
-
- Closed
-