janhoy commented on code in PR #3153: URL: https://github.com/apache/solr/pull/3153#discussion_r2332736034
########## solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-9.adoc: ########## @@ -74,6 +74,9 @@ Due to changes in Lucene 9, that isn't possible any more. SolrJ users not using SolrClients that use Apache HttpClient can safely exclude those dependencies. SolrJ users not using SolrClients that use Jetty HttpClient can safely exclude those dependencies. +=== Java Security Manager +Java removed support for the Security Manager starting with Java 24, therefore Solr will disable the feature when run with Java 24 or later. + Review Comment: On one hand, we could expect users upgrading to Java 25 to be aware of the JSM removal and what that means for the use of any java application. However, it is also quite likely that many will blindly upgrade to latest LTS java wherever they can without giving it much more thought. Perhaps we should err on stating clearly what this may mean. Perhaps not as thoroughly as the suggestion above, but I like the distinction between container and bare-metal. Users running Solr on bare-metal, perhaps side by side by other applications, have a real benefit of JSM today. But you could argue that when running in container, it's much harder to do much harm. -- 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]
