[
https://jira.codehaus.org/browse/SUREFIRE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316633#comment-316633
]
Andreas Gudian edited comment on SUREFIRE-949 at 2/27/13 4:16 PM:
------------------------------------------------------------------
We definitely need that. :)
but {{forkMode=perthread}} and {{forkCount=X}} still reads funny. I'd (again)
like to suggest -adding a new parameter {{fork}} (boolean)- (ignore that,
wasn't necessary). Together with {{reuseForks}} and {{forkCount}}, we should be
able to cover everything. We then declare {{forkMode}} as deprecated. WDYT?
was (Author: agudian):
We definitely need that. :)
but {{forkMode=perthread}} and {{forkCount=X}} still reads funny. I'd (again)
like to suggest adding a new parameter {{fork}} (boolean). Together with
{{reuseForks}} and {{forkCount}}, we should be able to cover everything. We
then declare {{forkMode}} as deprecated. WDYT?
> Create forkCount parameter
> --------------------------
>
> Key: SUREFIRE-949
> URL: https://jira.codehaus.org/browse/SUREFIRE-949
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
> Reporter: Kristian Rosenvold
> Assignee: Kristian Rosenvold
> Fix For: 2.14
>
>
> The "threadCount" parameter is overloaded to the extent that it is becoming
> problematic. A forkCount parameter would be nice, maybe supporting the same
> style as maven-core "1.5C" for 1.5 x number of cores.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
