Hi Chris, I hate to add confusion to this, but I wonder, do we have an idea how many modules will need to interact with a queryparser? If so, it might be worth making a simple abstract or even interface queryparser in core with something like Query parse(String text) throws ParseException
This could be overkill, but it would allow modules that need to use this stuff to depend upon the interface, not the implementation... again feel free to ignore me, but this is how we pulled this off with Analyzer. Otherwise, another idea you could consider is naming the surround one SurroundQueryParser? On Wed, Jul 6, 2011 at 1:00 AM, Chris Male <[email protected]> wrote: > Hi, > I'm in the process of consolidating the various QueryParsers into a single > queryparser module and Ryan reminded me that the names of the QPs could > probably be clearer. For example, we currently have two parsers called > QueryParser. Given that the core QueryParser is no longer going to be in > core, I think it could do with a name that more accurately describes its > purpose. > Does anybody have any thoughts on how to name the following parsers: > org.apache.lucene.queryParser.QueryParser (lucene core) > org.apache.lucene.queryParser.surround.parser.QueryParser (queryparser > contrib) > org.apache.lucene.queryParser.standard.StandardQueryParser (queryparser > contrib) > Cheers > Chris > -- > Chris Male | Software Developer | JTeam BV.| www.jteam.nl > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
