>Follow eclipse.md / Launching from Eclipse and you'll get the issue. That means there's no issue with "dist contains duplicate versions of jars". In other words, Gradle does not produce duplicate jars.
Gradle's dependency management is very flexible. Currently it resolves "groovy-all version 2.4.15" to be used for compilation and "groovy-all version 2.4.16" to be used for runtime. I'm not sure if Eclipse is flexible enough to represent that, however the resulting .classpath files seem to include both versions with no clear separation which is which. In the Ideal world, groovy-all should probably not be included to the compilation classpath (we don't expect to call low level Groovy APIs from JMeter's Java code). Vladimir
