I dealt with a dependency conflict between two different packages that wanted different versions of Apache Commons. Both of them only claimed that they wanted "greater than or equal to X version." This wasn't actually true, though, because Apache Commons had removed some features and added some features, so the real requirements were
Package A wants Commons >= X and < Y
Package B Commons >= Z
where Z > Y.Sorting that out meant manually doing exactly what this Depends package does - poking around with different versions and using the missing method exceptions and some other research to figure out the exact nature of the conflict, so that I could pin their versions and set up appropriate package relocation rules.
This tool would not just do that faster, but also more reliably - by doing it manually, I was only able to verify that I had resolved any issues with the code I actually exercised. A gap in test coverage would leave me exposed to run-time errors in production.
mvn dependency:tree -Dverbose
or
./mvnw dependency:tree -Dverbose (if you are using the Maven wrapper)
https://search.maven.org/#browse
to find the artifact hosting it, and it tends to be a couple minute job
Bonus tracks: gradle dependencyInsight is great for a similar task: finding out which artifact is bringing the dep.
Build tools do their best. Gradle has a reasonably sane version based solution. By statically analyzing the method invocations (and eventually properties too), this tool could (one day) just tell you the versions to use that would be most likely to work.
The long term vision would be to actually incorporate this as a dependency resolution strategy in Gradle so you don't have to think at all.
Besides, where's the automated part on the OP solution? I agree the automation, either with this tool, or vanilla project management ones like gradle, could be beneficial.
What was wrong with
> ./gradlew dependencies
and then sorting out your duplicate dependencies with improper version issues.
I have spent a lot of time down this road myself and most of it was not fully understanding the framework dependencies, munging of stackoverflow solutions, or apache-commons hell...sometimes a little bit of it all.
Not trying to crap on your hardwork but interested in your motivations if its something bigger which I am not seeing.
Long term I don't think you can properly suggest the appropriate dependency, this is why most build tools provide default selection and let you override with exclude patterns.
Additionally there is a linting tool that will parse through duplicates and offer to clean up your gradle files if that is interesting to you alongside your work.