[ https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-1449: --------------------------- Attachment: SOLR-1449.patch minor update to the previous patch... 1) the patch command didn't like the empty files, so now they have a single newline in them. 2) because of a typo, javadoc-all on the trunk is getting lucking and finding the download clustering jars only if they've already been copied to the example/lib ... since the patch stops the copying to example/lib i fixed the topy so it finds them in lib/downloads > 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.