-
Type:
Enhancement
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 17
-
Component/s: core-libs
-
b05
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8300387 | 20.0.1 | Dukebot | P4 | Resolved | Fixed | b02 |
| JDK-8300150 | 20 | Dukebot | P4 | Resolved | Fixed | b32 |
A DESCRIPTION OF THE PROBLEM :
There are several code samples in the Java SE API documentation still using constructors of primitive wrapper classes, which are deprecated for removal. They should be replaced by valueOf factory methods or auto-boxing.
Here's what I found:
java.util.Arrays.equals(double[], double[])
java.util.Arrays.equals(double[], int, int, double[], int, int)
java.util.Arrays.equals(float[], float[])
java.util.Arrays.equals(float[], int, int, float[], int, int)
There are several code samples in the Java SE API documentation still using constructors of primitive wrapper classes, which are deprecated for removal. They should be replaced by valueOf factory methods or auto-boxing.
Here's what I found:
java.util.Arrays.equals(double[], double[])
java.util.Arrays.equals(double[], int, int, double[], int, int)
java.util.Arrays.equals(float[], float[])
java.util.Arrays.equals(float[], int, int, float[], int, int)
- backported by
-
JDK-8300150 Usage of constructors of primitive wrapper classes should be avoided in java.util API docs
-
- Resolved
-
-
JDK-8300387 Usage of constructors of primitive wrapper classes should be avoided in java.util API docs
-
- Resolved
-
- clones
-
JDK-8299502 Usage of constructors of primitive wrapper classes should be avoided in javax.xml API docs
-
- Resolved
-
- links to
-
Commit
openjdk/jdk20/628266af
-
Commit
openjdk/jdk/f36f1354
-
Review
openjdk/jdk20/105
-
Review
openjdk/jdk/11885
(2 links to)