lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3753) Restructure the Lucene build system
Date Mon, 06 Feb 2012 20:33:59 GMT


Robert Muir commented on LUCENE-3753:

if we had a single test task this would mean one could pattern-scope the tests to be executed
and (if not restricted) all of the tests would run in a single balancing scope (Mike pointed
out that currently a lot of time is spent on waiting for the last test in each spawned).

Yes, but this doesn't really test any dependencies that different contribs/modules might have
right? Or maybe i misunderstand what you are suggesting.

I think Mike's python runner "cheats" and makes a huge classpath... sure its faster, but,
it loses test coverage because modules could have
bogus dependencies and we would never know.

> Restructure the Lucene build system
> -----------------------------------
>                 Key: LUCENE-3753
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: general/build
>    Affects Versions: 3.6, 4.0
>            Reporter: Steven Rowe
>            Assignee: Steven Rowe
>         Attachments: LUCENE-3753.patch, LUCENE-3753.patch, LUCENE-3753.patch
> Split out separate core/, test-framework/, and tools/ modules, each with its own build.xml,
under the lucene/ directory, similar to the Solr restructuring done in SOLR-2452.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message