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 24928] - Multithreaded JUnit test cases with Log4J and ANT
Date Wed, 26 Nov 2003 12:59:56 GMT
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=24928>.
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=24928

Multithreaded JUnit test cases with Log4J and ANT





------- Additional Comments From bodewig@apache.org  2003-11-26 12:59 -------
Ant attaches threads and their outputs to tasks to enable tasks running in
<parallel> to log without interfering with each other.

If you spawn a new thread, Ant won't know which task it belongs to and only
capture the output of the main thread for <junit> - and thus only this output
is going to end up in the output sent to the formatters.

If you fork <junit>, the task will only see one output (the output of the spawned)
VM and it will ge captured.  The alternative would be to explicitly register your
created threads with Ant's logging system which will be very hard if not impossible
to do (you'd need access to Project#registerThreadTask).

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


Mime
View raw message