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.

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 svn version of ant some diagnostics
has been added to check this condition.

Peter


On 1/29/07, Andrew Close <[EMAIL PROTECTED]> wrote:
> 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 task.  however i'm now getting 'Process fork failed'
> messages, but no details as to why.  here is the target i'm using to
> invoke JUnit:
>
>         <target name="test" depends="package_tests" >
>                 <junit fork="${junit.fork}"
>                                 forkmode="${junit.forkmode}"
>                                 maxmemory="${junit.maxmemory}"
>                                 printsummary="${junit.printsummary}">
>                         <classpath refid="lib.path" />
>                         <formatter type="${junit.format.type}" />
>                         <batchtest todir="${test.rpts.dir}">
>                                 <fileset dir="${test.src.dir}">
>                                         <exclude name="**/AllTests.*" />
>                                         <include name="**/*Test*.java" />
>                                 </fileset>
>                         </batchtest>
>                 </junit>
>         </target>
>
> i've defined the following variables in my properties file:
>
> junit.compile.failonerror=true
> junit.fork=true
> junit.forkmode=perBatch  (i've tried the default and other options as well...)
> junit.format.type=xml
> junit.maxmemory=512m
> junit.printsummary=withOutAndErr
> junit.report.format=frames
>
> in the stacktrace that gets printed during the JUnit task i see
> java.io.FileNotFoundException: junitvmwatcher1116665720.properties
> (The system cannot find the file specified)
> is this a prop file that should be created by the JUnit task?  or do i
> still have something configured incorrectly?
>
> thanks for any insight.
> andy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to