lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3076) add -Dtests.codecprovider
Date Thu, 05 May 2011 15:09:03 GMT


Uwe Schindler commented on LUCENE-3076:

bq. possibly containing your own set of huper-duper codecs

I will copypaste that to my brain's speech centre before the talk at Lucene Revolution to
entertain you again :-)

> add -Dtests.codecprovider
> -------------------------
>                 Key: LUCENE-3076
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>             Fix For: 4.0
>         Attachments: LUCENE-3076.patch
> Currently to test a codec (or set of codecs) you have to add them to lucene's core and
edit a couple of arrays here and there...
> It would be nice if when using the test-framework you could instead specify a codecprovider
by classname (possibly containing your own set of huper-duper codecs).
> For example I made the following little codecprovider in contrib:
> {noformat}
> public class AppendingCodecProvider extends CodecProvider {
>   public AppendingCodecProvider() {
>     register(new AppendingCodec());
>     register(new SimpleTextCodec());
>   }
> }
> {noformat}
> Then, I'm able to run tests with 'ant -lib build/contrib/misc/lucene-misc-4.0-SNAPSHOT.jar
test-core -Dtests.codecprovider=org.apache.lucene.index.codecs.appending.AppendingCodecProvider',
and it always picks from my set of  codecs (in this case Appending and SimpleText), and I
can set -Dtests.codec=Appending if i want to set just one.

This message is automatically generated by JIRA.
For more information on JIRA, see:

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

View raw message