I think that when I originally posted the question I misunderstood how custom tasks work. I didn't realize they were re-instantiated multiple times per build file.
I wanted to add a "forked" attribute to my task (or to any task really) to enable it to either run inside the same JVM or inside a new JVM. I'm no longer sure that is worth the headache though so I guess for now I will simply leave this attribute out. Gili [EMAIL PROTECTED] wrote: > > You can use something like a "presetdef" to set default values for your > task, and then use the presetdef when calling the task instead of the > original one. Is this what you want? > > On Tue, Aug 19, 2008 at 3:56 PM, cowwoc <[EMAIL PROTECTED]> wrote: > >> >> Hi, >> >> This seems like such an obvious use-case but from what I read in this >> forum >> there doesn't seem to be a way to do it... is there a way for me to pass >> parameters to my custom task at taskdef (initialization time)? >> >> One obvious use-case is grabbing the classpath used in the taskdef during >> the task execution time, but this could pretty much apply to any variable >> I >> want to initialize *once* and reuse anytime the task is invoked. Is this >> possible in Ant 1.7? >> >> Thank you, >> Gili >> -- >> View this message in context: >> http://www.nabble.com/Initializing-Task-variables-at-taskdef-time--tp19048295p19048295.html >> Sent from the Ant - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/Initializing-Task-variables-at-taskdef-time--tp19048295p19051702.html Sent from the Ant - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
