Resolved. It works fine to code a custom task with Groovy and no setter methods need to be coded.
The "trick" is to not have a macrodef with the same name as your task. When I meant to call my macrodef, it was calling my task directly. So the arguments that are passed to my task by my macrodef were never passed. From: Murray, Mike Sent: Tuesday, December 01, 2009 11:45 AM To: user@ant.apache.org Subject: Custom Task using Groovy 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
