[
https://issues.apache.org/jira/browse/LUCENE-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201613#comment-13201613
]
Dawid Weiss commented on LUCENE-3753:
-------------------------------------
Nah, just read the docs -- you're right, this is not multiple-test-per-jvm
allocation. I thought it was. Interestingly I did a small surefire replacement
for that ant task (with a few incompatibilities) that does run multiple jvms
for testing. If you want to check it out and provide feedback, it'd be awesome.
An example of use is in this POM:
https://github.com/carrotsearch/randomizedtesting/blob/master/integration-maven/junit4-maven-plugin-tests/src/it/01-basic-test/pom.xml
> 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]
