Hey guys, Today, I had a long chat with PeterN about our current strategy for command line order in a parallel build. Consider this:
gradle taskA taskB --parallel 1. We can let taskA graph and taskB graph execute in parallel. That's how Gradle 1.5 works and it feels pretty natural to me. It breaks certain 'clean build' scenarios (e.g. http://forums.gradle.org/gradle/topics/problem_with_clean_in_parallel_mode) 2. We can let taskA graph execute in parallel first. Then we let the taskB graph execute in parallel. This approach can be considered more consistent with the single threaded execution. What's the right way? Cheers! -- Szczepan Faber Principal engineer@gradleware; Lead@mockito Join me at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: http://www.gradlesummit.com
