summaryrefslogtreecommitdiff
path: root/manual
diff options
context:
space:
mode:
authorJaikiran Pai <jaikiran@apache.org>2021-06-17 08:51:21 +0530
committerJaikiran Pai <jaikiran@apache.org>2021-06-17 08:51:21 +0530
commitf61ac12960af852b8237fe91f256dea27d898dca (patch)
tree58b6dd654e7a496101ecf02d021d5c19c5db7cf7 /manual
parent96fa99ee6c8ad9b646ed872519da79971add98e4 (diff)
downloadant-f61ac12960af852b8237fe91f256dea27d898dca.tar.gz
Remove practically no-op code which was calling System.setSecurityManager()
Starting Java 17, System.setSecurityManager() usage is deprecated (for removal) as noted in https://openjdk.java.net/jeps/411. The code here was just calling getSecurityManager() and then in a finally block setting it back using setSecurityManager(). However, we aren't setting any other security manager in between these calls. Looking at the code history, it appears that at one point back in 2001, we were indeed setting a custom security manager (commit 41893fdb3052f79a2d09d7f8a86711912fc429e6) but that was then reverted in commit ff4e823ee29f5a6a0e1658ff8ff43f1076f7a559. So this current piece of code is practically doing nothing.
Diffstat (limited to 'manual')
0 files changed, 0 insertions, 0 deletions