DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7980>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7980 JUnit spawned thread spits output to STDOUT, not formatter destination Summary: JUnit spawned thread spits output to STDOUT, not formatter destination Product: Ant Version: 1.4.1 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Consider the following buildfile snippet: <junit> <batchtest todir="${project.build.test.reports}" fork="no"> <formatter type="plain" usefile="yes" /> <fileset dir="${project.build.classes}"> <include name="**/Test*" /> </fileset> </batchtest> </junit> This buildfile snippet runs all classes which begin with "Test" (in our project, all such classes inherit from JUnit's "TestCase" class) in JUnit. Some of our "public void test*()" methods in these classes spawn Threads; some of these spawned Threads print output to System.out. This output actually goes to console, and not to the <formatter>'s destination as the documentation states: "Output will always be sent to a file unless you set the usefile attribute to false". This also occurs in the 1.5 alpha (nightly) build on 04-11-02. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
