Hans Dockter wrote:
On Nov 1, 2008, at 10:07 PM, Adam Murdoch wrote
<snip>
Should there be some kind of inheritance going on, where a project
inherits this setting from its parent, and tasks from their project?
In general I'm not sure if inheritance is a good means to define
commons stuff in multi-project builds. Gradle provides inheritance for
properties and methods amongst build scripts (which would not enable
inheritance for settings stdout capture). But in general my preferred
way of configuring things is for example:
allprojects {
captureStandardOut(LogLevel.INFO)
groovydoc.captureStandardOut(LogLevel.DEBUG)
}
That way you can easily make exceptions for certain projects based on
filters.
Would you prefer an inheritance approach?
Not really for projects. Not fussed. Perhaps tasks could use the level
from their project as a default. Having played with this a bit, it seems
kind of odd that when you set the level on a project, its doesn't affect
the project's tasks. Or perhaps we just need to be able to do something
like:
alltasks {
captureStandardOut(LogLevel.INFO)
}
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
