Somehow having the Gradle Executable Jar plugin in Gradle's classpath makes tests in a module (in a multi-module project) not having the plugin applied behave differently, ie. it hangs in a deadlock or something similar.
By having the classpath for gradle-executable-jar-plugin only where it is needed, the problem goes away
Somehow having the Gradle Executable Jar plugin in Gradle's classpath makes tests in a module (in a multi-module project) not having the plugin applied behave differently, ie. it hangs in a deadlock or something similar.
By having the classpath for gradle-executable-jar-plugin only where it is needed, the problem goes away