Hello,
thank you very much for your support!
> > 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?
done.
> > 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
Thanks for that info.
The log of the BuildScriptProcessor was to far away and the delegation targets
changed without any hint about new scripts.
It was a multi-project-build and (if I remember right) the scriptnames of the
subprojects where not mentioned.
As I'm a newbie to gradle and groovy, the most challenging task for me is find
informations beyond the userguide and of cause find my own errors.
kind regards
Geronimo
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
