ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 47558] New: Assertion status silently ignored by <junit> if unforked
Date Wed, 22 Jul 2009 15:10:20 GMT

           Summary: Assertion status silently ignored by <junit> if
           Product: Ant
           Version: 1.6.0
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Optional Tasks

Compare the <junit><assertions> code added to 1.6 to from bug #21387; it
does not support assertions in unforked mode, and looks like it does not even
warn you if you try. Options:

1. Make JUnitTask.executeInVM warn:

        if (getCommandline().getAssertions() != null) {
            log("assertions are ignored if running in the same VM.",

2. Add a method to BaseAssertion to configure a ClassLoader with
set*AssertionStatus, and use this in JUnitTask.executeInVM (possibly also in

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

View raw message