lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3753) Restructure the Lucene build system
Date Mon, 06 Feb 2012 21:19:00 GMT


Dawid Weiss commented on LUCENE-3753:

@Robert. You're right, dependencies (and their order) may screw up things. I was tinkering
with an idea that testing could be a multi-pass process, then it would be possible to collect
all the "specs" in one pass and then run everything in another pass... but it temporarily
exceeds my time limits to actually implement this :)

@Steven. That was my impression from reading the release notes and from looking at the code:
Surefire 2.12 now supports parallel forks, which can also be run
in runOrder="balanced", which is a nice feature for long-running
Ah, I see -- I didn't mean "balanced" in the sense of dynamic balancing, the tests are statically
assigned, but they do run in separate concurrent slave JVMs and that's still something
> 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