Ah, I just upgraded us to 3.6, and abandoned xi:include in favor of symlinks, so I didn't know whether it was fixed or not.
Another thing I just thought of is if you want your config files to be available from the web UI, the xi:include directives won't be resolved, so you'll just see the literal file. Unless this has changed as well. Michael Della Bitta ------------------------------------------------ Appinions | 18 East 41st St., Suite 1806 | New York, NY 10017 www.appinions.com Where Influence Isn’t a Game On Thu, Sep 20, 2012 at 1:27 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > : "xi:include" directives work in Solr config files, but in most (all?) > : versions of Solr, they require absolute paths, which makes portable > : configuration slightly more sticky. Still, a very viable solution. > > Huh? > > There were bugs in xinclude parsing up to Solr 1.4 that caused relative > paths to be resolved in a very wonky way (relative the CWD), so that > absolute paths were recomended for the sake of clarity/sanity, but these > bugs have been fixed since Solr 3.1... > > https://issues.apache.org/jira/browse/SOLR-1656 > > > > -Hoss
