That said, I think the Antelope project on SF added a custom <antcall> task allowing just that, returning properties to the parent process. But this is very unlikely to ever make it to Ant proper. --DD
-----Original Message----- From: Dominique Devienne [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 5:24 PM To: 'Ant Developers List' Subject: RE: Trouble using user properties in custom Ant task, help!!! Ant 101: Properties set during an <antcall> are not visible to the callee (which lives in a different Project). This has nothing to do with using <parallel>, <sequential>, or your custom task for that matter. --DD -----Original Message----- From: Barry Lulas [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 4:58 PM To: [EMAIL PROTECTED] Subject: Trouble using user properties in custom Ant task, help!!! 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! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
