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

Steve Rowe edited comment on SOLR-3843 at 2/25/13 11:26 PM:
------------------------------------------------------------

bq. I guess for now I was just looking at us doing things consistently. Even if 
we are consistently wrong :)

Right, makes sense - in this case the consistent thing to do is to make the 
solr-core module, rather than the webapp module, depend on the lucene-codecs 
jar in the Maven build.  The attached patch does this.
                
      was (Author: steve_rowe):
    bq. I guess for now I was just looking at us doing things consistently. 
Even if we are consistently wrong :)

Right, makes sense - in this case the consistent thing to do is to make the 
solr-core module, rather than the webapp module, depend in lucene-codecs jar in 
the Maven build.  The attached patch does this.
                  
> 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