That sounds like you are calling your ant tasks in the configuration phase of
gradle instead of the execution phase. Make sure your task is defined like:
"task mytask << { stuff to do }", not like "task mytask { stuff to do}" The
latter form will cause all of the contents of the closure to be evaluated every
time the gradle file is processed (even when you run -t).
If this isn't your issue, you might try posting the snippet of your build.gradle
file where the ant tasks are referenced.
barrymac wrote:
Adam Murdoch-2 wrote:
Could you give a bit more detail about what you're seeing? Gradle should
run the Ant targets in the correct order. If not, it's a bug.
When I run gradle -t then all the task.execute statements that are contained
in the defined in the task calling them are run.
When I run a different task then they still run.
I just found out however that it only happens when the syntax for defining
the task is as follows:
task doStuff {
but not when the syntax is:
createTask('doStuff') {
my mistake?
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
