https://bz.apache.org/bugzilla/show_bug.cgi?id=70175
--- Comment #2 from Maarten Coene <[email protected]> --- Hi Jaikiran, we also use the haltonfailure property. <junit fork="yes" haltonerror="false" haltonfailure="false" ... became: <junitlauncher haltonfailure="false"> <testclasses ...> <fork forkMode="perTestClass" ...> ... </fork> </testclasses> </junitlauncher> I'm not sure we really distinguish between JUnit errors/failures ourselves: they are all things that needs to be addressed. The problem we run into is that with the JUnit task, the haltonerror='false' makes the JUnit task continue with the next test, even if the current test crashed (for instance a VM crash). With the JUnitLauncher Task, the task just stops after such a crash. We want to be able to configure this JUnitLauncher task to proceed to the next test in this case: the 'haltonerror' property seems to be a good fit for this. -- You are receiving this mail because: You are the assignee for the bug.
