Hello,
Using Ant version 1.5.
Is it possible that the optional Junit task
ignores a nested <classpath>? That seems to
be the case here.
I have a case like this:
<junit printsummary="yes" ....more
attributess...>
<classpath refid="test.classpath"/>
<batchtest todir="${reports.dir}">
<fileset
dir="${build.classes.dir}">
<include
name="**/*Test*.class"/>
</fileset>
</batchtest>
</junit>
This 'test.classpath' is set as:
<path id="test.classpath"
path="${test.classpath}"/>
'test.classpath' is a property set in a
properties file that IS being read.
However, when I run ant with -verbose, I see
the invocation of JUnitTestRunner class, but
the classpath does not contain the value
specified in test.classpath.
Because of that my tests fail with
ClassNotFound exception.
Does this sound familiar to anyone?
I was able to specify the classpath as
described above, with Ant 1.4.1.
Thanks,
Otis
P.S.
Note that the classpath does get set if I
use it like this:
<junit printsummary="yes" .....>
<classpath>
<pathelement location="${build.classes.dir}"/>
</classpath>
....
....
________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
