| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8269644 | 18 | Jonathan Gibbons | P4 | Resolved | Fixed | b04 |
| JDK-8270669 | 17.0.1 | Jonathan Gibbons | P4 | Resolved | Fixed | b03 |
A DESCRIPTION OF THE PROBLEM :
https://docs.oracle.com/en/java/javase/14/docs/api/java.base/java/lang/Runtime.html#exec(java.lang.String,java.lang.String[],java.io.File)
> by the call new {@link StringTokenizer}(command) with no further
Because the `{@link ...}` appears within a `{@code ...}` tag it is displayed as literal text.
Note that the link here can simply be omitted (or should point to the respective constructor) since a few words in front of it there is already a link to StringTokenizer.
https://docs.oracle.com/en/java/javase/14/docs/api/java.base/java/lang/Runtime.html#exec(java.lang.String,java.lang.String[],java.io.File)
> by the call new {@link StringTokenizer}(command) with no further
Because the `{@link ...}` appears within a `{@code ...}` tag it is displayed as literal text.
Note that the link here can simply be omitted (or should point to the respective constructor) since a few words in front of it there is already a link to StringTokenizer.
- backported by
-
JDK-8269644 Runtime.exec(String, String[], File) documentation contains literal {@link ...}
-
- Resolved
-
-
-
- Resolved
-
