Re: RFR: 8173827: Remove forRemoval=true from several deprecated security APIs

2017-02-02 Thread Stuart Marks
Hi Claes, The text of JEP 277 [1] has the following: Given the history of deprecation in Java SE, and the emphasis on long term API compatibility across versions, removal of an API is a matter of serious concern. Therefore, deprecation with the element |forRemoval=true| should be applied only

RFR: 8173827: Remove forRemoval=true from several deprecated security APIs

2017-02-02 Thread Sean Mullan
Please review this change to undo, or remove the forRemoval=true element from the Deprecated annotation of a number of security APIs. Since marking these APIs for removal in a future version of SE, it has since been reported that some external applications/code are still using these APIs, and

Re: RFR: 8145337: [JVMCI] JVMCI initialization with SecurityManager installed fails: java.security.AccessControlException: access denied

2017-02-02 Thread Alan Bateman
On 02/02/2017 02:12, Mandy Chung wrote: On Feb 1, 2017, at 3:07 AM, Doug Simon wrote: I’ve reworked the webrev as requested to make jdk.vm.compiler a non-upgradeable platform module, this allowing it to be mentioned in default.policy: