ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38006] New: - Ant JUnit batchtest eats log4j console output of 2nd and subsequent tests
Date Thu, 22 Dec 2005 07:49:03 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38006>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38006

           Summary: Ant JUnit batchtest eats log4j console output of 2nd and
                    subsequent tests
           Product: Ant
           Version: 1.7Alpha (nightly)
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Optional Tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: jamie@white-mountain.org


When using log4j console appenders in multiple test classes run with the Ant
JUnit task via batchtest, only the first test class that runs has its console
appender output go to the TEST-xxx.txt output file. All the rest of the classes'
console appender output go nowhere.

I created a test case to demonstrate this, and to show that explicit System.out
works normally, as does log4j output to FileAppenders. It's just console
appenders in everything but the first-run test class that fail.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message