[
https://issues.apache.org/jira/browse/LUCENE-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201559#comment-13201559
]
Robert Muir commented on LUCENE-3753:
-------------------------------------
{quote}
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).
{quote}
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: https://issues.apache.org/jira/browse/LUCENE-3753
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
