Peter,
thanks for your response. the simple solution was to add the
junit.jar to my ant lib/ dir. duh. thanks for 'reminding' me of the
verbose feature. i'll try to be a bit more diligent in the future. ;)
andy
On 1/29/07, Peter Reilly <[EMAIL PROTECTED]> wrote:
try with ant -verbose.
Th
try with ant -verbose.
This problem can happen with having old versions
of ant in the classpath of the forked junit task.
In this case the contents of lib.path should be looked
at. (common causes would be jars that have embedded
ant classes - fo example weblogic.jar and jrun.jar)
In the current
hello all,
i'm attempting to get the fork attribute to work with the optional
JUnit task. when attempting a build on this machine we are getting
JVM OutOfMemoryErrors during the JUnit task. so i figured i would use
the fork command and then be able to up the JVM heap size for that
particular ta
