[GRADLE-2250] Error resolving previous versions of plugins to build new versions of itself Created: 24/Apr/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-7, 1.0-milestone-8, 1.0-milestone-8a, 1.0-milestone-9, 1.0-rc-1
Fix Version/s: None

Type: Bug
Reporter: John VanderPol Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Attachments: File dogfood.tar.gz    


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

Attached is 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.

Comment by Peter Niederwieser [ 24/Apr/12 ]

Confirmed. See http://forums.gradle.org/gradle/topics/error_resolving_previous_versions_of_plugins_to_build_new_versions_of_itself

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:16:48 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.