[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 |
Description |
When adding an Ivy resolver, forgetting to set its name causes an exception. So dependencies { classpathResolvers.add(new URLResolver()) { // no name = "..." here addIvyPattern("...") addArtifactPattern("...") } } 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. |
Comments |
Comment by Hans Dockter [ 13/Apr/09 ] |
We now throw an exception with an appropriate message. |