-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: None
-
Component/s: deploy
-
b21
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8047881 | 9 | Daniil Titov | P3 | Resolved | Fixed | b22 |
| JDK-8063197 | 8u45 | Daniil Titov | P3 | Resolved | Fixed | b01 |
| JDK-8048712 | 8u40 | Daniil Titov | P3 | Resolved | Fixed | b01 |
| JDK-8049182 | 8u25 | Daniil Titov | P3 | Resolved | Fixed | b06 |
| JDK-8070599 | emb-8u47 | Daniil Titov | P3 | Resolved | Fixed | team |
| JDK-8053166 | emb-8u26 | Daniil Titov | P3 | Resolved | Fixed | b17 |
We have the text in the resources that still mentions that "This application will be blocked in a future Java...". And the logic here is driven by 3 methods in AppInfo : getFutureBlockPermission() ;getFutureBlockSelfsigned();getFutureBlockUnsigned()). We need to clean up the code and remove these method and resources, since future already come
- backported by
-
JDK-8047881 Remove AppInfo.getFutureBlock*** methods
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
(1 backported by)