-
Bug
-
Resolution: Fixed
-
P4
-
None
-
b69
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8098772 | emb-9 | Sundararajan Athijegannathan | P4 | Resolved | Fixed | team |
JDK-8129205 | 8u65 | Sundararajan Athijegannathan | P4 | Resolved | Fixed | b02 |
JDK-8085915 | 8u60 | Sundararajan Athijegannathan | P4 | Resolved | Fixed | b20 |
JDK-8138548 | emb-8u65 | Unassigned | P4 | Resolved | Fixed | b02 |
JDK-8129730 | emb-8u60 | Sundararajan Athijegannathan | P4 | Resolved | Fixed | b20 |
Objects.requireNonNull(obj) call is used as expression statement in many places and then "obj" is fetched again. Instead return value of Objects.requireNonNull could be used directly.
- backported by
-
JDK-8085915 Return value of Objects.requireNonNull call can be used
-
- Resolved
-
-
JDK-8098772 Return value of Objects.requireNonNull call can be used
-
- Resolved
-
-
JDK-8129205 Return value of Objects.requireNonNull call can be used
-
- Resolved
-
-
JDK-8129730 Return value of Objects.requireNonNull call can be used
-
- Resolved
-
-
JDK-8138548 Return value of Objects.requireNonNull call can be used
-
- Resolved
-