ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 639] Changed - JUnitTestRunner masks exceptions
Date Wed, 21 Feb 2001 12:13:41 GMT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=639

*** shadow/639	Mon Feb 19 11:05:53 2001
--- shadow/639.tmp.29889	Wed Feb 21 04:13:40 2001
***************
*** 2,9 ****
  | JUnitTestRunner masks exceptions                                           |
  +----------------------------------------------------------------------------+
  |        Bug #: 639                         Product: Ant                     |
! |       Status: NEW                         Version: Nightly build           |
! |   Resolution:                            Platform: All                     |
  |     Severity: Normal                   OS/Version: All                     |
  |     Priority: High                      Component: Optional Tasks          |
  +----------------------------------------------------------------------------+
--- 2,9 ----
  | JUnitTestRunner masks exceptions                                           |
  +----------------------------------------------------------------------------+
  |        Bug #: 639                         Product: Ant                     |
! |       Status: RESOLVED                    Version: Nightly build           |
! |   Resolution: FIXED                      Platform: All                     |
  |     Severity: Normal                   OS/Version: All                     |
  |     Priority: High                      Component: Optional Tasks          |
  +----------------------------------------------------------------------------+
***************
*** 45,48 ****
  ------- Additional Comments From jesse.glick@netbeans.com  2001-02-19 11:05 -------
  FWIW no-arg version of printStackTrace() is generally better because it uses
  System.err, which is unbuffered so you are not likely to get mingled exceptions
! from different threads.
--- 45,52 ----
  ------- Additional Comments From jesse.glick@netbeans.com  2001-02-19 11:05 -------
  FWIW no-arg version of printStackTrace() is generally better because it uses
  System.err, which is unbuffered so you are not likely to get mingled exceptions
! from different threads.
! 
! ------- Additional Comments From conor@cortexebusiness.com.au  2001-02-21 04:13 -------
! The code has been changed to behave like other JUnit test runners. Will be 
! included in Ant 1.3 Beta 3

Mime
View raw message