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?

- Hans

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





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

   http://xircles.codehaus.org/manage_email


Reply via email to