Closed jest closed 8 years ago
The Release Notes give me no hint of what might be wrong.
Maybe something similar to GRADLE-3455 issue?
This sounds like a bug in Gradle. Did you report it to them?
The code in the bnd plugin is doing what is described in https://docs.gradle.org/current/dsl/org.gradle.api.plugins.ExtensionAware.html to create a bnd
extension on the project.
Cross-posted to https://discuss.gradle.org/t/bnd-plugin-broken-in-2-14/17983
But isn't extensions.create()
for extending DSL and ext
for simple properties? Just guessing, I have no experience with plugins...
extentions.create is to create a named set of properties. I use it to create the bnd set of properties. Then bnd.ext.project is set to hold the bnd Project object. Then project.bnd.project is the Bnd Project object for the Gradle Project object.
This is an issue in Gradle 2.14 builds. See https://discuss.gradle.org/t/bnd-plugin-broken-in-2-14/17983/4
The Gradle team is investigating.
This bug resulted in the adding some release notes to the 2.14 release: https://docs.gradle.org/2.14/release-notes#changes-to-dynamic-property-look-up
Is there going to be an intermediary release of the Bnd Gradle plugin to fix this issue? Or in other words: any idea when the fix will be available to the general public?
I think we will release a 3.3 in the next month or two. In the interim, you will need to stick with Gradle 2.13 or use the dev Bnd builds.
Trying to run a project using Gradle 2.14 (rc-1 to rc-5) and biz.aQute.bnd plugin results in an error, where Gradle 2.13 works fine.
The error appears during applying a plugin in a script (a copy of enRoute's Gradle workspace):
The exception thrown:
The offending line: https://github.com/bndtools/bnd/blob/master/biz.aQute.bnd.gradle/src/aQute/bnd/gradle/BndPlugin.groovy#L64