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.