That kind of granular control isn't really the Gradle paradigm. The Gradle paradigm is about expressing dependencies and relationships in artifacts (declarative), not laying out a set of instructions (imperative).
~~ Robert. On Fri, Jun 17, 2011 at 5:53 PM, phil swenson <phil.swen...@gmail.com> wrote: > Ok, the reason I wanted this behavior is so I could have granular > control of each task unless I ran the whole batch. But I will work > around this. > > thanks > > On Fri, Jun 17, 2011 at 3:33 PM, Robert Fischer > <robert.fisc...@smokejumperit.com> wrote: >> There's no guarantied ordering of dependencies. If >> localeGenerateArchives depends on localeGenerateResources, it should >> say so itself. >> >> ~~ Robert. >> >> >> >> On Fri, Jun 17, 2011 at 5:16 PM, phil swenson <phil.swen...@gmail.com> wrote: >>> buildLanguagePackTask.dependsOn(["localeExportMessages", >>> "localeGenerateResources", "localeGenerateArchives"]) >>> >>> I was wondering why my build was failing, turns out it's because >>> dependency #3 is getting run before #2. Solutions? >>> >>> BTW, I'm on gradle 1.0 m3 >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
