[
https://issues.apache.org/jira/browse/LUCENE-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058730#comment-13058730
]
Hoss Man commented on LUCENE-3272:
----------------------------------
single module != single jar ... correct?
someone writing a small form factor app that wants to use the basic Lucene
QueryParser shouldn't have to load a jar containing every query parser provided
by solr (and all of the dependencies they have)
> Consolidate Lucene's QueryParsers into a module
> -----------------------------------------------
>
> Key: LUCENE-3272
> URL: https://issues.apache.org/jira/browse/LUCENE-3272
> Project: Lucene - Java
> Issue Type: Improvement
> Components: modules/queryparser
> Reporter: Chris Male
>
> Lucene has a lot of QueryParsers and we should have them all in a single
> consistent place.
> The following are QueryParsers I can find that warrant moving to the new
> module:
> - Lucene Core's QueryParser
> - AnalyzingQueryParser
> - ComplexPhraseQueryParser
> - ExtendableQueryParser
> - Surround's QueryParser
> - PrecedenceQueryParser
> - StandardQueryParser
> - XML-Query-Parser's CoreParser
> All seem to do a good job at their kind of parsing with extensive tests.
> One challenge of consolidating these is that many tests use Lucene Core's
> QueryParser. One option is to just replicate this class in src/test and call
> it TestingQueryParser. Another option is to convert all tests over to
> programmatically building their queries (seems like alot of work).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
