Gradle 2.14-rc-2 still exhibits backwards compatibility issues with plugins


(Danny Thomas) #1

We’re still seeing backwards compatibility issues with our plugins on the latest release candidate:

Caused by: groovy.lang.MissingMethodException: No signature of method: nebula.plugin.contacts.BaseContactsPlugin$_apply_closure1.doCall() is applicable for argument types: (build_csl5ov9p544a65d2upsg9lhk4$_run_closure1) values: [build_csl5ov9p544a65d2upsg9lhk4$_run_closure1@1ded7fca]
Possible solutions: doCall([Ljava.lang.String;), findAll(), findAll(), isCase(java.lang.Object), isCase(java.lang.Object)
	at org.gradle.internal.metaobject.CompositeDynamicObject.invokeMethod(
	at org.gradle.internal.metaobject.AbstractDynamicObject.invokeMethod(
	at org.gradle.groovy.scripts.BasicScript.methodMissing(
	at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$
	... 50 more

Where the build line that’s failing is:

The contacts extension is created like this:

The plugin applies itself as part of our plugin development plugin, so you can reproduce the problem with the project’s own build:

(Sterling Greene) #2

Thanks! We’re looking

(Sterling Greene) #3

I raised

I think we’ll have another RC

(Stefan Wolf) #4

Could you try with 2.14-rc-3. The bug should be fixed there.

(Danny Thomas) #5

Yep, all good here. Seeing this in one of our tests now: