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 21:04:59 GMT


Robert Muir commented on LUCENE-3753:

The speedups aren't dramatic, especially after Robert worked on the longest tests, so this
is not a huge priority.

Well, from time to time we try to clean up the tests... but i think it only takes a few weeks
for us to 'lose' all the benefits.
I'm not trying to say our tests get crappier, a lot of the reasons for the slowdown is really
just more test coverage...!

Basically, I don't think we can view speeding up slow tests as one-off tasks... its gotta
be a continuous maintenance thing.

For this reason, its important to speed up the other parts of the build (like rebuilding jars
over and over again 
such as this issue), and also to integrate the nice random test framework work etc you did...
these are more 'permanent'

However, I'm just concerned about adopting mike's cheating, because I like the idea of 'ant
test' being a total pain
to catch broken stuff. New modules, etc are added often, the build system is refactored, dependencies
upgraded, etc etc,
and I'm concerned we would somehow screw ourselves up and release stuff with bogus dependencies.

> 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