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

Houston Putman commented on SOLR-15914:
---------------------------------------

I am also perfectly fine moving the libs into 
{{{}contrib/mycontrib/lib/mycontrib-X.Y.Z.jar{}}}, it would make it easier to 
just add one path to the classpath instead of knowing that you need two 
locations.

I whole-heartedly support this ticket. I would even say that Solr should 
understand these arguments, even if the <sharedLib></sharedLib> entry is not in 
the {{{}solr.xml{}}}, but we can always handle that in a future issue (making 
the ENV_VAR, sysprop, solr.xml config options line up better). I think it would 
be great to get it into 9.0 if it wouldn't take much effort. (And if we move 
the location of the module jars, then we will definitely want to make this 
change in a major version release).

As a side-note, I remember [~dsmiley] mentioning that we should rename 
{{contrib}} to {{{}modules{}}}, and I don't see a time better than the present 
(major release and all...) to do that. As we make these add-ons more numerous 
and popular, having better messaging around them is critical. If I'm a user, 
then "modules" makes a lot more sense than "contrib".

> bin/solr argument to add contribs to classpath
> ----------------------------------------------
>
>                 Key: SOLR-15914
>                 URL: https://issues.apache.org/jira/browse/SOLR-15914
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Jan Høydahl
>            Priority: Major
>
> The solr tarball (and docker container) ships with several contribs, but 
> adding them to the classpath has earlier involved inserting 
> {{<lib>../../../foo.jar</lib>}} entries into solrconfig. There is also the 
> {{<sharedLib>}} config in solr.xml available as 
> {{{}-Dsolr.sharedLib=/my/folder,/my/other/folder{}}}. Finally we also have 
> package manager with own classloaders of course. We'll live with all of these 
> for some time, so let's make each one more pleasant to use.
> Today, to add a contrib to path you would add both {{dist/foo*.jar}} and 
> {{contrib/foo/lib/*.jar}} to classpath. Sometimes perhaps more.
> In this Jira I'd like to make it much easier for users to add a contrib to 
> path by its name. Goal is for something like
> {code:java}
> SOLR_MODULES=langid,extraction bin/solr start -c {code}
> The bin/solr script would have a map of contrib to lib-folders, and add those 
> as {{sharedLib}} entries, possibly appending to the user-supplied list of 
> sharedLib?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to