Closed david-resnick closed 12 years ago
Looks like we'll just need to release a version built using milestone 8. They moved the ServiceRegistry interface from the org.gradle.api.internal.project package to org.gradle.internal.service in one milestone release. This has the effect of putting a hard break in compatibility before and after that milestone.
My tests suggest that when milestone 8 comes out, I'll just have to build a version using that milestone to make it work correctly.
OK, good to know that it is a straightforward fix.
False alarm. No problem using the latest rpm plugin with the released gradle milestone 8.
Thanks for checking on that.
This is more of a heads up than an issue. I've tried running a build that uses the gradle-rpm-plugin with a gradle 1.0 milestone 8 nightly (http://repo.gradle.org/gradle/distributions-snapshots/gradle-1.0-milestone-8-20120122000008+0100-bin.zip).
The build fails during the configuration phase with the below stack trace. I've seen that the plugin code uses a few api.internal classes (though not org.gradle.api.internal.project.ServiceRegistry).
See also http://forums.gradle.org/gradle/topics/nightly_fails_to_initialize_with_java_lang_classnotfoundexception_org_gradle_api_internal_project_serviceregistry#reply_7791148