RFR: 8266459: Implement JEP 411: Deprecate the Security Manager for Removal [v3]

Sean Mullan mullan at openjdk.java.net
Sun May 23 16:40:59 UTC 2021

On Fri, 21 May 2021 15:27:39 GMT, Daniel Fuchs <dfuchs at openjdk.org> wrote:

>> Weijun Wang has updated the pull request incrementally with one additional commit since the last revision:
>>   fixing awt/datatransfer/DataFlavor/DataFlavorRemoteTest.java
> src/java.base/share/classes/java/lang/SecurityManager.java line 104:
>> 102:  * method will throw an {@code UnsupportedOperationException}). If the
>> 103:  * {@systemProperty java.security.manager} system property is set to the
>> 104:  * special token "{@code allow}", then a security manager will not be set at
> Can/should the `{@systemProperty ...}` tag be used more than once for a given system property? I thought it should be used only once, at the place where the system property is defined. Maybe @jonathan-gibbons can offer some more guidance on this.

Good point. I would remove the extra @systemProperty tags on lines 103, 106, and 113. Also, in `System.setSecurityManager` there are 3 @systemProperty java.security.manager tags, I would just keep the first one. (I think it's ok to have more than one, if they are defined in different APIs).


PR: https://git.openjdk.java.net/jdk/pull/4073

More information about the security-dev mailing list