You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erik Hatcher (JIRA)" <ji...@apache.org> on 2015/06/08 01:24:00 UTC

[jira] [Resolved] (SOLR-3550) Improve library loading with base path

     [ https://issues.apache.org/jira/browse/SOLR-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erik Hatcher resolved SOLR-3550.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 5.0
         Assignee: Erik Hatcher

This was done for Solr 5.0 as solr.install.dir

> Improve library loading with base path
> --------------------------------------
>
>                 Key: SOLR-3550
>                 URL: https://issues.apache.org/jira/browse/SOLR-3550
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Erik Hatcher
>            Assignee: Erik Hatcher
>             Fix For: 5.0
>
>
> The issue occurs when users copy Solr's example "solr home" directory somewhere else, not relative to Solr's installation and paths break.  Paths like these:
> {code}
> <lib dir="../../dist/" regex="apache-solr-cell-\d.*\.jar" />
> <lib dir="../../contrib/extraction/lib" regex=".*\.jar" />
> {code}
> I've addressed this in my own projects by introducing a new system property construct like dir="${solr.install.dir}/contrib/extraction/lib".  But this requires a change to solrconfig.xml for every <lib> element.  There's got to be a better way such that Solr can be installed in one place, and <lib> directives can readily access the Solr "installation" directory path.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org