-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 7, 8-pool
-
Component/s: core-libs
-
b112
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8050596 | 7u80 | Alexander Zuev | P4 | Resolved | Fixed | b02 |
| JDK-8060368 | 7u76 | Alexander Zuev | P4 | Resolved | Fixed | b04 |
| JDK-8047599 | 7u72 | Alexander Zuev | P4 | Resolved | Fixed | b01 |
| JDK-8039571 | 7u71 | Alexander Zuev | P4 | Resolved | Fixed | b01 |
| JDK-8040541 | 7u66 | Alexander Zuev | P4 | Resolved | Fixed | b01 |
| JDK-8040183 | 7u65 | Alexander Zuev | P4 | Resolved | Fixed | b08 |
This is a gray area in the JSR 292 spec.
The existing OpenJDK behavior is to refuse to admit that a "method" named <init> exists. We will document this behavior as the standard.
- backported by
-
JDK-8039571 an attempt to use "<init>" as a method name should elicit NoSuchMethodException
-
- Resolved
-
-
JDK-8040183 an attempt to use "<init>" as a method name should elicit NoSuchMethodException
-
- Resolved
-
-
JDK-8040541 an attempt to use "<init>" as a method name should elicit NoSuchMethodException
-
- Resolved
-
-
JDK-8047599 an attempt to use "<init>" as a method name should elicit NoSuchMethodException
-
- Resolved
-
-
JDK-8050596 an attempt to use "<init>" as a method name should elicit NoSuchMethodException
-
- Resolved
-
-
JDK-8060368 an attempt to use "<init>" as a method name should elicit NoSuchMethodException
-
- Resolved
-
-
JDK-8040184 an attempt to use "<init>" as a method name should elicit NoSuchMethodException
-
- Closed
-