[GRADLE-3033] Cannot use dependencyInsight report when resolution fails on a dependency 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: 8



When I have a version conflict, I want to use 'gradle dependencyInsight' to figure out the cause of the problem. Unfortunately, while running 'gradle dependencyInsight', the build will fail, too, due to this version conflict.

This means that I first have to fix the conflict before I can use dependencyInsight. But, once the conflict is resolved, I do not need dependencyInsight anymore.

Proposal: Offer a way to inspect the cause for version conflicts without having to resolve the conflict first.

Regards, Etienne

Comment by Gradle Forums [ 25/Feb/14 ]

Usually, a version conflict won't cause the build to fail. (Instead, the conflict will be resolved automatically.) Are you talking about a case where `configuration.resolutionStrategy.failOnVersionConflict()` is used?

Comment by Gradle Forums [ 25/Feb/14 ]

Yes, you guessed right: we are using failOnVersionConflict(). Unless I comment it out, I cannot investigate what is the root of a version conflict.

I propose that there is a way to run dependencyInsight even if there are dependency problems (cmd line flag or...?).

Comment by Raman Gupta [ 26/Apr/14 ]

I have this problem too. I think the best solution would be to just display the relevant dependencyInsight output automatically when failOnVersionConflict is triggered.

Comment by Andrew Barchuk [ 14/Jul/16 ]

The source of the problem is reporting of version conflicts: instead of showing location of conflicting versions in the tree, only version numbers are printed which are of little help to track and fix the conflict.

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