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
-1
AFAIU, forRemoval=true is not saying anything about *when* each deprecated
method/class will be removed (although there might be an expectation that it
should be in the next major release if possible, i.e., 10); if there's concern
like here that some known application or library won't be re
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 t
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:
http://cr.openjdk.java.net/~dnsimon/8145337/
Looks good
