http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1118

*** shadow/1118 Mon Mar 26 11:48:28 2001
--- shadow/1118.tmp.7353        Mon Apr  2 03:37:04 2001
***************
*** 2,11 ****
  | JUnit task problem with classpath nested element                           |
  +----------------------------------------------------------------------------+
  |        Bug #: 1118                        Product: Ant                     |
! |       Status: NEW                         Version: 1.3                     |
! |   Resolution:                            Platform: All                     |
! |     Severity: Normal                   OS/Version:                         |
! |     Priority:                           Component: Optional Tasks          |
  +----------------------------------------------------------------------------+
  |  Assigned To: [EMAIL PROTECTED]                                   |
  |  Reported By: [EMAIL PROTECTED]                                   |
--- 2,11 ----
  | JUnit task problem with classpath nested element                           |
  +----------------------------------------------------------------------------+
  |        Bug #: 1118                        Product: Ant                     |
! |       Status: RESOLVED                    Version: 1.3                     |
! |   Resolution: WONTFIX                    Platform: All                     |
! |     Severity: Normal                   OS/Version: All                     |
! |     Priority: High                      Component: Optional Tasks          |
  +----------------------------------------------------------------------------+
  |  Assigned To: [EMAIL PROTECTED]                                   |
  |  Reported By: [EMAIL PROTECTED]                                   |
***************
*** 24,27 ****
  around by using the CLASSPATH env variable.
  In contrast, the javac task correctly uses the nested classpath element. This 
  is why I think the problem is only in the JUnit task.
! Thanks for your help.
--- 24,33 ----
  around by using the CLASSPATH env variable.
  In contrast, the javac task correctly uses the nested classpath element. This 
  is why I think the problem is only in the JUnit task.
! Thanks for your help.
! 
! ------- Additional Comments From [EMAIL PROTECTED]  2001-04-02 03:37 -------
! junit.jar and optional.jar must be loaded via the same class loader, either 
you
! place junit.jar in your CLASSPATH or ANT_HOME/lib or you don't put 
optional.jar
! in ANT_HOME/lib at all and define the task via a <taskdef> with nested a
! <classpath> element, that contains both, junit.jar and optional.jar.

Reply via email to