[ https://issues.apache.org/jira/browse/SOLR-8384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623355#comment-15623355 ]
Jan Høydahl commented on SOLR-8384: ----------------------------------- I can agree with you. Looks like the {{-d}} option is designed to work even if the solr/server dir is missing completely, which is not the case for neither bin/solr or bin/solr.cmd currently. bin/solr uses DEFAULT_SERVER_DIR for the run_tool stuff. > Windows Start Script when Changing SOLR_SERVER_DIR via -d option > ---------------------------------------------------------------- > > Key: SOLR-8384 > URL: https://issues.apache.org/jira/browse/SOLR-8384 > Project: Solr > Issue Type: Bug > Components: scripts and tools > Affects Versions: 5.3.1 > Environment: Windows > Reporter: Jeremy Anderson > Priority: Trivial > > bin\solr.cmd Requires change of environment variables used in the " REM now > wait to see Solr come online ..." command. Currently this call uses > DEFAULT_SERVER_DIR which is no longer correct when starting SOLR with a > different server directory using the -d command option. > Replace DEFAULT_SERVER_DIR with SOLR_SERVER_DIR so that the proper libraries > are able to be found when checking that SOLR started. > There may be other uses in the script where this issue is present when > starting SOLR from a different directory other than 'server'. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org