lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4340) Move all codecs but Lucene40 to a module
Date Wed, 29 Aug 2012 12:24:08 GMT


Robert Muir commented on LUCENE-4340:

Sounds like a good plan. We can use ivy configuration for the dependency.

I also think "concrete" things not used by 4.0 codec like VariableGapTerms/BlockTermsWriter
etc should go to the module,
e.g. underneath packages like blockterms/. But some trickiness here: test-framework uses some
of this stuff (e.g. Lucene40WithOrds, NestedPulsing, etc).

So we have to figure out how to also support these test-only codecs somehow (maybe also RandomCodec
so we don't have to do a lot of craziness
to pass random parameters to these other codecs).

> Move all codecs but Lucene40 to a module
> ----------------------------------------
>                 Key: LUCENE-4340
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Task
>          Components: core/codecs, general/build
>            Reporter: Adrien Grand
>             Fix For: 5.0, 4.0
> We should move all concrete postings formats and codecs but Lucene40 to a module.

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message