I usually use ScriptDefs, but I needed to extend an abstract task that another custom task extends, to handle a set of nested data elements that I need to pass to it.
I also found, contrary to my earlier post, that I didn't need to explicitly code the property setters. Thanks, Mike -----Original Message----- From: Antoine Levy Lambert [mailto:anto...@gmx.de] Sent: Tuesday, December 08, 2009 7:47 AM To: Ant Users List Subject: Re: Custom Task using Groovy Hello Mike, you could define your task using scriptdef. See http://ant.apache.org/manual/OptionalTasks/scriptdef.html Then your groovy class does not need to extend Task. Regards, Antoine Murray, Mike wrote: > I've created a groovy class that (indirectly) extends Task, and I'm > calling it from my build script, but the property setters are not > getting called. I've even explicitly coded the setters, to make sure > they are visible to the Ant code. > > > > Is there some trick I am missing, or am have I just overlooked something > dumb in my code? > > > > Thanks, Mike --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@ant.apache.org For additional commands, e-mail: user-h...@ant.apache.org
