Peter, We're running into this issue. Do you know when this will be fixed or if there's a workaround?

Fix will be included in 1.1. As for a workaround, you could explicitly set the manifest version. Be aware that you might run into ordering issues when you set it to project.version.toString() rather than, say, a hardcoded String.

Thanks Peter. Here are comments from Alex Blewitt who is currently working on cbk.

I'm concerned this fix is being pushed out to Gradle 1.1 and not part of 1.0 - can we apply pressure to get it tagged for the 1.0 release candidate, particularly as it's a relatively simple change?

We can't change this in the workaround suggested on the external bug, because whether or not we set the version independently, applying the plugin causes the class cast exception. So no changes that we make can resolve this issue, until this is made available.

https://github.com/gradle/gradle/blob/master/subprojects/osgi/src/main/groovy/org/gradle/api/plugins/osgi/OsgiPluginConvention.java

Unfortunately we can't make this part of 1.0 because 1.0 already has code freeze. The good news is that 1.1 will be released shortly (weeks) after 1.0. If you can't wait that long, you may want to use a nightly build.

Have you tried to set project.version before the `osgi` plugin (and possibly after the cbk plugin) gets applied?

This has conflicted with GRADLE-2237 in someway that I don't understand at this moment.

This ticket (GRADLE-1670) really should have been two. One for the CCE and one for the laziness.