[
https://issues.apache.org/jira/browse/SOLR-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher updated SOLR-3550:
-------------------------------
Description:
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.
was:
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/extractin/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.
> 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
> Fix For: 4.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
