Do Ant JUnit tasks require an environment variables for CLASSPATH?
My Ant JUnits always fail with a Ant Property defined CLASSPATH.
I am trying to write OS independant Ant scripts that build, demploy
and call my JUnit tests. I use property definitions (in a file) for
all the environment parameters (CLASSPATH et al) and have had good
results with all the standard tasks.
The JUnit's fail every time. The error is 'cannot find the
optional.jar' - which is on the Property defined CLASSPATH. These
same Property definitions converted to env vars work great! I have
also tried some <systemproperty> and <classpath> overrides in the
JUnit task itself to no avail.