I have a custom task that extends the Java task because I want to be able to 
conditionalize on the exit code of the Java application.  I can't use the exec 
task because I have the need to specify JVM parameters and also have a very 
complicated classpath, for which I use a series of path elements.  My custom 
task simply looks at the exit code of the application and sets the exitCode 
property.  Simple enough.

Okay, now the problem comes in.  I have a target that uses this custom task:

  <target name = "run.client" depends = "run.initialize">
    <taskdef name = "myjava" classname = "com.my.tasks.JavaTask" classpathref = 
"project.class.path" />
    
    <myjava classname = "com.my.Application" classpathref = 
"project.class.path" fork = "true">
      <jvmarg value = "-Djava.library.path=${dir.bin" />
    </myjava>

    <echo message = "EXIT CODE is ${exitCode}" />
  </target>

This all works fine.  However, if I invoke this target from another target, 
using antcall, then the property doesn't seem to be set in my calling target:

  <target name = "run">
    <parallel>
      <antcall target = "run.server" />

      <sequential>
        <sleep seconds = "5" />
        <antcall target = "run.client" />

        <echo message = "This is the exit code of the client: ${exitCode}" />

        <antcall target = "stop.server" />
      </sequential>
    </parallel>
  </target>

The output from Ant looks like this:

   [echo] Server running...
  [echo] EXIT CODE is 1
  [echo] This is the exit code of the client: ${exitCocde}

As you can see, it treats the first echo command like the property is set, it 
shows the value.  However, in the calling target it treats it like it hasn't 
been set.  Can this be a by-product of using the parallel and sequential tasks?

Also, can somebody show me an example of how to conditionalize a call based on 
the exitCode property, if and when it is properly set?

Thanks for any help!

Reply via email to