Yes, calling execute() on tasks is not supported in any way. Gradle is always in control of deciding when to execute tasks (i.e. via dependsOn, mustRunAfter, finalizedBy etc.) and not the build script author. Therefore, it makes no sense to try and programatically execute a task.
On 28 Jan 2014, at 4:22 am, Anton Rutkevich <[email protected]> wrote: > Hi, > > I may be missing something, but as far as I remember, executing tasks with > execute() method executes only task itself, not its task dependencies. > Besides, execute() is internal api of org.gradle.api.internal.AbstractTask > > http://www.gradle.org/docs/current/javadoc/org/gradle/api/DefaultTask.html > > On Monday, January 27, 2014 8:56:13 PM UTC+3, [email protected] wrote: > Hi, > > I have a task that needs to do some work before calling build itself. And I > wanted to call build manually from that task. Accordingly to what I have > found it can be done with something like this: > > task someTask << { > ... > tasks['build'].execute() > ... > } > > But it does not trigger build at all. Though the same way of calling tasks > works fine with the tasks declared inside build.gradle. > Am I missing something here? > > P.S. I was able to trigger build by placing dependsOn inside task declaration > task someTask(dependsOn : 'build') << { > ... > } > > but it is not what I am looking for > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
