You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2011/07/01 09:19:43 UTC
[jira] Closed: (SUREFIRE-738) Fail on not existing run order.
[ https://jira.codehaus.org/browse/SUREFIRE-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-738.
---------------------------------------
Resolution: Fixed
Assignee: Kristian Rosenvold
Thanks, Nice patch! Applied unmodified in r1141846
> Fail on not existing run order.
> -------------------------------
>
> Key: SUREFIRE-738
> URL: https://jira.codehaus.org/browse/SUREFIRE-738
> Project: Maven Surefire
> Issue Type: Improvement
> Reporter: Stefan Birkner
> Assignee: Kristian Rosenvold
> Priority: Minor
> Attachments: surefire-738.patch
>
>
> I want surefire to fail, if I start surefire with a run order, which is not in the set alphabetical, reversealphabetical, random, hourly and fileset.
> Today I don't get any information, when I start surefire with a wrong run order like alphapetical.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira