Well I`ll now try to use your advise, and I didin`t know that --continue has influence only on test type tasks. But actually my gradle script is a little more complex. Each of my android projects are having two build.gradle files. I want to run each application twice, with differneces in number of tasks. That`s why I am using GradleBuild task types, because it is impossible to run a task twice during the gradle script execution.
Maybe there is a way to make a try-catch block, as it is made in gradle`s test task? But then it is probably necessary to write a task in buildSrc foler and create something like my own plugin? Вівторок, 19 серпня 2014 р. 18:58:58 UTC+3 користувач Xavier Ducrohet написав: > > It looks like you are creating a task that is meant to run a separate > Gradle call, per subproject. so each project is called with --continue, but > the first call isn't. > > --continue is used very specifically by task of type Test so that they do > not throw an exception if a test fail in order to not stop the execution of > Gradle. The GradleBuild task likely doesn't do that. > > I would find a different solution. For instance create a simple empty > task, then figure out which projects you want to run (since it seems to be > dynamic), and simply make you empty task depend on the project task using > the "fully-qualified" task name (:mysubproject:connectedAndroidTest'). > > -- > Xavier Ducrohet > Android SDK Tech Lead > Google Inc. > http://developer.android.com | http://tools.android.com > > Please do not send me questions directly. Thanks! > -- 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/d/optout.
