-
Notifications
You must be signed in to change notification settings - Fork 588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System::setSecurityManager is deprecated and will be removed in a future JDK release #1579
Comments
See also #1515 (not a duplicate). |
People start shifting to Java 17 (latest LTS), me and my project included. So, any ETA on this? Thanks! |
I can confirm that Java 17 is pretty angry about that:
|
Is there an update on this issue? I'm slowly shifting projects to Java 17 and notice the warning nagging me to report the issue. |
This is pretty frustrating now that we're moving over to Java 17. Our builds output 12 lines of "WARNING:..." due to this. |
so we welcome your contribution :) |
The Security Manager is deprecated and subject to removal in a future release. There is no replacement for the Security Manager. See also spotbugs#1579
My proposal is to stop using the ValidationSecurityManager, see #1983. Looks like it is only there to help with troubleshooting certain issues. WDYT? 🙂 |
The Security Manager is deprecated and subject to removal in a future release. There is no replacement for the Security Manager. See also spotbugs#1579
The Security Manager is deprecated and subject to removal in a future release. There is no replacement for the Security Manager. See also spotbugs#1579
At the very least would do well to have an option available to exclude.xml to disable the security manager. |
Now with Java 18, this is an error, not a warning:
|
The Security Manager is deprecated and subject to removal in a future release. There is no replacement for the Security Manager. See also #1579 Co-authored-by: Kengo TODA <skypencil@gmail.com>
… deprecated for removal. This fixes spotbugs#1579.
… deprecated for removal. This fixes spotbugs#1579. If needed, disabling the security manager can still be requested on Java 17 and newer by setting the 'edu.umd.cs.findbugs.securityManagerDisabled' property to 'false'. Using this property also allows to disable this functionality on older VMs.
… deprecated for removal. This fixes spotbugs#1579. If needed, disabling the security manager can still be requested on Java 17 and newer by setting the 'edu.umd.cs.findbugs.securityManagerDisabled' property to 'false'. Using this property also allows to disable this functionality on older VMs.
… deprecated for removal. This fixes spotbugs#1579. If needed, disabling the security manager can still be requested on Java 17 and newer by setting the 'edu.umd.cs.findbugs.securityManagerDisabled' property to 'false'. Using this property also allows to disable this functionality on older VMs.
… deprecated for removal. This fixes spotbugs#1579. If needed, disabling the security manager can still be requested on Java 17 and newer by setting the 'edu.umd.cs.findbugs.securityManagerDisabled' property to 'false'. Using this property also allows to disable this functionality on older VMs.
… deprecated for removal. (#2123) * Do not disable the security manager on Java 17 VMs and newer as it is deprecated for removal. This fixes #1579. If needed, disabling the security manager can still be requested on Java 17 and newer by setting the 'edu.umd.cs.findbugs.securityManagerDisabled' property to 'false'. Using this property also allows to disable this functionality on older VMs. * make the field private and final Co-authored-by: Kengo TODA <skypencil@gmail.com> Co-authored-by: Kengo TODA <skypencil+github@gmail.com>
This is marked as completed, and unless I'm mistaken, it's in the latest
|
That |
@io7m looks to be spotbugs/spotbugs-maven-plugin#423 |
Ah, thanks. Didn't realize the Maven plugin was tracked in a different repos. 👍 |
We have several usage of
System::setSecurityManager
in SpotBugs implementation.https://github.com/spotbugs/spotbugs/search?q=setSecurityManager&type=
The text was updated successfully, but these errors were encountered: