Error resolving previous versions of plugins to build new versions of itself


(john.vanderpol) #1

In gradle versions after 1.0 milestone 6 I am having problems building a gradle plugin that uses a previous version of itself as a plugin for its own build. For example if I am building a com.foo:dogfood:1.1 artifact that is attempting to use com.foo:dogfood:1.0 as a buildscript classpath dependency I get the following error:

Could not resolve all dependencies for configuration ‘:classpath’. Cause: Module version group:com.foo, module:dogfood, version:1.1, configuration:classpath declares a dependency on configuration ‘default’ which is not declared in the module descriptor for group:com.foo, module:dogfood, version:1.1

GRADLE-2250 has a sample project that can reproduce the error. Untar it and run the test command, it will run a release to the local maven repo, try to use it in another build which will fail, and then try to use it in a 3rd build which will succeed. The only difference between the 2nd and 3rd build is that that 3rd build doesn’t use a gradle.properties file for it’s group and version.


(Peter Niederwieser) #2

Thanks for the thorough report. Definitely looks like a bug. Can you use the workaround (declare the version in the build script or set the version to a project/system property from the build script) for the moment?


(john.vanderpol) #3

Yeah that works for the time being.