Yes. "gradle c" would work. "gradle a b" would work. Adding "b" at the end of "a" would work. And I can think of half a dozen other ways of solving the problem as stated with slightly different implications. Without an actual use-case, all that can be talked about is vague generalities. If none of the current suggestions makes it clear "Oh, I can adapt it in *this* way to my problem" then a clearer statement of the problem is needed...
On Fri, Aug 20, 2010 at 4:40 PM, Robert Fischer < [email protected]> wrote: > But then if I do "gradle a", I'll always get "b" run, too, right? > > ~~ Robert. > > > On 20 August 2010 16:37, Matthias Bohlen <[email protected]> wrote: > >> How about a.doLast(b) ? Does that work? >> >> Am 20.08.2010 um 22:10 schrieb Robert Fischer: >> >> I suppose that'll work for the time being. As long as nobody expects >> "gradle a b" to work. >> >> ~~ Robert. >> >> On 20 August 2010 16:00, Jim Moore <[email protected]> wrote: >> >>> Depends on your need, but it sounds like you simply need >>> >>> task c(dependsOn: [a, b]) {} >>> >>> >>> On Fri, Aug 20, 2010 at 3:51 PM, Robert Fischer < >>> [email protected]> wrote: >>> >>>> Is there a way to tell Gradle, "If task A is being executed, make sure >>>> to run task B after task A"? I specifically don't want to make Task A a >>>> dependency on B (it shouldn't run every time), but I'd like it to run them >>>> together now and again, and when that happens they need to run in a certain >>>> order. >>>> >>>> ~~ Robert. >>>> >>> >>> -Jim Moore >>> >> >> >> > -Jim Moore
