Gradle says there is a conflict but then claims nothing uses the dependency

Help/Discuss
4

Hey,

  1. I changed the title of your post. The motivation was not to maintaining a fallacy that Gradle solves this issue, but to make the title more expressive and easier for other Gradle users who run into the same issue. The intention here was not to censoring anything. We know that dealing with builds can be build hell. We’ve all have been there

  2. As mentioned dependencyInsight is always running on the current project when invoked. In your first build output you can see that this resolves to executing :dependencyInsight meaning the dependencyInsight task of the root project. The task description of dependencyInsight when running gradle tasks tells you exactly that and is explicit about which project is evaluated here. Furthermore you can read that the resolution of :engine-impl dependencies is failing.

  3. I agree with you that dependencyInsight should do a better job when dealing with failOnVersionConflict set and diagnosing conflicting dependencies. This issue was raised before in another thread at Cannot use dependencyInsight report when resolution fails on a dependency version conflict and we have an open jira ticket GRADLE-3033 to track this. This hasn’t been high prioritized so far but we finally have the bandwidth to deal better with this kind of issues raised by the Gradle community. Please vote for this issue.

cheers,
René