https://bz.apache.org/bugzilla/show_bug.cgi?id=65176
Jaikiran Pai <jaiki...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Target Milestone|--- |1.10.14
Status|NEW |RESOLVED
--- Comment #5 from Jaikiran Pai <jaiki...@apache.org> ---
This has now been implemented. A new optional attribute "forkMode" can be
provided to the <fork> element of <junitlauncher> task. That attribute allows
"perTestClass" as a value and if that is what is specified then each of the
test class is forked in a separate JVM of its own.
Here's the documentation
https://github.com/apache/ant/blob/master/manual/Tasks/junitlauncher.html#L643:
<td>forkMode</td>
<td>Controls how many JVMs are launched for the forked tests. Allowed
values are:
<ul class="inlinelist">
<li><code>perTestClass</code> - This mode launches each test
class in a
separately forked JVM</li>
</ul>
<p><em>Since Ant 1.10.14</em></p>
</td>
<td>No; defaults to launching all test classes in one single forked
JVM.</td>
This will be available in the upcoming 1.10.14 release.
It will be helpful if one of you could try it out against our nightly Ant
builds
https://ci-builds.apache.org/job/Ant/job/Ant_Nightly/lastSuccessfulBuild/artifact/distribution/
--
You are receiving this mail because:
You are the assignee for the bug.
