Muhammad>gradle supports parallel execution The good thing is Gradle can run tests from "core" in parallel with javadoc build for "cassandra" and so on.
Muhammad> Will this ease the project importing process to Eclipse ? This is usually a Muhammad> problem to me. I have to close projects to avoid displaying their build Muhammad> errors, define source folders, run mvn eclipse:eclipse (and some say I Muhammad> don't have to) and still have a couple of projects showing build errors in Muhammad> Eclipse. I don't use Eclipse, however: 1) They say Gradle projects could be imported to Eclipse just fine. I'm updating Apache JMeter's build system to Gradle at the moment (see https://github.com/apache/jmeter/pull/448 ), and you can try importing the project to see how it feels like (see gradle branch https://github.com/vlsi/jmeter/tree/gradle ). You can try importing https://github.com/ben-manes/caffeine/ , or https://github.com/spring-projects/spring-framework/ or whatever you like. However I'm inclined to Kotlin-based DSL, as it has way less magic than in Groovy-based scripts. 2) Gradle is very easy to customize. That is if default import somehow fails, the build script can contain customizations to make import better. For instance, you can check https://github.com/ben-manes/caffeine/blob/master/gradle/eclipse.gradle Vladimir
