maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Rosenvold (JIRA)" <>
Subject [jira] Commented: (SUREFIRE-555) Support junit core for parallel running of tests
Date Wed, 04 Nov 2009 01:25:55 GMT


Kristian Rosenvold commented on SUREFIRE-555:

Yes to all. Will resubmit tomorrow.

The purpose of the separated directory scanner was really just to get it unit-testable as
an individual piece. I suppose I couldn't resist the urge to make things more unit-testable,
since they're both faster and easier to write. There is also a unit-test for that separate
piece of code. At that point I guess It was a bit irresponsible of me not to replace usage
in the other plugins too, but I suppose I realized I was getting a bit carried away. The api-contract
of the separated scanner is also slightly cleaner than the original. 

I can take this both ways (revert to old-style or change the other plugins), what do you think

> Support junit core for parallel running of tests
> ------------------------------------------------
>                 Key: SUREFIRE-555
>                 URL:
>             Project: Maven Surefire
>          Issue Type: New Feature
>         Environment: All
>            Reporter: Kristian Rosenvold
>         Attachments: surefire.patch, surefirev2.patch
> The enclosed patch adds junitcore support to surefire. The patch requires junit 4.6 (the
latest released version) to compile, but is only activated when running with the 4.7 snapshot
or higher (due to some bugs in 4.6).  The patch adds one extra setting to the surefire plugin.
More details at
> The new plugin also requires an external library which can be found at,
which will be bumped to 1.0 when/if you decide to accept the patch. I am requesting that the
junit project actually accept the features of the configurable-parallel-computer as a standard
feature in junit 4.7, but that's not decided yet. I do not have a public maven repo that is
hosting configurable-parallel-computer, but was hoping maybe you could publish it ?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message