[
https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285241#comment-285241
]
John Casey edited comment on SUREFIRE-803 at 12/8/11 11:39 AM:
---------------------------------------------------------------
Something akin to what the failsafe plugin does might work, but it'd require a
surefire mojo executing later in the build process to read the reports and
trigger the build failure...which means running `mvn clean test` might not cut
it without re-shuffling the surefire executions to some earlier phase.
There might be other ways to detect whether the current execution is the last
(and therefore whether it's okay to fail the build now), but I'm not sure off
the top of my head.
was (Author: jdcasey):
Something akin to what the failsafe plugin does might work, but it'd
require a surefire mojo executing later in the build process to read the
reports and trigger the build failure...which means running `mvn clean test
> Multiple Surefire executions - FAILURE in an execution prevents successive
> from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Priority: Critical
>
> Let's have multiple Surefire executions in a single module (different config
> needed).
> A failure of a test in one of these executions prevents running the
> successive.
> Surefire's testFailureIgnore is not an option because it makes a run with
> failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests
> should run.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
