On 20/03/10 9:08 PM, Geronimo M. H. wrote:
Hello,

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.

A good idea. Can you add a JIRA issue for this?



Another log, which I like to get further informations is
---------<snip>---------------
10:28:03.120 [main] DEBUG o.g.g.scripts.DefaultScriptMetaData - Property
gradle not found in script! Delegating to project ':project1'.
10:28:03.125 [main] DEBUG o.g.g.scripts.DefaultScriptMetaData - Method
repositories not found in script! Delegating to project ':project2'.
---------<snap>--------------

It would be nice, to get the file- or project-name, gradle is evaluating.
Especially in multi-project-builds.

It's already there:

08:15:26.392 [main] INFO o.g.c.BuildScriptProcessor - Evaluating root project 'quickstart' using build file '.../build.gradle'. <== this is the project and build file it is evaluating
... snip ...
08:15:28.226 [main] DEBUG o.g.g.scripts.DefaultScriptMetaData - Property manifest not found in script! Delegating to root project 'quickstart'. <== this is the project it is evaluating


--
Adam Murdoch
Gradle Developer
http://www.gradle.org


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to