GradleTestKit issue with Gradle 2.13

issue-resolved
gradle-3433

(Schalk Cronjé) #1

I’ve been banging my head against this one for a while now and I am only seeing this when running against Gradle 2.13 and when the Gradle version invoking it is Gradle 2.13 or Gradle 2.14.

I’ve checked the Gradle Source code for releases 2.13-3.2 and I cannot find such a signature. Maybe I’m just going mad.

java.lang.NoSuchMethodError: org.gradle.tooling.internal.consumer.DefaultBuildLauncher.withInjectedClassPath(Lorg/gradle/testkit/jarjar/org/gradle/internal/classpath/ClassPath;)Lorg/gradle/tooling/internal/consumer/AbstractLongRunningOperation;
        at org.gradle.testkit.runner.internal.ToolingApiGradleExecutor.run(ToolingApiGradleExecutor.java:98)
        at org.gradle.testkit.runner.internal.DefaultGradleRunner.run(DefaultGradleRunner.java:270)
        at org.gradle.testkit.runner.internal.DefaultGradleRunner.build(DefaultGradleRunner.java:219)

The release notes for 2.14 do not provide any clue either of a significant enough change for this to be possible.

Anyone has any idea where I can look?


(Schalk Cronjé) #2

I’m just wondering whether it is related to the Gradle API isolation that occurred between 2.13 & 2.14.


(Benjamin Muschko) #3

You are running into GRADLE-3433 which was fixed with Gradle 2.14. Please see the discussion in the linked forum post for more information.


(Schalk Cronjé) #4

That’s fixed it! Thank you very much.