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

Uwe Schindler commented on SOLR-3843:
-------------------------------------

If users want to experiment they just need to copypaste a file, where is the 
problem?

In addition: The analysis-extras module is also not needed (except the special 
ICUField, which may more into a solr-icu module), as all analysis factories are 
already inside the analyzers jar. In my opinion, the Solr WAR file should only 
bundle analyzers-common.jar and nothing more. The analysis-extras build.xml 
file is the worst I have seen: It just copies some JAR files from Lucene to 
Solr.

To make it easier for people, we can add a command that uses get/ivy to 
download the JAR file from Maven and install it in solr's lib folder. Optional 
stuff should not be in the WAR file.
                
> Add lucene-codecs to Solr libs?
> -------------------------------
>
>                 Key: SOLR-3843
>                 URL: https://issues.apache.org/jira/browse/SOLR-3843
>             Project: Solr
>          Issue Type: Wish
>    Affects Versions: 4.0
>            Reporter: Adrien Grand
>            Priority: Critical
>             Fix For: 4.2, 5.0
>
>         Attachments: SOLR-3843.patch, SOLR-3843.patch, SOLR-3843.patch
>
>
> Solr gives the ability to its users to select the postings format to use on a 
> per-field basis but only Lucene40PostingsFormat is available by default 
> (unless users add lucene-codecs to the Solr lib directory). Maybe we should 
> add lucene-codecs to Solr libs (I mean in the WAR file) so that people can 
> try our non-default postings formats with minimum effort?

--
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