A helpful ModuleVersionNotFoundException

(Andreas Nyberg) #1

It is very common to get a dependency wrong, and the error message tells me what could not be resolved, but gives no clue as to what went wrong:

FAILURE: Build failed with an exception. >

* What went wrong: > Could not resolve all dependencies for configuration ‘:xxx:yyy:zzz’. > > Could not find aaa:bbb:1.2.3. >

Required by: >

xxx.yyy:4.5.6 >

* Try: > Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. >


Using ‘–info’ or ‘–stacktrace’ don’t tell me much more, and ‘–debug’ might, I just van’t had time time parse the output yet. Verbose logging is great when you don’t know what the problem is; useful exceptions contain information about the problem, not just the location where it was discovered.

What would be really helpful, and probably fairly easy to implement, is a list of “tried” URLs as part of the Exception, that could be printed as a nice list.