You should be able to set the properties in the calling ant script or in your environment file using variables. Unfortunately it's been a while since I used Ant and can't remember exactly. If they are values that don't change set them directly, otherwise the env variables or properties in a file.
dependencies can be hard coded as well, from the Ant script calling the new task defs. KM On Friday, August 19, 2022 at 01:40:19 AM EDT, Hiran Chaudhuri <hiran.chaudh...@gmx.net> wrote: Hello there. I successfully created several custom Ant Tasks myself, thanks to the fine documentation in https://ant.apache.org/manual/developlist.html Now when I want to use these tasks, I always have to use taskdef elements in all my scripts and always remember exact dependencies (classpath) or the class names of the tasks. >From other libraries I have seen there are things like property or XML files bundled with the tasks that can host such information - but they seem to be an undocumented feature? How would I apply them correctly? Hiran --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@ant.apache.org For additional commands, e-mail: user-h...@ant.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@ant.apache.org For additional commands, e-mail: user-h...@ant.apache.org