[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285672#comment-285672 ]
Kristian Rosenvold commented on SUREFIRE-803: --------------------------------------------- I think Stephen makes a 3/4 decent argument for keeping it in the xml file. The way I see this, the change will /not/ be modifying the surefire plugin, but only failsafe. So the user would typically replace surefire with failsafe, and then run "mvn verify" instead of "mvn test". Any executions of the failsafe plugin would simply record/update the file, and any executions from test to integration-test would simply amend their results, we're only interested in toggling from success->failure anyway, so that should be ok. This would of course leave us with the problem of /when to delete/ the file, and I suppose we could use the pluginContext for that, because Stephen seems to indicate there may be tools using that file. With the exception of amending to the current result, this is much the way failsafe works today, so it should be a tiny patch. Making some nice IT's is probably going to be half the effort... I am trying hard to remember the last time I used the pluginContext. It works, I have done it. I just can't remember when; argh. This /will/ wake me up tonight.... > 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: Improvement > Components: Maven Surefire Plugin > Affects Versions: 2.10 > Reporter: Ondrej Zizka > Assignee: John Casey > Attachments: surefire-803-failure-prevents-subsequent-executions.zip > > > 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. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira