epugh commented on PR #2501: URL: https://github.com/apache/solr/pull/2501#issuecomment-2152328714
> > As far as security manager goes, don't we need to just tackle that and solve the issue? Versus suppress it and ignore the problem? > > Removing a SecurityManager will not be a simple task as some of these settings, I believe, were put in place to fix Security issues. For now, using forbidden would clear the path to the upgradation, Lucene did the same thing. However, now that the JDK has marked it for removal, future JDK upgradation would only be possible after removing it So we should start looking into it right after upgrading to Java 21. > > And that's why I suggested marking SecurityManager, and related stuff, forbidden which is a viable solution for now. yeah.. It sort of feels like that is the opposite of "get the code ready for java 21 first" like you are doing here with Url. However I also understand that it may spiral into a bigger thing. The important thing is to keep moving forward! Thanks for this. -- 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: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
