[GRADLE-356] Not naming resolvers causes NullPointerException Created: 10/Jan/09  Updated: 04/Jan/13  Resolved: 13/Apr/09

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 0.6

Type: Bug
Reporter: Levi Hoogenberg Assignee: Hans Dockter
Resolution: Fixed Votes: 0


When adding an Ivy resolver, forgetting to set its name causes an exception. So

dependencies {
    classpathResolvers.add(new URLResolver()) {
        // no name = "..." here


fails when trying to resolve dependencies when either Gradle or Ivy, I'm not sure, tries to put the resolver into a hash table (probably with its name as the key).

A message that says that a resolver needs a name would be much more user-friendly, of course.

Comment by Hans Dockter [ 13/Apr/09 ]

We now throw an exception with an appropriate message.

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