ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <DDevie...@lgc.com>
Subject RE: another unit-test question
Date Wed, 05 Mar 2003 14:55:55 GMT
FWIW, junit.jar does not need to be explicitly in the <junit> classpath, as
Ant will automatically add it. For compiling the tests though, you need it,
but to have <junit> work correctly, it's already in the system CLASSPATH, or
ANT_HOME/lib, so you also don't need it explicitly for <javac> either,
unless you use a combination of includeAntRuntime=false and/or
includeJavaRuntime.

All that because optional tasks require their dependent classes to be in
either system CLASSPATH or ANT_HOME/lib... --DD

-----Original Message-----
From: Erik Hatcher [mailto:jakarta-ant@ehatchersolutions.com] 
Sent: Tuesday, March 04, 2003 6:54 PM
To: Ant Users List
Subject: Re: another unit-test question

On Tuesday, March 4, 2003, at 07:42  PM, Erik Price wrote:
> Great.  ${ant.home} was exactly what I needed.  (Actually, it didn't 
> work at first, and I wondered if I had done something wrong but my 
> build file seemed to be right.  It turns out that junit.jar doesn't 
> work if it's a symlink [at least on Cygwin], but when I copied the JAR 
> into ANT_HOME it worked great.  Strangely, xalan.jar [for generating 
> reports per the <junitreport> task] works fine as a symlink into 
> ANT_HOME.)

I'm guessing you mean ANT_HOME/lib rather than just ANT_HOME here.  
Only the lib subdirectory is part of the operating classpath, not the 
root directory (just in case that was the issue you had).

Mime
View raw message