[GRADLE-3035] Confusing error messages regarding the configuration name when there is a version conflict Created: 25/Feb/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 0



If I run 'gradle assemble' from the root of my multi-project build, I get this (which is okay):

Could not resolve all dependencies for configuration ':edoras-commons-test:compile'.
> A conflict was found between the following modules:

  • org.hamcrest:hamcrest-core:1.1
  • org.hamcrest:hamcrest-core:1.3

I then run 'gr dependencyInsight --configuration :edoras-commons-test:compile --dependency org.hamcrest:hamcrest-core' and get the following message:

Configuration with name ':edoras-commons-test:compile' not found.

I'm confused: first, Gradle tells me there is a conflict in a given configuration, and then when I inspect that configuration, it tells me the configuration does not exist.

Can anybody help me out?

Thanks and regards, Etienne

Comment by Gradle Forums [ 25/Feb/14 ]

You need to run `gradle :edoras-commons-test:dependencyInsight --configuration compile`, not `gradle dependencyInsight --configuration :edoras-commons-test:compile`.

Comment by Gradle Forums [ 25/Feb/14 ]

Ok Thanks, Peter.

In this case, I propose to improve the error message 'Could not resolve all dependencies for configuration ':edoras-commons-test:compile''

to something like

'Could not resolve all dependencies for configuration 'compile' in module :edoras-commons-test'

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:38:08 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.