[GRADLE-861] Please improve the error message when trying to use "null" as a dependency notation Created: 22/Mar/10  Updated: 04/Jan/13  Resolved: 24/Nov/11

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 1.0-milestone-7

Type: New Feature
Reporter: Reinhard Mantey Assignee: Unassigned
Resolution: Fixed Votes: 0


 Description   

I tried to use a map of libraries with references from subprojects.
I spent few hours on diving into logfiles, adding messages, changing
buildscripts line by line, before I discovered my typo in dependency
references.

The output from gradle was:
---------<snip>----------------
FAILURE: Build failed with an exception.

  • Where:
    Build file '.../build.gradle' line: 2
  • What went wrong:
    A problem occurred evaluating project ':library'.
    Cause: The dependency notation: null is invalid.
    --------<snap>----------------

and the logs (-d option) did not gave any further hint.
The referred errorline was the start of dependencies.

Don't know, whether it is possible, but I would appreciate an error-message
telling about which key not found in the map or something similar. It's
completely ok, have that information at debug-level only.



 Comments   
Comment by Hans Dockter [ 24/Mar/10 ]

What exactly was your typo?

Comment by Reinhard Mantey [ 24/Mar/10 ]

I renamed a map entry from "acegi" to "acegi_security" and forgot that "acegi" has already been used in dependencies, so I referred to a non existing key.

Generated at Wed Jun 30 11:40:50 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.