Hmmm, I see what you mean. If you'd be kind enough to submit a patch
that'd be great, attach it to a JIRA and ping people to get it
applied.
Glancing quickly it looks like there are a number of things in
solr.in.sh that are not in solr.in.cmd, certainly a _lot_ of the Solr
devs are *nix sorts so t
SOLR 7.4.0
In the linux solr script, LOG4J_PROPS is expected to be the path to a custom
log4j2.xml file. LOG4J_CONFIG ends up being a collection of all
-Dlog4j.configurationFile=BLAH parameter strings.
In the windows solr.cmd script, LOG4J_PROPS is not respected at all. And
LOG4J_CONFIG is expe
