<AWT Dev> [12] Review Request: 8210692 The "com.sun.awt.SecurityWarning" class can be dropped

[Philip Race]

It was exported  in the past .. and it was publicly documented ..

http://www.oracle.com/technetwork/articles/javase/appletwarning-135102.html

.. so I think Sergey was correct in his "JDK" scope.
Implementation would be for something entirely internal.

+1

-phil.

On 9/13/18, 7:20 PM, mandy chung wrote:
>
> On 9/13/18 2:43 PM, Sergey Bylokhov wrote:
>> Hello.
>> Please review fix for jdk12.
>>
>> Bug: https://bugs.openjdk.java.net/browse/JDK-8210692
>> Webrev: http://cr.openjdk.java.net/~serb/8210692/webrev.00
>> CSR: https://bugs.openjdk.java.net/browse/JDK-8210693
>>
>
> Thus change looks okay to me.  This class is not exported
> and so I have updated the CSR of "Implementation" scope rather
> than JDK.
>
> Mandy
>
>> The client code has a "com.sun.awt.SecurityWarning" class which at 
>> some point in the past, JDK 6u10, was used as a kind of "public" API.
>>
>> During development of jdk9 it was considered that this API is not 
>> supported and may be removed in the future: JDK-8051640.
>> In jdk11 this class was marked as "forRemoval = true" (see 
>> JDK-8205588) and can be dropped in 12.
>>
>> In the fix these things were removed:
>>  - com/sun/awt/SecurityWarning.java
>>  - The test for SecurityWarning class
>>  - Test groups, because SecurityWarning is the latest class in 
>> "com/sun/awt" package
>>  - The reference to "com/sun/awt" in the "default.policy"
>>
>> (cc) core-libs-dev:
>> I am not sure who is responsible to review the change in 
>> "default.policy".
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/security-dev/attachments/20180915/eaae46de/attachment.htm>