On 13 April 2013 17:11, Peter Niederwieser <pnied...@gmail.com> wrote: > Daz DeBoer-2 wrote >> 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 > > I'm not sure if we are on the same page already. What I'm saying is that we > should change the behavior of `--parallel` to honor the contract I > mentioned. How we do that is secondary (for now).
While I agree this makes sense for: "gradle --parallel clean build " it's not so clear that it works for: "gradle --parallel :a:build :b:build" Do you really want to wait for 'a' to finish building before starting to build 'b'? So I'm not sure about making this an explicit contract. I'm not 100% against, but I don't think it's a given either. I think we first need to define exactly what the contract means, ie: "gradle clean build" constructs an anonymous build-type with parameters "clean, build" (where build-type is a well-defined construct). Daz > > Cheers, > Peter > > > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/command-line-order-and-parallel-build-tp5711162p5711189.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
