-
Enhancement
-
Resolution: Fixed
-
P3
-
9
-
b20
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8206824 | 12 | Roger Riggs | P3 | Resolved | Fixed | team |
JDK-8206601 | 11.0.1 | Roger Riggs | P3 | Resolved | Fixed | b01 |
It leads me to question on whether we should change this behaviour. There are a whole bunch of properties that make no sense to change.
Those like : java.version, java.vendor, java.home, java.vm.specification.version, java.vm.specification.vendor, java.vm.specification.name, java.vm.version, java.vm.vendor, java.vm.name, java.specification.version, java.specification.vendor,java.specification.name.
Should we consider making them read only for JDK 9 and later ?
- backported by
-
JDK-8206601 Make some JDK system properties read only
-
- Resolved
-
-
JDK-8206824 Make some JDK system properties read only
-
- Resolved
-
- csr for
-
JDK-8204235 Make some standard system properties effectively read only
-
- Closed
-
- is blocked by
-
CODETOOLS-7902139 jtreg should not set system property java.class.path
-
- Open
-
-
JDK-8201279 javax.sound tests should not set java.home system property
-
- Resolved
-
- relates to
-
JDK-4165411 java.lang.System: Forbid the modification of read-only system properties
-
- Open
-
-
JDK-8233020 (fs) UnixFileSystemProvider should use StaticProperty.userDir().
-
- Resolved
-
-
JDK-8185496 Improve performance of system properties initialization in initPhase1
-
- Resolved
-
-
JDK-8176456 Clearing system property user.dir causes File methods to throw NPE
-
- Closed
-