[Nestmates] RFR: 8197539: [Nestmates] Revert all changes to VerifyAccess.isSameMemberPackage and Lookup.in behaviour (original) (raw)
David Holmes david.holmes at oracle.com
Mon Feb 12 03:32:43 UTC 2018
- Previous message (by thread): hg: valhalla/valhalla: 8197395: [Nestmates] VerifyAccess.isMemberAccessible must not allow private access between legacy nested types
- Next message (by thread): [Nestmates] RFR: 8197539: [Nestmates] Revert all changes to VerifyAccess.isSameMemberPackage and Lookup.in behaviour
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
webrev: http://cr.openjdk.java.net/~dholmes/8197539/webrev/
webrev relative to mainline: http://cr.openjdk.java.net/~dholmes/8197539/webrev.mainline/
bug: https://bugs.openjdk.java.net/browse/JDK-8197539
After going through the issue in JDK-8197395, there is no need to change VerifyAccess.isSameMemberPackage to be aware of nestmates, as nestmates will already pass the enclosing class check. So we can restore this code to its existing mainline form.
This leaves the legacy behaviour of Lookup.in exactly as it was, and adds no special cases for nestmates.
Testing: runtime/Nestmates java/lang/invoke
Thanks, David
- Previous message (by thread): hg: valhalla/valhalla: 8197395: [Nestmates] VerifyAccess.isMemberAccessible must not allow private access between legacy nested types
- Next message (by thread): [Nestmates] RFR: 8197539: [Nestmates] Revert all changes to VerifyAccess.isSameMemberPackage and Lookup.in behaviour
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]