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 2014/10/27 15:26:33 UTC

[jira] [Comment Edited] (SOLR-6661) Address relative path references

    [ https://issues.apache.org/jira/browse/SOLR-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185173#comment-14185173 ] 

Erik Hatcher edited comment on SOLR-6661 at 10/27/14 2:25 PM:
--------------------------------------------------------------

This has historically been a problem, and I've always adjusted the example configurations when I build prototypes/demos to have this $\{solr.install.dir} system property concept.  Now that we have start scripts, we can simply pass in the already known Solr "install" (under which contrib/ lives, most importantly for this issue) directory. 


was (Author: ehatcher):
This has historically been a problem, and I've always adjusted the example configurations when I build prototypes/demos to have this ${solr.install.dir} system property concept.  Now that we have start scripts, we can simply pass in the already known Solr "install" (under which contrib/ lives, most importantly for this issue) directory. 

> Address relative path <lib> references
> --------------------------------------
>
>                 Key: SOLR-6661
>                 URL: https://issues.apache.org/jira/browse/SOLR-6661
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.10
>            Reporter: Erik Hatcher
>            Assignee: Erik Hatcher
>            Priority: Critical
>             Fix For: 5.0
>
>
> Relative paths in solrconfig.xml's <lib> references are wrong, and require manual adjusting, when the base directory moves to different place in the file system tree.  This can happen when cloning a configuration, such as the new start scripts in "-e cloud" mode.
> Having an incorrect relative path manifests itself as /browse not working (can't find VelocityResponseWriter related JARs), and likewise with /update/extract because of wrong paths to Tika, etc.



--
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