0.16.1 crash: missing getProperty() implementation

[akarnokd]

Hi. I upgraded to 0.16.1 and now my build (Gradle 6.8.3) crashes with the following error:

Receiver class com.hierynomus.gradle.license.LicenseBasePlugin does not define or inherit an implementation of the resolved method 'abstract java.lang.Object getProperty(java.lang.String)' of interface groovy.lang.GroovyObject.

Caused by: java.lang.AbstractMethodError: Receiver class com.hierynomus.gradle.license.LicenseBasePlugin does not define or inherit an implementation of the resolved method 'abstract java.lang.Object getProperty(java.lang.String)' of interface groovy.lang.GroovyObject.
at com.hierynomus.gradle.license.LicenseBasePlugin$_createExtension_closure2.doCall(LicenseBasePlugin.groovy:73)

0.15.0 still works.

[NilsOliverLinden]

It seems Gradle 7.0 and license-gradle-plugin 0.16.1 are compatible.

[hierynomus]

Yes, that's what I used when releasing/testing 0.16.1 indeed. I'll check with 6.0+ to see whether something can be done to improve this.

[rarcher]

I am also experiencing this issue. In Gradle 6.3, in my case.

[rarcher]

Work-around seems to be to upgrade Gradle and the plugin at the same time, as 0.15.0 seems to be incompatible with Gradle 7.

[Samuel3]

@rarcher If you have a bigger project with multiple Gradle plugins it is not always so easy to update the Gradle version due to the plugin constraints. I would really appreciate a fix for Gradle 7.0 as well as the versions below.

[torgeros]

something when running version 0.15.0 with gradle:

Executing tasks: [downloadLicenses] in project XXXXXXXXXXXXXXXXXXXXXXXXX

> Task :app:downloadLicenses

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.7.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 141ms
1 actionable task: 1 executed
14:32:12: Task execution finished 'downloadLicenses'.

[xtreme-shane-lattanzio]

I am also running into this.Are there plans to have the new version be backwards compatible with older versions of gradle?

[ngyukman]

From our experience, building the plugin using 6.9 can support both gradle 6 and gradle 7
committed #202 to fix the issue