On 13 April 2013 16:09, Peter Niederwieser <pnied...@gmail.com> wrote: > Daz DeBoer-2 wrote >> So the current command-line ordering is more like "should run after". > > In my mind, the guarantees are much stronger. My mental model is: > > "For the purpose of task execution order, `gradle foo bar` is the same as > `gradle foo; gradle bar`, except that each task is executed at most once."
Right, this is exactly what I referred to in the fourth alternative that I outlined: and I agree it's probably the mental model that most users have. But this isn't the same as saying this as a mustRunAfter constraint. When I said the current behaviour is more like "should run after", I was comparing to "must run after". I think that in the non-parallel case, the current behaviour behaves exactly like "should run after" would. The problem is that this equivalence doesn't translate to the parallel world. I guess we don't currently have a nice way to describe the 'contract' that you're expecting to be honoured: perhaps build types will give us this language and a way to express it programmatically. > Users rely on this all the time: > > gradle clean build (clean everything before building anything) > gradle build uploadArchives (build everything before uploading anything) > gradle test sonarAnalyze (compile and test everything before running Sonar > analysis) > etc. > > I'd totally expect `--parallel` to honor this contract. If we have strong > evidence that being less strict makes `--parallel` significantly faster in > practice, then I suggest we add a *new* syntax/option/whatever for that. But > we shouldn't touch the existing one. > > Cheers, > Peter > > > > > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/command-line-order-and-parallel-build-tp5711162p5711187.html > Sent from the gradle-dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Darrell (Daz) DeBoer Principal Engineer, Gradleware http://www.gradleware.com Join us at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: http://www.gradlesummit.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
