I don't remember the exact error message, but one of our developers just got
a "dependency missing error" for module 'A'.  Running with the '-s' option
informed me that there was no such configuration as 'default'.  This was no
help.  After quite a bit of things (including rebuild the gradle cache, and
making sure that the developer had all latest code from our VCS) I
remembered the dependencyReport task.  Running that on module A informed me
that it depended on module B which did not exist.  Looking at the developers
file system, sure enough the directory for module B was missing.  We
restored it from VCS and all was good.

Does anyone know of an existing bug report for this?  The original error
message really needs to point out the A depends on B which doesn't exist.
That would have saved 1/2 to 1 hour of troubleshooting.

-- 
John Murph
Automated Logic Research Team

Reply via email to