janhoy commented on code in PR #2172:
URL: https://github.com/apache/solr/pull/2172#discussion_r1440772945
##########
solr/server/etc/security.policy:
##########
@@ -219,6 +219,9 @@ grant {
permission java.io.FilePermission "${solr.allowPaths}",
"read,write,delete,readlink";
permission java.io.FilePermission "${solr.allowPaths}${/}-",
"read,write,delete,readlink";
+ permission java.io.FilePermission "${solr.sharedLib}", "read,readlink";
Review Comment:
Yea, it will go away, so agree on that. One option could be to write a
SolrCLI tool to generate/update the policy file. That way, `bin/solr` could run
a tool that generates correct policy file based on whatever env/prop active and
then start the main Solr process.
--
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
