ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 1118] New - JUnit task problem with classpath nested element
Date Mon, 26 Mar 2001 19:48:28 GMT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1118

*** shadow/1118	Mon Mar 26 11:48:28 2001
--- shadow/1118.tmp.14534	Mon Mar 26 11:48:28 2001
***************
*** 0 ****
--- 1,27 ----
+ +============================================================================+
+ | 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: ant-dev@jakarta.apache.org                                   |
+ |  Reported By: martin.moorhead@viaken.com                                   |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ The JUnit task does not seem to correctly use the classpath nested element. I 
+ have used this nested element to point to where the junit.jar file is located 
+ and the junit task failed. The error reported is that optional.jar needs to be 
+ added into the ant/lib directory, but I have already done this. 
+ I have been able to work around this problem by using the CLASSPATH environment
+ variable to point to junit.jar, but I would rather not do that. This problem 
+ occurs on both Windows 2000 and Linux platforms and in both cases can be worked 
+ 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.

Mime
View raw message