[GRADLE-1945] IDE plugins do not warn that some dependencies are unresolved Created: 20/Nov/11  Updated: 20/Jan/16  Resolved: 14/Jan/16

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 2.11-rc-1

Type: Bug
Reporter: Szczepan Faber Assignee: Stefan Oehme (Inactive)
Resolution: Fixed Votes: 6

Issue Links:
Duplicated by GRADLE-2370 Idea plugin should fail if there are ... Resolved


'gradle eclipse' or 'gradle idea' continue executing even if some dependencies are unresolved. This is expected behavior because the user might be interested in working in IDE even though some dependencies are unresolved. However, it would be nice to warn the user ahead that something is wrong, rather than wait until he cannot build the project in the IDE. The problem is not critical because the unresolved dependencies in IDE have an extra 'unresolved' label that helps understanding why the project does not build. Nevertheless we should consider printing a warning if some dependency is unresolved at build time.

Comment by Andreas Nyberg [ 26/Mar/13 ]

Also, in general when artefacts are missing, it would be great to see where it looked already in the error message (captured in the exception thrown), rather than first failing with a message that cannot pinpoint the problem and then have to rerun with debug logging.
"Could not resolve x:y:z; tried ...; tried ..."

Comment by Carl Pritchett [ 14/Sep/14 ]

Git bitten by this today, wasted some time so warnings at least would be valuable

Generated at Wed Jun 30 12:08:35 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.