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=5377>. 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=5377 JUnit spits System.out to System.out, not formatter log file, when fork="yes" Summary: JUnit spits System.out to System.out, not formatter log file, when fork="yes" Product: Ant Version: 1.4 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Example: <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> Using this buildfile snippet, classes which begin with "Test" (in our project, all such classes inherit from JUnit's "TestCase" class) spit System.out.println ()s to default test case output files (using <formatter> rules to come up with an output filename for each TestCase class). Changing fork from "no" to "yes" makes Ant spit System.out.println()s to STDOUT, not log file. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
