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

Uwe Schindler commented on SOLR-4495:
-------------------------------------

Another idea (brought up in SOLR-4653) is the use of a better glob pattern 
syntax. My idea was to use similar approach like ANT's fileset/classpath 
definitions. We can use plexus-utils-1.1.jar, which provides DirectoryScanner 
that understands patterns like {{\*\*/\*.jar}}.

Also your patch is now outdated after SOLR-4652: You should not create a 
ClassLoader at all, but instead add the components of classpath to the shared 
ResourceLoader using addToClassPath(). See the changes in SOLR-4652.
                
> solr.xml sharedLib attribtue should take a list of paths
> --------------------------------------------------------
>
>                 Key: SOLR-4495
>                 URL: https://issues.apache.org/jira/browse/SOLR-4495
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>            Reporter: Jan Høydahl
>              Labels: classpath, solr.xml
>             Fix For: 4.3
>
>         Attachments: SOLR-4495.patch
>
>
> solr.xml's sharedLib is a great way to add plugins that should be shared 
> across all cores/collections.
> For increased flexibility I would like for it to take a list of paths. Then 
> I'd put Solr's own contrib libs in one shared folder "solrJars" and custom 
> plugins with deps in another "customerJars". That eases Solr upgrades, then 
> we can simply wipe and replace all jars in "solrJars" during upgrade.
> I realize that solr.xml is going away, and so the same request will be valid 
> for whatever replaces solr.xml, whether it be system prop or properties file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]

Reply via email to