On 6 Jul 2014, at 6:50 am, Daz DeBoer <darrell.deb...@gradleware.com> wrote:
> I'm pretty sure we don't want to expose a raw ExecutorService. We are pretty > careful about exposing Gradle APIs that we have control over, rather than > APIs that we don't have control over. I don’t think we talking about adding a public mechanism here, are we? - just some internal mechanism to get parallel compilation working. Given this, ExecutorService isn’t a bad option to start with. Or something that looks something like ExecutorService (a queue of Runnable things) that we can grow into the public thing. -- Adam Murdoch Gradle Co-founder http://www.gradle.org CTO Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
