I run into the very same problem (http://jira.codehaus.org/browse/GRADLE-242)
and I temporarily fixed it for me by patching Ivy:
Index: java/org/apache/ivy/plugins/report/LogReportOutputter.java
===================================================================
--- java/org/apache/ivy/plugins/report/LogReportOutputter.java (revision
706277)
+++ java/org/apache/ivy/plugins/report/LogReportOutputter.java (working
copy)
@@ -67,9 +67,16 @@
nodeConfs.add(conf);
}
}
+
+ final String resolverName;
+ if ((null != node) && (null !=
node.getModuleRevision()) && (null !=
node.getModuleRevision().getResolver())) {
+ resolverName =
node.getModuleRevision().getResolver().getName();
+ } else {
+ resolverName = "*** UNKNOWN resolver ***";
+ }
Message
.info("\t" + node + " from "
- +
node.getModuleRevision().getResolver().getName() + " in "
+ + resolverName + " in "
+ nodeConfs);
}
}
After that patch the underlying dependency problem was properly reported and
did not have to spend time on guessing the problem any more.
But this is only a fix in the Ivy sources and not in the Gradle sources...
I hope there will be a final fix for the problem in 0.5.0.
Helmut Denk wrote:
>
> if i fix the dependencys so that they can be resolved by
> gradle, no NPE is thrown ...
>
> i get a compile-error then, but that's not a gradle-
> problem ... ;-)
>
> F:\workspaces\gradle>gradle -v
> Gradle 0.5-081021151745+0200
> Gradle buildtime: Dienstag, 21. Oktober 2008 15.17 Uhr CEST
> Groovy 1.5.6
> Java 1.5.0_14
> JVM 1.5.0_14-b03
> JVM Vendor: Sun Microsystems Inc.
> OS Name: Windows XP
>
--
View this message in context:
http://www.nabble.com/NullPointerException-if-dependencys-can-not-be-resolved-tp20128584p20130787.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
