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

[Claes Redestad]

-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 ready for it then I dont see why we shouldnt simply defer the actual removal to some later release rather than drop the intent to remove like this.

/Claes 



Sean Mullan <sean.mullan at oracle.com> skrev: (2 februari 2017 19:35:03 CET)
>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 there is concern that there may not be enough advance notice 
>to adapt their code to transition away from these legacy APIs and/or 
>replace them with newer APIs before they would be removed.
>
>bug: https://bugs.openjdk.java.net/browse/JDK-8173827
>webrev: http://cr.openjdk.java.net/~mullan/webrevs/8173827/webrev.00/
>
>Thanks,
>Sean

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/security-dev/attachments/20170202/d6d0711d/attachment.htm>