On 07/27/2016 12:45 PM, Coleen Phillimore wrote:
This looks great. Thank you!
Should we have another bug to actually remove the code and hotspot code
for jdk10
Yes we should. We need to also do that for all of the other APIs that we
have added forRemoval=true to for 9, so I was thinking abou
This looks great. Thank you!
Should we have another bug to actually remove the code and hotspot code
for jdk10 and make it blocked by
https://bugs.openjdk.java.net/browse/JDK-8162416?
thanks,
Coleen
On 7/27/16 9:53 AM, Xuelei Fan wrote:
Looks fine to me.
Xuelei
On 7/27/2016 9:02 PM, Sean
Looks fine to me.
Xuelei
On 7/27/2016 9:02 PM, Sean Mullan wrote:
> Please review this change to mark the pre-1.2 deprecated SecurityManager
> methods (and 1 field) with forRemoval=true. These methods are no longer
> necessary and are known to be error-prone and have been deprecated since
> JDK 1
Please review this change to mark the pre-1.2 deprecated SecurityManager
methods (and 1 field) with forRemoval=true. These methods are no longer
necessary and are known to be error-prone and have been deprecated since
JDK 1.2. The intention is to remove them in a subsequent release of Java SE.
