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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on SOLR-6661:
-------------------------------------------------------

Commit 1638496 from [~ehatcher] in branch 'dev/branches/lucene_solr_4_10'
[ https://svn.apache.org/r1638496 ]

SOLR-6661: Adjust all example configurations to allow overriding error-prone relative paths for solrconfig.xml <lib> references with solr.install.dir system property; bin/solr scripts will set it appropriately. (merged from branch_5x r1634771, manually fixing solr/CHANGES.txt conflict)

> 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: Blocker
>             Fix For: 4.10.3, 5.0, Trunk
>
>         Attachments: SOLR-6661.patch
>
>
> 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