[
https://issues.apache.org/jira/browse/SOLR-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536025#comment-17536025
]
ASF subversion and git services commented on SOLR-15921:
--------------------------------------------------------
Commit 9a2a737873b9cde62a709c18971d110c877688eb in solr's branch
refs/heads/branch_9x from Jan Høydahl
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=9a2a737873b ]
SOLR-15921 Look for jars in SOLR_TIP/lib/ (#525)
(cherry picked from commit 16657ccab0929ab6440b4b1b09a4b4983616c7d9)
> Look for jars in SOLR_TIP/lib/
> ------------------------------
>
> Key: SOLR-15921
> URL: https://issues.apache.org/jira/browse/SOLR-15921
> Project: Solr
> Issue Type: Improvement
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> From dev list thread:
> {quote}
> Another minor improvement for users is if we pre-add $SOLR_TIP/lib to the
> classloader, similar to what we have with $SOLR_HOME/lib today. The
> disadvantage of $SOLR_HOME/lib is that it can be anywhere, perhaps on a
> Docker volume or a different disk, so you cannot e.g make a Dockerfile like
> FROM solr:9.0
> ADD foo.jar /var/solr/data/lib/foo.jar
> ...since /var/solr/data is a volume and will resolve to the volume partition
> of the user, not the content from the image. So if we instead allow users to
> do
> FROM solr:9.0
> ADD foo.jar /opt/solr/lib/
> That is both logical and beautiful, and would always work.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
