On Nov 4, 2008, at 5:23 PM, Phil Messenger wrote:
hdockter wrote:
Setting: ivySettings.setVariable("ivy.log.modules.in.use", "false"),
is a work around we are now using (and it seems to be the Ivy
default). Are you working with Gradle trunk? The getIvy() method
should then contain an IvySettings object were this property is set
to false.
I'm don't know what this property is exactly about and if the above
solves your issue with this bug. So I'm happy to bundle Gradle with
an Ivy snapshot if it helps you.
Heh, I actually wrote a patch to fix the issue and decided to do a
search on
the Ivy Jira before submitting it and found your report.
:)
The root cause is
that if the version/revision property in a Maven pom is nonesense,
an object
doesn't get set in Ivys internal dependency tree and the logging
(!) tries
to dereference this null object causing the NPE. That property just
disables
the logging.
It has been fixed in Ivy trunk, but if you've added the workaround
to Gradle
that should suffice. My trunk is about a week old...
From the Gradle svn log:
------------------------------------------------------------------------
r1050 | hans_d | 2008-10-30 12:07:44 +0100 (Thu, 30 Oct 2008) | 1 line
GRADLE-242 Gradle throws a NPE if Ivy can't resolve a dependency.
------------------------------------------------------------------------
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
