[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760124#action_12760124
]
Hoss Man commented on SOLR-1449:
--------------------------------
bq. should we reference the libs in contrib (where they are actually checked
in) rather than dist? "ant example" doesn't currently copy anything to dist...
and avoiding another copy of those libraries would be nice too.
FYI: We already copy them to ./dist/ as part of dist-contrib, and "ant example"
already depends on dist-contrib so nothing changed there.
Ultimately it's a question of how we want to solve SOLR-1433 ... this patch
assumes we keep including the full ./dist structure that we have now for all
the jars in our artifacts 9and SOLR-1433 could be solved w/o changing that by
exclusing the source locations of those libs), but if the solution to SOLR-1433
is to not copy libs to ./dist at all then it's trivial to change the <lib> refs
in the solrconfig.xml files to point at the original locations.
> solrconfig.xml syntax to add classpath elements from outside of instanceDir
> ---------------------------------------------------------------------------
>
> Key: SOLR-1449
> URL: https://issues.apache.org/jira/browse/SOLR-1449
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Fix For: 1.4
>
> Attachments: SOLR-1449.patch, SOLR-1449.patch, SOLR-1449.patch,
> SOLR-1449.patch, SOLR-1449.patch
>
>
> the idea has been discussed numerous times that it would be nice if there was
> a way to configure a core to load plugins from specific jars (or "classes"
> style directories) by path w/o needing to copy them to the "./lib" dir in
> the instanceDir.
> The current workaround is "symlinks" but that doesn't really help the
> situation of the Solr Release artifacts, where we wind up making numerous
> copies of jars to support multiple example directories (you can't have
> reliable symlinks in zip files)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
