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?

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...?).

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

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.

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!

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.