lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrien Grand (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4340) Move all codecs but Lucene40 to a module
Date Mon, 03 Sep 2012 17:25:07 GMT


Adrien Grand commented on LUCENE-4340:

I tried the proposed approach on my local copy (unfortunately, the diff is pretty meaningless
because of the svn mvoves, does anyone know how to produce something both readable and applyable
through svn?):

 - moved  all sub packages of oal.codecs except perfield and lucene40 to a new {{codecs}}
 - also moved BlockTerms{Reader,Writer}, FixedGapTermsIndex{Reader, Writer}, TermsIndex{Reader,Writer}Base,
 - lucene-codecs has been added to the classpath of test-framework,
 - lucene-codecs has been added to the test classpath of lucene-core.

Compilation and tests seem to work fine...

Does it look good to you? I tried to take care of javadocs, eclipse, idea and Maven, is there
anything else I should worry about?
> 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