ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saripalli, Raju" <>
Subject RE: <junit> task
Date Tue, 23 Apr 2002 15:30:39 GMT
Oops. My bad.

It does work. Thats what happens when ur staring at a damn
screen too long ;).

A quick question about using <classpath> elements in other
tasks such as <javac> and <junit>. Is there a way of elminating
the inclusion of the classpath of the process which actually
started the initial Ant build?



-----Original Message-----
From: Saripalli, Raju 
Sent: Tuesday, April 23, 2002 11:00 AM
To: ant-user (E-mail)
Subject: <junit> task


I have looked through the archives for this, but I have'nt had any luck.

Here is a portion of my build file, where I compile a set of tests and 
then run them from Ant using the <junit> tasks.

	<path id="">
		<pathelement location="${BIN_DIR}"/>
		<pathelement location="${LIB_DIR}"/>
		<fileset dir="${LIB_DIR}">
			<include name="**.jar"/>
			<include name="**.zip"/>
		<pathelement location="${PROP_DIR}"/>

	<target name="LOG_test" depends="LOG_compile">

		<javac srcdir="${TEST_SOURCE_DIR}" destdir="${BIN_DIR}">
			<patternset refid="log.pattern"/>
				<path refid="javac.test.classpath"/>

		<junit fork="yes">
				<path refid=""/>
			<formatter type="plain"/>
			<test name=""/>

The <junit> task does not pick up the nested classpath that I have
defined. Has anyone else run into the same issue ?



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message