: Instead, maybe a relative path should be made relative to Solr's home
: directory instead of to the current working directory?
I'm not sure how i feel about that ... it would be one thing if Solr could
generate an error if the dataDir didn't exist, but since we create the
directory on the fly as needed, changing this behavior <dataDir> is
relative working directory vs solr.home) could really confuse people.
Does the system property substitution stuff in the solrconfig deal with
substitutions that contain other substitutions? if so then maybe we
should set the solr.solr.home system property if we see that solr home has
been specified with JNDI, and make the example solrconfig something
like...
<dataDir>${solr.data.dir:${solr.solr.home}/solr/data}</dataDir>
...but people can still choose to use something like...
<dataDir>data</dataDir>
...and have it mean "the data directory in my current working directory"
Of course, i may just be paranoid about breaking esoteric use cases.
-Hoss
