mbien commented on PR #8169: URL: https://github.com/apache/netbeans/pull/8169#issuecomment-2600985878
> Disabling the SecurityManager with an easily revertible flag for one release first seems like a good separate step. It's a bit of a "rip the band-aid" situation, but eventually OpenJDK will rip it for us. I never had anything against this idea, except the timing - the consequence is that NB 25 will be released with nb-javac 24 while having CI still testing on JDK 23. The only PR which did test on JDK 24 so far was https://github.com/apache/netbeans/pull/7928. > I saw the discussions myself but never quite managed to understand what the SecurityManager was doing that was essential. I just understood the part about protection from System.exit(), which seemed like something we could live without. And there seems to be a lot of other things which are mainly diagnostic in nature. Though it sounds like there are a lot of tests that break without it. the linked PR does list a few things and discusses them / gives alternatives where applicable -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
