Skip to content

Commit 1f6ff6c

Browse files
committed
keep only one systemProperty tag
1 parent c4221b5 commit 1f6ff6c

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

src/java.base/share/classes/java/lang/SecurityManager.java

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -93,24 +93,24 @@
9393
* manager to be set dynamically by invoking the
9494
* {@link System#setSecurityManager(SecurityManager) setSecurityManager} method.
9595
* In the JDK implementation, the default value of the
96-
* {@systemProperty java.security.manager} system property, if not set, is
96+
* {@code java.security.manager} system property, if not set, is
9797
* the special token "{@code disallow}". If the Java virtual machine is
98-
* started with the {@systemProperty java.security.manager} system property
98+
* started with the {@code java.security.manager} system property
9999
* not set or set to "{@code disallow}" then a security manager will not be
100100
* set at startup and cannot be set dynamically (the
101101
* {@link System#setSecurityManager(SecurityManager) setSecurityManager}
102102
* method will throw an {@code UnsupportedOperationException}). If the
103-
* {@systemProperty java.security.manager} system property is set to the
103+
* {@code java.security.manager} system property is set to the
104104
* special token "{@code allow}", then a security manager will not be set at
105105
* startup but can be set dynamically. Finally, if the
106-
* {@systemProperty java.security.manager} system property is set to the
106+
* {@code java.security.manager} system property is set to the
107107
* class name of the security manager, or to the empty String ("") or the
108108
* special token "{@code default}", then a security manager is set at startup
109109
* (as described previously) and can also be subsequently replaced (or
110110
* disabled) dynamically (subject to the policy of the currently installed
111111
* security manager). The following table illustrates the behavior of the JDK
112112
* implementation for the different settings of the
113-
* {@systemProperty java.security.manager} system property:
113+
* {@code java.security.manager} system property:
114114
* <table class="striped">
115115
* <caption style="display:none">property value,
116116
* the SecurityManager set at startup,

src/java.base/share/classes/java/lang/System.java

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -341,12 +341,12 @@ private static void checkIO() {
341341
* the method simply returns.
342342
*
343343
* @implNote In the JDK implementation, the default value of the
344-
* {@systemProperty java.security.manager} system property, if not set, is
344+
* {@code java.security.manager} system property, if not set, is
345345
* the special token "{@code disallow}". If the Java virtual machine is
346-
* started with the {@systemProperty java.security.manager} system property
346+
* started with the {@code java.security.manager} system property
347347
* set to the special token "{@code allow}", then a security manager can
348348
* be set dynamically. If the Java virtual machine is started with the
349-
* system property {@systemProperty java.security.manager} not set or set
349+
* system property {@code java.security.manager} not set or set
350350
* to "{@code disallow}" then a security manager cannot be set
351351
* dynamically (the {@code setSecurityManager} method will throw an
352352
* {@code UnsupportedOperationException}).

0 commit comments

Comments
 (0)